From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: hjl@lucon.org (H.J. Lu)
Cc: bug-libtool@gnu.org, gas2@cygnus.com,
ian@cygnus.com (Ian Lance Taylor),
gord@profitpress.com
Subject: Re: Why is libfoo.la is installed?
Date: Mon, 02 Mar 1998 11:50:00 -0000 [thread overview]
Message-ID: <orvhtwdgjs.fsf@iguacu.dcc.unicamp.br> (raw)
In-Reply-To: <m0y9aZE-00058fC@ocean.lucon.org>
H J Lu writes:
> libtool installs libfoo.la along with libfoo.so and libfoo.a. As the
> result, there are libbfd.la and libopcodes.la when "make install"
> is done on binutils. Is there a particular reason to install libfoo.la?
Certainly. Suppose libfoo is a library provided by your package.
Wouldn't you like other packages that build upon your library to get
correct library dependencies and run-time paths? These are stored in
the .la file, so it should be installed, so that libtool can use it
later. AFAIK, it currently doesn't such files from other packages,
but I believe it's intended to support this in the future.
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil
prev parent reply other threads:[~1998-03-02 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-02 11:08 H.J. Lu
1998-03-02 11:50 ` Alexandre Oliva [this message]
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=orvhtwdgjs.fsf@iguacu.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=bug-libtool@gnu.org \
--cc=gas2@cygnus.com \
--cc=gord@profitpress.com \
--cc=hjl@lucon.org \
--cc=ian@cygnus.com \
/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).