Re: C++ transition stumbling blocks?
Matt Zimmerman <mdz@debian.org> writes:
> On Thu, Jan 30, 2003 at 12:44:17PM +0900, Miles Bader wrote:
>
> > Scott James Remnant <scott@netsplit.com> writes:
> > > > Can you tell it to not use/produce shared libraries at all (e.g., just
> > > > use traditional static libraries)?
> > >
> > > If you're using libtool from within automake:
> > >
> > > lib_LTLIBRARIES = libhello.la
> > > libhello_la_LDFLAGS = -static
> >
> > Actually I think the problem was that the package I had problems
> > with had been distributed with a very old version of libtool;
> > after updating to something more recent, I can use the
> > --disable-shared and --enable-static configure switches to get
> > what I want.
>
> Speaking of which...is there any way to force building only a shared
> library, without using --disable-static? flac, for example, builds both a
> normal shared library (shared and static versions) and a plugin (which makes
> no sense static, and would be a pain to link statically). Currently, it
> uses separate libtools to build the two libraries, which seems silly.
>
Yes, this would indeed by a nice libtool feature. Could cut down build
time and disk space for quite a few packages /methinks.
Regards, Andy
--
Andreas Rottmann | Dru@ICQ | 118634484@ICQ | a.rottmann@gmx.at
http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Reply to: