>>> "Richard" == Richard Boulton <[EMAIL PROTECTED]> writes:
[...]
Richard> Surely one thing we could do is to implement wildcards
Richard> that are evaluated at the time that automake is run.
[...]
Richard> It is still true that it would be impossible to ensure
Richard> that the Makefile.in
>>> "Sean" == Sean Finney <[EMAIL PROTECTED]> writes:
[...]
Sean> - create a Makefile.am
Sean> - edit configure.ac (AM_INIT_AUTOMAKE and AM_CONFIG_HEADER)
Sean> - re-run aclocal
Sean> - re-run autoconf
Sean> - run automake (--foreign :^>)
`autoreconf' can do these three steps for you
Se
(This problem is taking on a life of its own, so I bit the bullet and
subscribed to the list...)
I need to backpedal a little on my earlier statement. Regarding eliminating
duplicate library targets, I said:
Commenting out the first two lines does get rid of the error message and
my bu
On Wed, 2002-04-10 at 16:57, Skip Montanaro wrote:
> I just installed autoconf 2.53 and as a result wound up installing the
> Release-1-6 snapshot from the automake CVS tree. Automake now complains:
>
> automake: src/Makefile.am: object `alf.lo' created both with libtool and without
The sam
On Wed, Apr 10, 2002 at 09:34:48AM +0200, Alexandre Duret-Lutz wrote:
> >>> "Sean" == Sean Finney <[EMAIL PROTECTED]> writes:
> Sean> - ./configure now tests for auto* and makeinfo
>
> Sean> is that really necessary?
>
> Yes. Automake create Makefiles that know how to rerun the auto*
> tool
On Wed, 2002-04-10 at 18:26, Tom Tromey wrote:
> Also wildcards wouldn't interact well with some automake features.
> That's because we need to do certain things statically to work around
> problems and missing features in vendor makes.
>
> As an example suppose you want to use per-executable CFL
Skip> lib_LIBRARIES = libalf.a
Skip> libalf_a_SOURCES = alf.c alf.h common.h
Skip> lib_LTLIBRARIES = libalf.la
Skip> libalf_la_SOURCES = alf.c alf.h common.h
Tom> In this particular case can't you just rely on libtool to create
Tom> the static library for you?
I don't kn
> "Timo" == Timo K Suoranta <[EMAIL PROTECTED]> writes:
Timo> Yes I have read those. I still do not understand the reason why
Timo> it is so,
Wildcards are unreliable, and with automake we try to promote reliable
builds. For instance that is why we use full instead of partial
dependency inf
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
Skip> lib_LIBRARIES = libalf.a
Skip> libalf_a_SOURCES = alf.c alf.h common.h
Skip> lib_LTLIBRARIES = libalf.la
Skip> libalf_la_SOURCES = alf.c alf.h common.h
In this particular case can't you just rely on libtool to create the
stati
[CCing Johannes who posted the very same question one week ago.]
>>> "Skip" == Skip Montanaro <[EMAIL PROTECTED]> writes:
Skip> I just installed autoconf 2.53 and as a result wound up
Skip> installing the Release-1-6 snapshot from the automake CVS
Skip> tree. Automake now complains:
Skip>
I just installed autoconf 2.53 and as a result wound up installing the
Release-1-6 snapshot from the automake CVS tree. Automake now complains:
automake: src/Makefile.am: object `alf.lo' created both with libtool and without
The relevant Makefile.am file is
lib_LIBRARIES = libalf.a
Schulfreunde,
Familienangehoerige,
Urlaubflirts, Bekanntschaften, Verzogene
Personen...
Title: ::: HANJAWA.COM Ãßõ ¸ÞÀÏ :::
WWW.HANJAWA.COM ÇÑÀÚ¿Í ´åÄÄ ¼Ò°³ ¸ÞÀÏÀÔ´Ï´Ù. Çѹø Àо½Ã±â
¹Ù¶ø´Ï´Ù.
Title: Secured Investements
Earn 15%-300% Interest On Your Money
GUARANTEED BY THE GOVERNMENT!
Government Secured Tax Cerificates Provide:
The highest guaranteed interest returns compared to any other investment.
A return up to 100 times your mo
Yes I have read those. I still do not understand the reason why it
is so, but I think I can live with it by making the work around
scripts. Unfortunately I am very unexperienced script writer so I
was hoping someone already had such script.
> Timo> My problem is that my current Makefile.in use
>>> "BERTRAND" == BERTRAND Joël <[EMAIL PROTECTED]> writes:
[...]
BERTRAND> How can I force libtool to include the external
BERTRAND> libraries use by librpl in librpl ?
Since no one answered you should probably try to ask the
[EMAIL PROTECTED] people. (Personally I thought it was enough
to
>>> "Sean" == Sean Finney <[EMAIL PROTECTED]> writes:
Sean> hey all--
Sean> A few weeks ago I began the transition over to autoconf/automake by
Sean> taking my semester's project and incorporating autoconf into the
Sean> package. everything works really fine, only now I'm having trouble
Sea
17 matches
Mail list logo