FYI: It is indeed possible to have libtool create static libraries even
when you provided --enable-shared and --disable-static to ./configure.
This happens for instance if you use options like:
libfoo_la_CFLAGS = -static
libfoo_la_LDFLAGS = -static
Regards,
Sander Niemeijer
On vrijdag,
> >>> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
>
> [...]
>
> Tim> It currently isn't; --enable-shared --disable-static
> still builds
> Tim> static libraries. There's a thread on the libtool
> mailing list about
> Tim> this; seems some people want this behaviour changed.
>
> Are
>>> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
[...]
Tim> It currently isn't; --enable-shared --disable-static still builds
Tim> static libraries. There's a thread on the libtool mailing list about
Tim> this; seems some people want this behaviour changed.
Are you sure?? AFAICT --dis
> > Norman> Also, note that if you include the declarations
> for building a shared
> > Norman> library, automake will automatically build the
> corresponding static
> > Norman> library [this is true, isn't it?]
> >
> > Honestly I don't know. Perhaps it's true, I guess it is, but
> > even
Alexandre,
On Thu, 31 Jul 2003, Alexandre Duret-Lutz wrote:
> Norman> You don't need to know anything about the structure of `.la' or `.lo'
> Norman> files (and they are subject to change), but it is these files that
> Norman> libtool and automake use to coordinate the dependencies in a packa
>>> "Norman" == Norman Gray <[EMAIL PROTECTED]> writes:
Norman> Alexandre, greetings,
Norman> On Wednesday, July 30, 2003, at 06:40 PM, Alexandre Duret-Lutz wrote:
>> Here is a second version of this section, so that we have
Norman> This looks great -- it's very clear indeed. As an ignoran
Alexandre, greetings,
On Wednesday, July 30, 2003, at 06:40 PM, Alexandre Duret-Lutz wrote:
Here is a second version of this section, so that we have
This looks great -- it's very clear indeed. As an ignorant user, I'm
much more confident that I know what's going on. I have a few comments.
--
Here is a second version of this section, so that we have
something cleaner in the archives. Beside including comments
from Guido, Harlan, and Tim, I've split the whole section into
shorter nodes (it was all on one node), and added a section
about `ltmain.sh not found'.
(Tim I'll post the Texinfo
>>> "gd" == Guido Draheim <[EMAIL PROTECTED]> writes:
gd> Just trying to get terminology to the point, note that developers
gd> from other platforms will most probably have known the term
gd> "linker script", so let's expand on that knowledge without
gd> driving away newbies.
Hi Guido! Thank
>>> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes:
[...]
Harlan> and immediately wondered if one could say:
Harlan> lib_LTLIBRARIES = libhello.la
Harlan> libhello_la_SOURCES = hello-common.c
Harlan> if LINUX
Harlan> libhello_la_SOURCES+= hello-linux.c
Harlan> else
Harlan> libhello_l
Ralf Corsepius wrote:
On Wed, 2003-07-30 at 09:30, Guido Draheim wrote:
Just trying to get terminology to the point, note that developers
from other platforms will most probably have known the term
"linker script", so let's expand on that knowledge without
driving away newbies.
FYI: I find the t
On Wed, 2003-07-30 at 09:30, Guido Draheim wrote:
> Just trying to get terminology to the point, note that developers
> from other platforms will most probably have known the term
> "linker script", so let's expand on that knowledge without
> driving away newbies.
FYI: I find the term "linker scrip
Tim Van Holder wrote:
platform dependent parts present in the ".libs" subdirectory.
(or "_libs" on platforms where filenames cannot start with a '.')
s|".libs"|".libs"/"_libs"|
:-)=)
btw, s|general concept|generalized concept| ?
-- guidohttp://AC-Archive.sf.
> platform dependent parts present in the ".libs" subdirectory.
(or "_libs" on platforms where filenames cannot start with a '.')
Just trying to get terminology to the point, note that developers
from other platforms will most probably have known the term
"linker script", so let's expand on that knowledge without
driving away newbies.
Alexandre Duret-Lutz wrote:
All these examples ought be backed up with test cases, but I
hav
Alexandre,
I noticed:
>Or we could simply use an Automake conditional as follows.
>
> lib_LTLIBRARIES = libhello.la
> if LINUX
> libhello_la_SOURCES = hello-linux.c hello-common.c
> else
> libhello_la_SOURCES = hello-generic.c hello-common.c
> endif
and immedia
This is an attempt to rewrite the "Building a Shared Library"
section of the manual, in order to answer some recent questions
about Libtool libraries (notably "gathering convenience
libraries", "conditional compilation using .lo files", and
"foo.lo build both with libtool and without").
All these
17 matches
Mail list logo
