&Sgr;&tgr;&igr;&sfgr; &Sgr;&aacgr;&bgr;&bgr;&agr;&tgr;&ogr; 02 &PHgr;&egr;&bgr;&rgr;&ogr;&ugr;&aacgr;&rgr;&igr;&ogr;&sfgr; 2002 09:19, &ogr;/&eegr; Tom Tromey &eacgr;&ggr;&rgr;&agr;&psgr;&egr;:
> > ">" == =?iso-8859-7?b?wevd7uHt5PHv8iDK4fH18N/k5/I=?= (Alexandros
> > Karypidis) writes:
> >
> >> I have found a workaround. It seems that automake generates a rule
> >> to build a library, only if XXX_la_SOURCES is defined.
> >>
> >> libgather_la_SOURCES = gather.c
> >> The gather.c is an empty file (created with "touch gather.c").
> >> Is there a way to make this work without the gathe
> >> From the autobook:
> >> `_LIBADD': Like `_LDADD', but used for static libraries and not
> >> programs.
>
> At first I thought this was a bug in the book.
> Then it looked like a bug, and then like an undocumented change.
>
> But now I think maybe the docs (both book and automake.texi) have
>
> ">" == =?iso-8859-7?b?wevd7uHt5PHv8iDK4fH18N/k5/I=?= (Alexandros Karypidis)
> writes:
>> I have found a workaround. It seems that automake generates a rule
>> to build a library, only if XXX_la_SOURCES is defined.
>> libgather_la_SOURCES = gather.c
>> The gather.c is an empty file (creat
> ">" == =?iso-8859-7?b?wevd7uHt5PHv8iDK4fH18N/k5/I=?= (Alexandros Karypidis)
> writes:
>> make[2]: rpath: Command not found
This means some macro, I think $(LIBTOOL), didn't get defined.
What version of automake are you using?
Tom
> ">" == =?iso-8859-7?b?wevd7uHt5PHv8iDK4fH18N/k5/I=?= (Alexandros Karypidis)
> writes:
>> From the autobook:
>> `_LIBADD': Like `_LDADD', but used for static libraries and not programs.
At first I thought this was a bug in the book.
Then it looked like a bug, and then like an undocumented
I have found a workaround. It seems that automake generates a rule to build
a library, only if XXX_la_SOURCES is defined. So the following doesn't work:
SUBDIRS = lib1 lib2 .
lib_LTLIBRARIES = libgather.la
libgather_la_SOURCES =
libgather_la_LIBADD = lib1/libgoodbye1.la lib2/libgoodbye2.la
B
> I'm not distinguishing between dynamic & static. Libraries are libraries.
I suppose you are correct. That's supposed to be the whole purpose of
libtool after all. Anyway, as you suggested, I'm focusing on:
libgather_la_LIBADD = lib1/libgoodbye1.la lib2/libgoodbye2.la
Now, the only relevant
I'm not distinguishing between dynamic & static. Libraries are libraries.
An example from CVS libwmf:
libwmf_la_LIBADD = libwmflite.la ipa/libipa.la $(LIBGD) $(LIBTRIO)
where libwmflite.la is not convenience but the other three are. Generally
all are built as static & shared libraries, but that'
>From the autobook:
`_LIBADD': Like `_LDADD', but used for static libraries and not programs.
...and I want to create a dynamically library. Anyway, in either case the
subsequent make fails and I get:
when using "libgather_la_LIBADD = lib1/libgoodbye1.la lib2/libgoodbye2.la"
make[2]: Enterin
On Fri, 1 Feb 2002, [iso-8859-7] ÁëÝîáíäñïò Êáñõðßäçò (Alexandros Karypidis) wrote:
> I am trying to understand how convenience libriaries work. Using the dir
> structure "project/src/libX", where X is 1 & 2, I want to create 2
> convenience libraries in project/src/lib1 & project/src/lib2, th
I am trying to understand how convenience libriaries work. Using the dir
structure "project/src/libX", where X is 1 & 2, I want to create 2
convenience libraries in project/src/lib1 & project/src/lib2, then merge them
into a shared library in project/src. So I wrote the following 3 Makefile.a
12 matches
Mail list logo
