Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <425E64A1.734F8EAC@dessent.net> Date: Thu, 14 Apr 2005 05:40:01 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: cygwin on Mac: files in Virtual PC "shared folder" References: <3d0b16f3b50f2acdb38a5479b9813ce4@dcs.warwick.ac.uk> <6.2.1.2.0.20050413180131.03cf4bf8@pop.prospeed.net> <6c620aa8a3e08df24c9dd17cf8f27c83@dcs.warwick.ac.uk> <425E4DC5.C37692A5@dessent.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Ashley Ward wrote: > I was a bit confused about it, though -- can such a setup *link* a > final binary as well as compile? Presumably then all the necessary > libraries from each platform need to be available on the build > platform? You can link the final binary as long as you have import libraries. As far as I know, you don't need the actual libraries themselves since you're not running the binary. So for example, just install winsup/w32api/lib*.a (or /usr/lib/w32api/lib*.a from an installed Cygwin) into your cross compiler's library search path and the link should work, assuming everything is setup right. (You of course also need a working set of headers too.) If you check the Cygwin/X web site there's a nice guide on how to build a cross toolchain for the purposes of building the XWin server (which works equally well for general cygwin cross compiling.) Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/