Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <425E4DC5.C37692A5@dessent.net>
Date: Thu, 14 Apr 2005 04:02:29 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: cygwin on Mac: files in Virtual PC "shared folder"
References: <3d0b16f3b50f2acdb38a5479b9813ce4 AT dcs DOT warwick DOT ac DOT uk> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050413180131 DOT 03cf4bf8 AT pop DOT prospeed DOT net> <6c620aa8a3e08df24c9dd17cf8f27c83 AT dcs DOT warwick DOT ac DOT uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Ashley Ward wrote:

> Because of these issues, my preferred solution would be to use Shared
> Folders -- if it worked, it'd be a lot simpler than Samba -- no
> separate server and configuration to worry about.  I might try
> following up the issue with MS VPC support in the newsgroup and then
> possibly through their email or phone support (although it seems I
> might have to give them a credit card number first! :<).

I know that this doesn't really address your question at hand... but if
I were in your situation I would look into just building a gcc/binutils
cross compiler toolchain.  Then you could run the build natively under
OS X, but produce win32 binaries.  You would still need VPC for testing
the binaries (I presume) but OS X should have enough unix under the hood
to host the build.

In fact the cygwin1.dll on your system right now was probably compiled
on linux, as some of the Cygwin developers (or at least cgf) use this
method.  (And I can understand why they do it, after I tried it myself
-- a linux hosted cross gcc runs the configure && make for the Cygwin
build about 2 to 3 times faster under linux on the same hardware
compared to win32.)

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/