From: noer AT cygnus DOT com (Geoffrey Noer)
Subject: Re: Patching/Compiling a new cygwin.dll?
25 Apr 1997 02:03:29 -0700
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199704250718.AAA18016.cygnus.gnu-win32@rtl.cygnus.com>
Content-Type: text
Original-To: kunglao AT prairienet DOT org
Original-Cc: gnu-win32 AT cygnus DOT com
In-Reply-To: <199704232243.RAA01937@bluestem.prairienet.org> from "kunglao@prairienet.org" at Apr 23, 97 05:46:04 pm
X-Mailer: ELM [version 2.4 PL23]
Original-Sender: owner-gnu-win32 AT cygnus DOT com

kunglao AT prairienet DOT org wrote:
> 
> For some reason, in the back of my cluttered mind, I seem to have 
> this notion that there may have once been mentioned that to compile a 
> new cygwin.dll you needed a commercial compiler like VC++.  Is that 
> true?

Nope, not at all.

> Or can you compile it with the normal cygwin gcc et al?  

Yes.

> Would a linux cross-compiler be an option?

Yes.  If you configure the sources under most standard Unix flavors
(including Linux) setting --target=i386-cygwin32, and then build the result
you will get a cross-compiler capable of compiling Win32 apps.  Once you
have this cross-compiler, you can build the native tools if you want,
setting --build=i586-linux (or whatever), --host=i386-cygwin32, and
--target=i386-cygwin32 and then doing the make.  Once you have the native
tools, you can rebuild the native tools with a simple configure and make.

-- 
Geoffrey Noer
noer AT cygnus DOT com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".