This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: need some explanations about files ".a" ".la" ".dll.a"
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin at cygwin dot com
- Date: Wed, 05 Nov 2008 05:56:44 -0700
- Subject: Re: need some explanations about files ".a" ".la" ".dll.a"
- References: <49116DA1.4000803@gmail.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@byu.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/