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
Message-ID: <40F4B550.7070205@cwilson.fastmail.fm>
Date: Wed, 14 Jul 2004 00:23:44 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115 MultiZilla/1.6.2.0c
MIME-Version: 1.0
Cc: cygwin AT cygwin DOT com
Subject: Re: gcc: How does gcc look for foo.dll in `gcc ... -lfoo'?
References: <000701c468f8$234c5640$4c62bcd4 AT ael> <9027008325 DOT 20040713190054 AT familiehaase DOT de>
In-Reply-To: <9027008325.20040713190054@familiehaase.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Gerrit P. Haase wrote:
> Alexey wrote:
> 
> 
>>I'm confused since the gcc documentation says that the only thing that
>>`-lfoo' does, is that it allows gcc to look for `libfoo.a' while linking.
>>But what about the shared libraries (DLLs)? It seems to me that gcc looks
>>for `libfoo.dll', `cygfoo.dll', `foo.dll' and may be for all these plus `.a'
>>suffix, doesn't it? But, for example, libfoo and cygfoo could be two
>>_different_ libraries at all. Can anybody explain the "-l" feature for DLLs?
>>I've tried the Cygwin's User Guide and gcc info, but did not find any
>>answer.
> 
> Given you have a library 'mfoo', then you should have a file libmfoo.a
> in /usr/lib which is the static archive in the default search path.  you
> specify this archive at the gcc link command with -lmfoo, if this
> library is a shared library, you should have also an import library
> /usr/lib/libmfoo.dll.a and a DLL /usr/bin/cygmfoo-2.dll, the default
> search order is /usr/lib, /usr/bin and then libmfoo.dll.a, libmfoo.a,
> cygmfoo.dll. 
> 
> So if you have just a static archive, it is found, if you have an import
> library and a static archive at first the import library is used (if
> not -static is used at the link command).  If the import library is
> used, ld knows how to find the correct DLL and links the application
> against the DLL using the import library.   If there is no static
> archive and no import library, then also /usr/bin is searched and also
> the cygmfoo.dll would be found, but if its actual name is cygmfoo/2.dll
> you would need to specify -lmfoo-2 at the link line to succeed the
> direct linking with the DLL.
> 
> Additionally you may specify the full name with path to link against:
> 
> gcc -o myapp.exe main_object.o /usr/lib/libmfoo.dll.a
> or
> gcc -o myapp.exe main_object.o /usr/lib/libmfoo.a
> or
> gcc -o myapp.exe main_object.o /usr/bin/cygmfoo-2.dll

Don't forget the -static option, which forces the compiler to ignore 
lib*.dll.a and cyg*.dll.

All of this is documented in the linker's documentation.  Do 'info ld'

--
Chuck


--
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/