Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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, 9 Mar 2005 22:57:41 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
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?
Message-ID:	<20050310035741.GA31538@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> <6 DOT 1 DOT 2 DOT 0 DOT 0 DOT 20050309193453 DOT 020e1528 AT imap DOT myrealbox DOT com>
Mime-Version:	1.0
In-Reply-To:	<6.1.2.0.0.20050309193453.020e1528@imap.myrealbox.com>
User-Agent:	Mutt/1.5.6i

On Wed, Mar 09, 2005 at 07:48:58PM -0800, Tim Prince wrote:
>At 12:01 PM 3/9/2005, Christopher Faylor wrote:
>
>>A foo.lib can be used interchangeably with a libfoo.a file.  Except
>>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.
>>
>>In fact, I just tried it.  I created two MSVC object files, put them
>>in a .lib, and linked them with a program that I compiled using
>>gcc -mno-cygwin.
>>
>>Then I put the same two files in a ".a" and linked them using "cl".  You
>>will have to play around with the right libraries required to satisfy
>>things that mingw adds to an object file if you want to use msdev for
>>linking but this is not an insurmountable problem.
>>
>>Getting this working with object files compiled without -mno-cygwin
>>would be tricky (and maybe even not possible) but it's certainly
>>possible to use msvc created .lib files with gcc and gcc/ar created .a
>>files with msvc.
>
>When cygwin is used as a build environment for plain Windows compilers 
>(e.g. CL, IFORT), it insists on making libraries with its own ar 
>tool.  I've found it quite difficult to persuade it to use lib.  Maybe 
>because the Makefile wants to use the alias AR for lib, and we run afoul of 
>case insensitivity.

"It insists"?

"The Makefile"?

"the alias AR for lib"?

>64-bit objects in a library built by ar,

"64-bit objects"?

>BTW, I want to thank whoever made it so that cygwin runs right out of setup 
>now on the 64-bit Windows 180-day trial version.  No more editing of 
>cygwin.bat.

Uh.  Yeah.  No more editing.

I want to point out that cygwin likes pie both in the 32-bit and 64-bit variety.

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/

- Raw text -