This is the mail archive of the
mailing list for the binutils project.
Re: [RFC] Simplify MinGW canadian crosses
- From: Daniel Jacobowitz <drow at false dot org>
- To: gcc-patches at gcc dot gnu dot org, gdb-patches at sourceware dot org, binutils at sourceware dot org, mingw-patches at lists dot sourceforge dot net, cygwin-patches at cygwin dot com
- Date: Tue, 29 Aug 2006 08:45:25 -0400
- Subject: Re: [RFC] Simplify MinGW canadian crosses
- References: <20060829114107.GA17951@calimero.vinschen.de>
On Tue, Aug 29, 2006 at 01:41:07PM +0200, Corinna Vinschen wrote:
> I created the below patchset to allow to build canadian crosses with
> MinGW as host machine. It allowed me to build a linux-x-mingw-x-powerpc
> canadian cross, using the in-tree winsup directory, and so,
> consequentially, without the need to have any externally installed MinGW
> headers and/or libraries.
> Unfortunately, this requires changes in top-level, in libiberty, in
> winsup, in winsup/mingw, and in winsup/w32api.
Some of these patches may be good on their own. But, why go to this
much effort to support doing this complicated setup in a single tree? I
really don't think it's a good idea. If you want to build some code
that runs on mingw, I don't think that having mingw tools installed
is an unreasonable requirement.
We have to pick and choose where to invest in making our build system
even more complex.