Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: thing1-200.fsi.com: ford owned process doing -bs Date: Wed, 10 Mar 2004 09:38:06 -0600 (CST) From: Brian Ford X-X-Sender: ford AT thing1-200 Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: Creating DLL's for use with MSVC In-Reply-To: <20040310152944.GB5318@redhat.com> Message-ID: References: <20040310152944 DOT GB5318 AT redhat DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes On Wed, 10 Mar 2004, Christopher Faylor wrote: > On Wed, Mar 10, 2004 at 02:21:41PM +0100, Niklas Wallin wrote: > >When I try to link the .lib file with an MSVC executable it still can't > >find the references. I am not sure what to expect, should the lib, def > >and dll contain Cygwin decorated symbols (which is the case now) or the > >MSVC symbols? Or do I have to add any flags to the MSVC linker > >(compiler) to solve the name differences? > > http://cygwin.com/faq/faq_4.html#SEC120 I am probably wrong, as I'm sure cgf is *way* more knowledgable than I, but I got the impression this was no longer true via the list. Since Niklas is using gcc -mno-cygwin, this question is really off topic for this list. He would probably get better advice on the mingw-users list. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/