From: "Gary V. Vaughan" <gvv@techie.com>
To: Paul Sokolovsky <paul-ml@is.lg.ua>
Cc: Chris Faylor <cygwin@sources.redhat.com>
Subject: Re: Re[2]: DLL naming conventions
Date: Thu, 31 Aug 2000 18:05:00 -0000 [thread overview]
Message-ID: <20000831225258.Q7695@demon.co.uk> (raw)
In-Reply-To: <7593.000831@is.lg.ua>
On Thu, Aug 31, 2000 at 02:14:56PM +0300, Paul Sokolovsky wrote:
> [[snip]]
> I'm going to submit patch to libtool which (supposing it will be
> accepted) will make it use other naming scheme for PW32,
> posix-on-win32 layer I maintain. If it is in favor of Cygwin,
> community, I may do the same for cygwin too.
>
> Proposed naming conventions [only pertinent one shown]
>
> For some library 'foo', libtool will procude on
>
> Cygwin:
> libfoo.la - standard libtool wrapper
> libfoo.a - import library, thing against which objects are linked
> ("developer" part)
> cygfoo.<release>.dll - dll, this is what gets loaded in runtime
> ("user" part)
>
> Note that <release> is standard part of name of shared libraries
> produced by libtool. While it sequency of three arbitrary numbers,
> there's strictly recommended policy to using them - in two words, they
> should reflect interface version, never version of library itself. And
> yes, there's a way to disable putting it in name. Most packages don't do
> that, however.
> [[snip]
That's not how libtool works on cygwin -- remember that libtool only
want's you to see (and thus link against) the libfoo.la file. Behind
the scenes it maintains a static library, libfoo.a, and a dynamic
library, libfoo-<release>.dll. When you link against libfoo.la and
libtool decides you want dynamic linkage, it will generate an import
library from libfoo-<release>.dll *on the fly*.
I have no objections to using cyg instead of lib as the default prefix
for libtool built dlls on cygwin, but installing an import library
would be a step backwards IMHO. If you do want to install it (for
people who don't like libtool perhaps), I would suggest naming it
cygfoo.dll.a.
Cheers,
Gary.
--
___ _ ___ __ _ mailto: gvv@techie.com
/ __|__ _ _ ___ _| | / / | / /_ _ _ _ __ _| |_ __ _ ___ gary@gnu.org
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
\___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
home page: /___/ /___/ gpg public key:
http://www.oranda.demon.co.uk http://www.oranda.demon.co.uk/key.asc
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-08-31 18:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-30 3:36 Paul Sokolovsky
2000-08-30 7:26 ` Chris Faylor
2000-08-31 4:21 ` Re[2]: " Paul Sokolovsky
2000-08-31 8:56 ` Chris Faylor
2000-09-01 9:10 ` Re[2]: " Paul Sokolovsky
2000-08-31 18:05 ` Gary V. Vaughan [this message]
2000-08-30 7:48 ` Charles Wilson
2000-08-30 7:52 ` Chris Faylor
2000-08-30 8:07 ` Norman Vine
2000-08-30 8:17 ` Charles Wilson
2000-08-30 8:19 ` Charles Wilson
2000-08-30 11:37 ` Chris Faylor
2000-08-31 5:14 ` Re[2]: " Paul Sokolovsky
2000-08-30 8:11 ` Charles Wilson
2000-08-31 5:07 ` Re[2]: " Paul Sokolovsky
2000-08-31 8:58 ` Charles S. Wilson
2000-08-31 11:28 ` Re[2]: " Tor Lillqvist
2000-08-31 11:47 ` Chris Faylor
2000-08-31 12:07 ` Larry Hall (RFK Partners, Inc)
[not found] ` <20000831230822.R7695@demon.co.uk>
2000-08-31 18:58 ` Charles S. Wilson
2000-09-02 6:56 ` Gary V. Vaughan
2000-08-31 20:27 ` Charles S. Wilson
2000-08-31 6:52 Re[2]: " Earnie Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000831225258.Q7695@demon.co.uk \
--to=gvv@techie.com \
--cc=cygwin@sources.redhat.com \
--cc=paul-ml@is.lg.ua \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).