Hi,
I am finally reaching the end of my autotoolization of my program but
I still have two questions I think will be easy to solve but I can not
figure out how to do it...
1st: I have a multiple subdirectories project. One of those directories
stores again multiple subdirectories. In each of
hi,
For the second question, you can use the $(top_srcdir)
variable and give the complete path of your library.
example:
2Dinterpolation_LDADD =
$(GLIB_CFLAGS) \
$(top_srcdir)/src/errors/libErrors.a \
$(top_srcdir)/src/lib/libLib.a
with
Hi,
Santosh [EMAIL PROTECTED] writes:
For the second question, you can use the $(top_srcdir)
variable and give the complete path of your library.
example:
2Dinterpolation_LDADD =
$(GLIB_CFLAGS) \
$(top_srcdir)/src/errors/libErrors.a \
Thank you for correcting me.
with regards,
Santosh.
On Tue, 17 Jun 2003, Raja R Harinath wrote:
Hi,
Santosh [EMAIL PROTECTED] writes:
For the second question, you can use the $(top_srcdir)
variable and give the complete path of your library.
example:
Jose Roman Bilbao [EMAIL PROTECTED] writes:
1st: I have a multiple subdirectories project. One of those directories
stores again multiple subdirectories. In each of them a librtary
(shared) is built and stored in .lib (local) directory. Te thing is that
I would like all my libraries to be
It looks like the libs.am is setting AR = ar (I am
using version 1.5 of automake). This eventrually gets
inserted in Makefile.in, when libraries are being
created. This seems to override any other
initialization done by the user for AR. Does this mean
that the user cannot set AR ?
Thanks,
DH
D H [EMAIL PROTECTED] writes:
It looks like the libs.am is setting AR = ar (I am
using version 1.5 of automake). This eventrually gets
inserted in Makefile.in, when libraries are being
created. This seems to override any other
initialization done by the user for AR.
make AR=my-ar should just
I'm currently running automake 1.5 and autoconf
2.53. I would like to upgrade to 1.7.5 and 2.57 respectively. I
don't have a need to keep the old versions, so upgrading over them would be my
first choice. I want to make extra sure that I won't break anything in the
upgrade process (i.e. not
Alexandre
Thanks for the info. I really appreciate it. What is the easiest way
then to tell system to go to a different directory to build a dependency
if it is not built yet??
By the way, if you don't mind me asking, what is the point of
_DEPENDENCIES when you can just add library to _LDADD
Joel Apter [EMAIL PROTECTED] writes:
matter). Would a simple configure, make, make install be all that is
necessary for both automake and autoconf (autoconf before automake
since it appears that autoconf 2.54+ is required to install automake
1.7.5). Thank you for your time.
Yes. And then
Hi,
[EMAIL PROTECTED] writes:
By the way, if you don't mind me asking, what is the point of
_DEPENDENCIES when you can just add library to _LDADD
and Autotools will update dependency list automatically from that???
Usually, there's no point. However, there can be cases where
automake cannot
comes from the Gnits standards.
There is no such thing as Gnits standards. I was/am a founding member
of gnits (which was just a few friends talking informally), and I can
state this authoritatively :).
Before automake existed, there were various
autoconf/installation/etc. conventions that
The original message was received at Tue, 17 Jun 2003 23:07:55 -0400 (EDT)
from rly-xe01.mail.aol.com [172.20.105.193]
*** ATTENTION ***
Your e-mail is being returned to you because there was a problem with its
delivery. The address which was undeliverable is listed in the section
labeled:
Davy Durham [EMAIL PROTECTED] writes:
These files are listed in the DIST_COMMON (at least I'm pretty sure
DIST_COMMON is where these files are coming from in the cp commands)
so I'm not explicitly listing them myself anywhere to be distributed.
I've tried several versions between and including
14 matches
Mail list logo
