This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cygport cross-compiling beta1

On Tue, 2010-07-20 at 10:51 -0400, Charles Wilson wrote:
> Well, I guess the replacement package for the gcc(3)-mingw stuff can 
> just create symlinks:
>     /usr/lib/mingw     -> /usr/i686-pc-mingw32/sys-root/mingw/lib
>     /usr/include/mingw -> /usr/i686-pc-mingw32/sys-root/mingw/include
> (or, rather, gcc-mingw-* could simply be obsoleted -- and the 
> replacement version having a postinstall script that does what the 
> gcc-mingw-* preremove scripts SHOULD have done, which is to remove the 
> /usr/i686-pc-mingw32/{bin,include/lib} symlinks, and a new repackaged 
> version of gcc(3)-core could generate the /usr/{lib,include}/mingw 
> symlinks itself.

If gcc-mingw* go away then you don't need /usr/{include,lib}/mingw,
because -mno-cygwin will no longer work, right?

Either way, changing /usr/{include,lib}/mingw from directories into
symlinks is not so simple, as the current mingw-* packages all install
into there.

> However, depending on how the system includes are ordered, gcc3 
> -mno-cygwin will then either use the "cygwin" w32api in 
> /usr/include/w32api, or the cross versions mixed in to 
> /usr/i686-pc-mingw32/sys-root/mingw/include.

How would gcc3 know about the mingw sysroot?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]