Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 29 Jan 2001 13:09:22 -0500 Message-Id: <200101291809.NAA10503@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: cygwin AT cygwin DOT com CC: dfeustel AT mindspring DOT com, cygwin AT sources DOT redhat DOT com In-reply-to: <3A75B107.4B884A32@yahoo.com> (message from Earnie Boyd on Mon, 29 Jan 2001 13:05:59 -0500) Subject: Re: Cygwin lib files References: <20010126173102 DOT 3803 DOT qmail AT web1902 DOT mail DOT yahoo DOT com> <00ff01c089fa$51865000$275c100a AT actfs DOT co DOT uk> <010e01c089fb$a825cca0$6701a8c0 AT dafcor1qondarn> <200101291745 DOT MAA10219 AT envy DOT delorie DOT com> <3A75B107 DOT 4B884A32 AT yahoo DOT com> > But, that doesn't mean you couldn't use the MSVC utilities to create an > import library named CYGWIN.LIB if you want to go to the trouble and > there will be problems giving you trouble I would assume. Note there > are static items also in libcygwin.a and those static items will need to > exist in your CYGWIN.LIB. Except that cygwin1.dll knows the difference between being invoked by an import library and being invoked by LoadLibrary, and initializes itself differently for each. I wouldn't expect it to work correctly if you used a plain import library without all the other initialization stuff that the default libcygwin.a provides. Someone would have to review it in depth to know if it would work at all, and commit to keeping it working. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple