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 Message-ID: <422F4DBA.7020501@buddydog.org> Date: Wed, 09 Mar 2005 14:25:46 -0500 From: Jonathan Arnold User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050202 MultiZilla/1.7.0.2d MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: req: using cygwin's gcc for creating static libs in msvc binary format (.a => .lib) # Re: static MSVC library? References: <20050309173223 DOT 505222101B7 AT warserver DOT warande DOT net> <20050309173442 DOT GB16830 AT gully DOT bosbc DOT com> In-Reply-To: <20050309173442.GB16830@gully.bosbc.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Christopher Faylor wrote: > On Wed, Mar 09, 2005 at 06:32:09PM +0100, Arend-Jan Westhoff wrote: > >>It looks like changing a lib.a into a lib.lib might require only a rename! >>(But I remember reading that debug formats differ between gcc and VC.) > > You're right. The only difference is the debug info. A cygwin .a file is > roughly the same thing as a MSVC .lib file. > > But, of course, that was true back in 1999, too. Yes, just because the *format* is the same doesn't mean you can use a LIB (or OBJ) file generated by one compiler when using another linker. In fact, I'd be willing to bet dollars to donuts that it cannot be done. This is due to lots of things, not the least of which is naming conventions, stack usage, and internal structure differences. Static libs are not, and never will be, cross-compiler, unless there is a specific switch in a compiler that says "Generate VC++ compatible object information" or some such. -- Jonathan Arnold (mailto:jdarnold AT buddydog DOT org) Amazing Developments http://www.buddydog.org I feel like a fugitive from the law of averages. - William H. Mauldin -- 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/