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: RFC: cygport cross-compiling APIs

On Thu, 2010-07-15 at 01:46 -0400, Christopher Faylor wrote:
> On Wed, Jul 14, 2010 at 06:54:41PM -0500, Yaakov (Cygwin/X) wrote:
> >On Wed, 2010-07-14 at 11:12 -0400, Christopher Faylor wrote:
> >> You know, back when I was distributing the mingw and w32api packages I
> >> would have sworn that I put them in cross-compiler locations and created
> >> legacy symlinks back to the old /usr/include /usr/lib locations.
> >
> >That would be possible with mingw-runtime but not with w32api.
> It's possible with anything if you modify the compiler which is, I believe,
> what I had done.

Let me clarify: mingw-runtime and mingw-w32api will end up in the same
directory, namely /usr/i686-pc-mingw32/sys-root/mingw/{include,lib}.
Theoretically, one could create symlinks from there
to /usr/{include,lib}/mingw without issues.  But if you do the same
for /usr/{include,lib}/w32api, then suddenly the MSVCRT headers and libs
end up in native gcc's default search path, and that is a recipe for

However, practically, we won't be able to ship /usr/{include,lib}/mingw
symlinks because those locations are currently real directories
containing the soon-to-be-old mingw-* packages.  OTOH, if the new
mingw-gcc cross-compiler outright replaces the old gcc-3 -mno-cygwin
support packages, then we won't need /usr/{include,lib}/mingw at all.


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