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 Date: Wed, 10 Mar 2004 11:07:07 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Creating DLL's for use with MSVC Message-ID: <20040310160707.GE5318@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <20040310152944 DOT GB5318 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Reply-To: cygwin AT cygwin DOT com On Wed, Mar 10, 2004 at 09:38:06AM -0600, Brian Ford wrote: >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 at lists dot sourceforge dot net> list. The last I saw, there was a big discussion about this on the gcc mailing list and everyone agreed that gcc was not going to change anytime soon. As always, it is possible to link some C objects between MSVC and gcc. It isn't possible to link C++ objects which export symbols. However if you think this has changed why not post a URL which explains how this came to be? -- 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/