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
Message-ID: <3CC8D3A1.7070605@ece.gatech.edu>
Date: Fri, 26 Apr 2002 00:12:17 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: cygwin-apps AT cygwin DOT com
Subject: Re: setup changes to build standalone
References: <FC169E059D1A0442A04C40F86D9BA7600C5F04 AT itdomain003 DOT itdomain DOT net DOT au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Robert Collins wrote:

> 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).


https://sourceforge.net/projects/mingwrep/

 
>>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.


Yes, I like this too -- but I'm nervous about it growing ridiculously 
large.  What if (eventually) setup.ini turns into XML?  Do we put a 
mingw build of libxml into 'mingw-libs'?  How far does this go? 
(visions of full{mingw}.exe)

OTOH, we've already discussed (and discarded, thank g-d) the idea of 
(for instance) the zlib maintainer providing both a 
cygwin-setup-installable zlib package (/usr/bin/cygz.dll, 
/usr/lib/libz.[dll|a]) and a cygwin-setup-installable mingw-zlib package 
(/usr/bin/mgwz.dll, /usr/lib/mingw/libz.[dll|a]).  Ditto bzip2, libxml, 
...  we are not a mingw-porting factory.

>>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.


whatever happened to the idea of an official cygwin package, that 
contained a true cygwin-host, mingw-target cross compiler?  Didn't 
somebody or other volunteer to provide that?

(Granted, we still need 'cygwin-gcc -mno-cygwin' for the "self-hosting" 
feature of cygwin1.dll, but there's no real need to *require* cygwin-gcc 
-mno-cygwin for setup.exe, now that setup has been moved out of the 
winsup tree)


>>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
> :}.


see above, true cross compiler...

--Chuck