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: Fri, 11 Mar 2005 11:13:07 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: gcc/ ld/ Mixing C++ objects from gcc and msvc : possible link ? Message-ID: <20050311161307.GA28287@gully.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050309173223 DOT 505222101B7 AT warserver DOT warande DOT net> <20050309173442 DOT GB16830 AT gully DOT bosbc DOT com> <422F4DBA DOT 7020501 AT buddydog DOT org> <20050309200112 DOT GA17199 AT gully DOT bosbc DOT com> <422F63F7 DOT 2080100 AT buddydog DOT org> <78a9ab5d05031107377b3148e4 AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <78a9ab5d05031107377b3148e4@mail.gmail.com> User-Agent: Mutt/1.5.6i On Fri, Mar 11, 2005 at 04:37:36PM +0100, RzR www.rzr.online.fr wrote: >> > A foo.lib can be used interchangeably with a libfoo.a file. Except >Yea I did not realize that was just a convention (I was also confused >on cygwin : .so vs .dll) > >> > for the well-documented and frequently repeated problems with C++ >> > name mangling, and the even more repeated problems with mixing >> > the cygwin and msvcrt runtime libraries, there should be no problems >> > with using a .lib file on the gcc command line or a .a file on the >> > "cl" command line. >> == >> You cannot intermix non-trivial C++ (and, in many cases, even C) object >> files between compilers. >> == >> >> I'm not saying that it can't be done in some specialized circumstances, >... if it is not impossible, let's do it :) Great. *pause* It's done! Onto the next problem. cgf -- 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/