Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
content-class: urn:content-classes:message
Subject: RE: setup changes to build standalone
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Fri, 26 Apr 2002 13:44:32 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5F04@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-apps AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3Q3iau16328



> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com] 
> Sent: Friday, April 26, 2002 1:19 PM

> >So,
> >I've made a copy of bz2lib from src/winsup/bz2lib to set/bz2lib, and 
> >adjusted accordingly.
> 
> Ack.  Duplication.  Duplication bad.

Yup.
 
> Here was a good reason not to move cinstall.  Sigh.

Yes. I even documented all this some time back on
http://www.cygwin.com/ml/cygwin-apps/2001-11/msg00634.html, but
predicatably enough, no patches where forthcoming. Probably due to the
complete lack of a prebuilt bz2lib for mingw (that my cursory searches
have looked for).
 
> I can't think of any way around this, though.  Even if we say 
> "You must have a mingw version of libbz2.a available" that 
> will screw up my need for this library in winsup.
> 
> I wonder if we need a "mingw-libs" package.

Yes, please, please, yes. I would really really love it if some of the
common libs (zlib, bz2lib, stdc++) where available in a setup.exe
installable pacakge.
 
> 1) Why the --host=?  So that you'll be able to use a mingw version of
>    everything?

Yes. It gets rid of the need for mingw_foo in the make files, and makes
it explicit that we are cross compiling.
 
> 2) The above won't work in a cross build environment.  You could say
>    CC='i686-pc-cygwin-gcc -mno-cygwin'..., I guess.

for cross compiles:
../setup/configure --host=i686-pc-mingw32 --build-i686-pc-linux 
should do it (assuming a mingw32 cross compiler is present), or a
combination using the CC string you have above with the mingw host will
work too.
 
> I think you should just check it in and tweak things in cvs 
> rather than post a patch.  It's not going to impact anyone 
> but a tiny handful of people if you use cvs but it will 
> impact a much larger audience if you send out patches.

Ok, will do. 
 
> anything that is non-simple.  I haven't looked at it in a 
> while, though, so maybe things have changed.

It really depends on what you want to do. Some stuff it does
spectalularly well, some things it has trouble with. With the 'cross
compiling but not' approach, it would almost certainly have some trouble
:}.

Rob