Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <3BEDFD26.7060806@ece.gatech.edu>
Date: Sat, 10 Nov 2001 23:23:02 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin-apps AT cygwin DOT com
Subject: Re: Move zlib up one level?
References: <20011111032226 DOT GA21492 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Christopher Faylor wrote:

> Would there be any objections to my moving cinstall's zlib directory to
> the same level as bz2lib, i.e., making it winsup/zlib?
> 
> I'd like to use some of its functionality in cygcheck.exe.


Yeah, but isn't cygcheck a cygwin1.dll application?  That would mean you'd 
need to (at least) compile libz.a twice anyway -- once as a cygwin "app" 
and once as a native "app", right?

Or can we build that static lib the same way both times (e.g. only build it 
once) since *static* libs CAN have unresolved externals (like "printf") and 
then trust the linker to "do the right thing" w.r.t. cygcheck and setup?

--Chuck