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 X-Apparently-From: Message-ID: <3A75B107.4B884A32@yahoo.com> Date: Mon, 29 Jan 2001 13:05:59 -0500 From: Earnie Boyd Reply-To: Earnie Boyd X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: DJ Delorie CC: dfeustel AT mindspring DOT com, cygwin AT sources DOT redhat DOT com 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> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit DJ Delorie wrote: > > > It ocurred to me that, if there were a .lib file for the cygwin dll, > > that it could be linked in with and used by VS6 exes that were > > compiled using the cygwin headers. > > Cygwin is more than just a library. You can't build cygwin programs > with MSVC because MSVC will use the MS runtime; you need to use gcc to > use the cygwin runtime. Plus, cygwin isn't a .lib and probably never > will be a .lib. It's a .dll. > 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. Now, using the CYGWIN.LIB will be a different challenge and you'll have to manually do the linking to avoid MSVC standard includes and libraries. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple