www.delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-Spam-Check-By: | sourceware.org |
X-Authority-Analysis: | v=1.0 c=1 a=cTAtoGte6EoA:10 a=VhJ-Z-h-wfMA:10 a=xe8BsctaAAAA:8 a=7SFmJ-K2E_MM26pej7AA:9 a=H5HmkyfbrXC_sIUIeZQA:7 a=A83mMM9gWVSokNViP5hALJ_lRhQA:4 a=eDFNAWYWrCwA:10 a=rPt6xJ-oxjAA:10 |
Message-ID: | <4911980C.7040509@byu.net> |
Date: | Wed, 05 Nov 2008 05:56:44 -0700 |
From: | Eric Blake <ebb9 AT byu DOT net> |
User-Agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080914 Thunderbird/2.0.0.17 Mnenhy/0.7.5.666 |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: need some explanations about files ".a" ".la" ".dll.a" |
References: | <49116DA1 DOT 4000803 AT gmail DOT com> |
In-Reply-To: | <49116DA1.4000803@gmail.com> |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
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 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to ludo on 11/5/2008 2:55 AM: > In linux : > .../lib/libfoo.so is the equivalent of .../bin/cygfoo.dll > .../lib/libfoo.a is the equivalent of .../lib/libfoo.a > and there are no equivalent for libfoo.dll.a Correct so far... > and libfoo.la in linux ? Missed one. libfoo.la exists on Linux as well (in order for libtool to hide platform differences on how libraries are accessed, *.la files are an essential installation point. Some Linux distros prefer to strip .la files when installed into default locations, but there is a discussion on the libtool list right now how that is only hurting libtool's chances of getting everything right). > > when gcc links binaries, it uses only > .o files > .a files > .dll.a files > libfoo.la is a helper file only uses by libtool (not handled by gcc) : > is that correct ? Gcc can also link directly against *.dll, but yes, having *.dll.a in place aids its job. And yes, libfoo.la is only used by libtool. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkRmAwACgkQ84KuGfSFAYBO8wCglbXDmAvjV8OMdXip3/nuGSei aYsAn0NFe5tBVII4n4KV1ajpxcg9P0/7 =v7Kb -----END PGP SIGNATURE----- -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |