[RFC] Simplify MinGW canadian crosses

Corinna Vinschen vinschen@redhat.com
Tue Aug 29 15:35:00 GMT 2006

On Aug 29 11:09, Daniel Jacobowitz wrote:
> On Tue, Aug 29, 2006 at 10:59:27AM -0400, DJ Delorie wrote:
> > 
> > > If you want to build some code that runs on mingw, I don't think
> > > that having mingw tools installed is an unreasonable requirement.
> > 
> > This is how you *get* mingw tools installed.  The same logic that
> > gives you a canadian (worst case) also gives you host-x-host.
> Not so, unless I'm vastly confused.
> Corinna is trying to generate --host=i686-mingw32 tools, with a
> different --target.  This requires at least a --target=i686-mingw32
> compiler coming from elsewhere.  That compiler can build the
> --host=i686-mingw32 libraries, and usually should.
> This is more like adding support for using the in tree newlib with an
> arm-linux compiler so that you could build GCC to run on arm-linux,
> without having to install an arm-linux C library first.  That's why
> I'm dubious about the value.  But maybe Corinna has some good example
> of when you want to do this?

Sorry, but that's not the deal.  Using my patches, you can install a
standard source tree, including gcc, gdb, binutils, [...], and last but
not least the winsup directory on, say, a Linux machine, and then build
a complete three stage canadian cross on *Linux*, which generates a
i686-pc-mingw32-x-arm-elf toolchain.  You don't have to install the MinGW
libraries and header files somewhere on the Linux machine and tweak the
build process to find them.  Everything comes out of the same source
tree.  From my point of view this simplifies stuff, it doesn't make it
more complicated.


Corinna Vinschen
Cygwin Project Co-Leader
Red Hat

More information about the Cygwin-patches mailing list