> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
Ralf> Am Don, 2002-01-31 um 22.31 schrieb Alexandre Duret-Lutz:
>> >>> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
>>
Ralf> Am Don, 2002-01-31 um 17.27 schrieb Russ Allbery:
>> [...]
>>
>> >> Why are you lowercasing the package
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
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
>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
Am Fre, 2002-02-01 um 12.33 schrieb Akim Demaille:
> > "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
>
> Ralf> Am Don, 2002-01-31 um 22.31 schrieb Alexandre Duret-Lutz:
> >> >>> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
> >>
> Ralf> Am Don, 2002-01-31 um 17.27 schrieb Russ
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'
Ralf Corsepius wrote:
>
> BTW, I would appreciate the other autoconf and automake maintainers to
> speak up, because apparently a reasonable discussion between Akim and me
> doesn't seem to be possible anymore.
First let me say that IANAAM (I Am Not An Autoconf Maintainer) but I'm
going to give
> 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 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
Earnie Boyd wrote:
> ... But let's stand back and look at what we have:
>
> 1) ... 2) ... 3) ... 4) ... 5) ...
What we *really* have are more very good reasons to coordinate
auto* tool releases. Even, perhaps, to the point of having
coordinated tags in the CVS repositories? Anything but
surpr
Bruce Korb wrote:
>
> Earnie Boyd wrote:
>
> > ... But let's stand back and look at what we have:
> >
> > 1) ... 2) ... 3) ... 4) ... 5) ...
>
> What we *really* have are more very good reasons to coordinate
> auto* tool releases. Even, perhaps, to the point of having
> coordinated tags in the
> ">" == =?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
> ">" == =?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:
>> 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
> "Daniel" == Daniel Shane <[EMAIL PROTECTED]> writes:
Daniel> I have a recursive automake installation and I would like to
Daniel> have make go into each subdirectory and execute some code
Daniel> before and after the recursion. Is this possible with
Daniel> automake?
I don't think it is p
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> Automake names PACKAGE what Autoconf name PACKAGE_TARNAME. In
Akim> addition, Autoconf support PACKAGE_NAME. Because in many cases
Akim> PACKAGE_TARNAME can be computed from the PACKAGE_NAME, such a
Akim> _default_ is provided. If
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> Aside: some people use
adl> AM_INIT_AUTOMAKE([AC_PACKAGE_TARNAME], [AC_PACKAGE_VERSION])
adl> (this won't work with Automake in --gnits mode, though)
If this is a common idiom, we could support it.
I'm inclined to ignore it,
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
Tom> Automake used PACKAGE with a specific meaning for years. It is
Tom> unfortunate that Autoconf has chosen to use the same name with a
Tom> different meaning. But I don't wish to belabor this point.
Of course, it would be idiotic for me
18 matches
Mail list logo
