Re: [MinGW-dvlpr] mingwrt and w32api build system clean-up

[Earnie <ea...@us...>]

Keith Marshall wrote:
> This means that, for a mingw32 deployable build destined for a cygwin
> target, (whatever that might mean), installation will be directed to:
> 
>   ${prefix}/i386-pc-cygwin/include/w32api/*.h
>   ${exec_prefix}/i386-pc-cygwin/lib/w32api/lib*.a
> 
> with default substitution of /usr/local for both ${prefix} and
> ${exec_prefix}; these installation paths, with initial / stripped off,
> will also be reflected in the distributable binary package.  Doesn't
> look sane to me, but what do I know?  Is this what you guys want?
> 

Yes, in Cygwin, w32api is delivered and required as /usr/include/w32api
and /usr/lib/w32api.

The mingwrt and w32api on the other hand is delivered in a cross tools
directory for mingw32-gcc in /usr/i686-pc-mingw32/sysroot/mingw/.  This
though may be handled by cygport?

-- 
Earnie
-- https://sites.google.com/site/earnieboyd/