Alexandre Julliard : configure: Don't accept mingw32 as target name, we need an explicit CPU specification.

King InuYasha ngompa13 at gmail.com
Fri Jun 19 14:59:27 CDT 2009


On Fri, Jun 19, 2009 at 12:43 PM, Steven Edwards <winehacker at gmail.com>wrote:

> On Fri, Jun 19, 2009 at 1:21 PM, Alexandre Julliard<julliard at winehq.org>
> wrote:
> > This is not a configure option, it's the name of the installed mingw32
> > binaries. They are supposed to follow the GNU naming convention for
> > cross-compilers, and they do on all sane distros AFAIK.
>
> Right I get that. I just mean that its pretty common to see homebrewed
> cross-compilers with just mingw32 as the prefix.  The reason I guess
> is that on Windows (c:\mingw\bin\*) it does not follow the gnu naming
> convention because it does not have to follow it and people carry that
> over when they are rolling their own cross-compiler. Now that most
> distro's are shipping mingw packages this is less common. I guess your
> argument is right and anyone rolling their own should get with the
> program and follow the standard.
>
> --
> Steven Edwards
>
> "There is one thing stronger than all the armies in the world, and
> that is an idea whose time has come." - Victor Hugo
>
>
>
Fedora, Debian/Ubuntu, SUSE, and Mandriva come with complete toolkits that
follow the GNU naming convention for the Win32 cross compiler.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20090619/95dd9906/attachment.htm>


More information about the wine-devel mailing list