Re: Cygport improvements

[JonY <jon_y at users dot sourceforge dot net>]

On 6/26/2010 12:24, Christopher Faylor wrote:
> On Sat, Jun 26, 2010 at 12:15:10AM -0400, NightStrike wrote:
> > On Sat, Jun 26, 2010 at 12:05 AM, Christopher Faylor
> > <cgf-use-the-mailinglist-please@cygwin.com>  wrote:
> > > On Sat, Jun 26, 2010 at 10:14:42AM +0800, JonY wrote:
> > > > Hello,
> > > >
> > > > I am planning to bring mingw-w64 to cygwin. Here are some nits I found
> > > > when working with it.
> > > >
> > > > * It sets CC=gcc
> > > > While not a major issue, it does present some issues when cross
> > > > compiling the mingw-w64 CRT.
> > >
> > > Why would a Cygwin tool worry about mingw? ?We've already removed mingw
> > > support from gcc. ?Why add it to something called "cygport"?
> > >
> > > > * Implicitly setting --prefix=/usr
> > > > While I understand this is suitable for native builds, perhaps adding
> > > > some cross compile logic to disable this?
> > >
> > > Ditto. ?It's intended to make cygwin packages.
> > >
> > > I really don't see how making something mingw aware is a topic for
> > > the cygwin mailing list.
> >
> > He's trying to make a cygwin package that consists of a cross compiler
> > toolchain for targetting 64-bit windows from a cygwin host.  Cygport
> > puts some obstacles in the way for doing that.  Maybe you could
> > suggest how to get around his issues?  That'd be a big help if you
> > could shed some light on the things he mentioned.
>
> If it's a cross-compiler then it should be installed in /usr.

Yes, its a cross compiler, compiler frontend binaries go in /usr/bin, 
but headers and libraries for target do not belong in cygwin 
/usr/include and /usr/lib.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple