Re: C++ transition stumbling blocks?
Scott James Remnant <firstname.lastname@example.org> writes:
> On Thu, 2003-01-30 at 17:02, Matt Zimmerman wrote:
> > On Thu, Jan 30, 2003 at 12:44:17PM +0900, Miles Bader wrote:
> > > Scott James Remnant <email@example.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.
> In your configure.in put
You seem to lack understanding what the problem is: how to disable
static building for a *specific* library (e.g plugin), not all in the
Andreas Rottmann | Dru@ICQ | 118634484@ICQ | firstname.lastname@example.org
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