Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> This is a new section I'd like to add to the FAQ. It has been
> discussed two or three times on the list.
It would be useful to have this in the Texinfo documentation for
GNU Make, not just for Automake.
oconf2.13
and (2) most of the time the proper version should be selected
automatically when you type "autoconf", as long as you install
both versions.
--
Ben Pfaff
email: [EMAIL PROTECTED]
web: http://benpfaff.org
Akim Demaille <[EMAIL PROTECTED]> writes:
> > Personally, I positively *like* "witness" - it describes what it is
> > in a colourful way.
>
> For the records, this is the official English word for the same
> concept in logic. A witness of an existential quantifier \exists
> x. P(x) is precisely
CFLAGS = -DFEATURE
>>
> ...
>> Where have I gone wrong?
>
> Of course, when my source files are C++ files the _CFLAGS extension does
> nothing. Changing this to _CPPFLAGS fixed the problem. Duh.
You know that CPPFLAGS is for the C preprocessor and CXXFLAGS is
Bob Friesenhahn <[EMAIL PROTECTED]> writes:
> On Tue, 24 Feb 2004, Ben Pfaff wrote:
>> >
>> > Of course, when my source files are C++ files the _CFLAGS extension does
>> > nothing. Changing this to _CPPFLAGS fixed the problem. Duh.
>>
>> You
I recommend reading the autoconf and automake lists via the NNTP
server at gmane.org, as the gmane.comp.sysutil.auto{conf,make}.*
groups. They filter spam for you and you don't have to screw
around with email subscriptions.
--
"Implementation details are beyond the scope of the Java virtual
mach
@ --or --other
Why use Autoconf for this? Just add a variable to Makefile.am:
SOME_TEST = $(top_builddir)/scripts/test/install/bin/something
check-local: check-something
check-something:
$(SOME_TEST) --or --other
--
Ben Pfaff
http://benpfaff.org
Automake "include" directive to
include that in each of your "Makefile.am"s. Personally I prefer
the latter. One sometimes-nice advantage is that modifying the
include file requires only rerunning Automake, which is faster
than rerunning Autoconf and Automake.
--
Ben Pfaff
http://benpfaff.org
ards.
It sounds (from this message and from other replies) that this is
not really trivial. So, I would write a separate shell script
that does everything needed properly and invoke that from the
Makefile. It's much easier, in my opinion, to write nontrivial
bits of shell in separate scripts than to try to maintain them
inside a Makefile.
--
Ben Pfaff
http://benpfaff.org
Eric Dorland <[EMAIL PROTECTED]> writes:
> * Alexandre Duret-Lutz ([EMAIL PROTECTED]) wrote:
>>
>> Eric:
>> | Is there any way you might consider dropping the
>> | Front and Back Cover Texts requirements from the manual?
>>
>> Sorry, this is the FSF policy. Not my call.
>
> Could you please poi
Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> Over the last weeks I've been writing an introductory chapter
> for the Automake manual. Now I could use some proofreading
> eyes, especially since I'm a foreigner. Other suggestions
> welcome too, of course.
I'm always amazed how well people w
e build directory corresponding to the
subdirectory of the source file. For instance, if the source file
is `subdir/file.cxx', then the output file would be
`subdir/file.o'.
In order to use this option with C sources, you should add
`AM_PROG_CC_C_O' to `configure.ac'.
--
Ben Pfaff
[EMAIL PROTECTED]
http://benpfaff.org
hey will be built only for "make check",
not for "make all" or "make install".
--
Ben Pfaff
http://benpfaff.org
d.
Is noinst_TEXINFOS unsupported? The manual says nothing about it
as far as I can tell. I see a 5-year-old patch that would have
added support for noinst_TEXINFOS:
http://thread.gmane.org/gmane.comp.sysutils.automake.patches/191
It appears to have never been applied.
--
Ben Pfaff
http://benpfaff.org
"Bobby Dill" <[EMAIL PROTECTED]> writes:
> pkgmaker_UI =
> sigcreatedlg.h
> sigcreatedlg.cpp
One obvious error is here: the first two lines should end in \.
--
"[Modern] war is waged by each ruling group against its own subjects,
and the object of the war is not to make or prevent conqu
he dh_compress program used in many Debian packages
automatically finds and compresses any Info documents and
manpages (and some other kinds of files) that are not already
compressed.
--
Ben Pfaff
http://benpfaff.org
#x27;gcc -E' init.o
mv init.o init.i
--
Ben Pfaff
http://benpfaff.org
Monty Taylor <[EMAIL PROTECTED]> writes:
> I've got a project that has 24 Makefile.am files. At the top of all of
> them at the moment, I've got:
>
> AM_CPPFLAGS = -I$(top_builddir)/include -I$(top_srcdir)/include
I tend to write "include $(top_srcdir)/Make.vars" at the top of
each Makefile.am, a
rmat. See:
[...]
> Should autotools add even more workarounds, or should rather
> simply BusyBox be fixed?
If only old versions of BusyBox do not support v7 tar format, as
Vincent implies, then BusyBox has already been fixed, and Nokia
just needs to upgrade to a current version.
--
Ben Pfaff
http://benpfaff.org
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> * Akim Demaille wrote on Tue, Sep 23, 2008 at 04:35:50PM CEST:
>>
>> I'm slowly getting rid of my recursive Makefiles. Instead I have one
>> local.mk per directory, and a few Makefile.ams that include them. Of
>> course I have to prefix all my fi
"Laura Hughes (lahughes)" <[EMAIL PROTECTED]> writes:
> My directory struct looks like this:
>
> topdir/
>src/
>src/basic_utilities
>src/ethernet_tests/bc5709_tests
>src/ethernet_tests/bc57711_tests
>src/mezzanine_card_tests
[...]
> AC_CONFIG_FILES([Makefile
>
Stefan Bienert writes:
> Could it be that a primary
>
> noinst_TEXINFOS
>
> does not work with automake 1.10.2?
This seems likely. I reported the same problem some time ago:
http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/4046
My report did not receive any r
Makefile.am in question:
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob;f=Makefile.am;h=dccb8cfdf92a3dd4dc9f3276e7533f68769587f8;hb=c2b070214097fa40dc78252882d96babe7fab4b4
Thanks,
Ben.
--
Ben Pfaff
http://benpfaff.org
[AM_INIT_AUTOMAKE([foreign])])
This seems to me more in keeping with the Autoconf philosophy.
--
Ben Pfaff
http://benpfaff.org
Ralf Wildenhues writes:
> * Ben Pfaff wrote on Fri, Aug 14, 2009 at 06:33:14PM CEST:
>> As an alternative, could Automake provide an API that allows
>> users to say "if feature X is supported, then expand this
>> configure.ac code"? For example:
>>
Bob Friesenhahn writes:
> Usually I don't care much about 'make clean' times but when I am
> chasing down compilation warnings I tend to do a lot of cleans.
When I'm chasing down compilation warnings I usually turn on
"-Werror" temporarily. Save
g
that some vendors have apparently not updated their C compilers
in that long.
--
Ben Pfaff
http://benpfaff.org
of it in the manual, but
it is sometimes convenient.
Thanks,
Ben.
--
Ben Pfaff
http://benpfaff.org
The question "libtool reorders link fags" seems to have a
spelling error in the last word. It's not obvious to me what
word is meant.
--
Ben Pfaff
http://benpfaff.org
"Too, Justin A." writes:
> However, Autoconf expands $#. How can I escape $#, so that it
> will remain as-is in the configure script? I just can't figure
> this one out :)
$[#] or $[@%:@] will avoid expansion.
(This is really an autoconf question.)
--
Ben Pfaff
http://benpfaff.org
non-recursive
subdirectories.
--
Ben Pfaff
http://benpfaff.org
Paul Lew <[EMAIL PROTECTED]> writes:
> I would like to propose we modify automake (and autoconf) to
> allow multiple versions of automake coexisting on a given
> system. [...]
You may want to have a look at my packaging of Autoconf 2.13 and
Autoconf 2.52 for Debian, which includes an heuristic t
Paul Lew <[EMAIL PROTECTED]> writes:
> >>>>> "Ben" == Ben Pfaff <[EMAIL PROTECTED]> writes:
>
> Ben> You may want to have a look at my packaging of Autoconf 2.13
> Ben> and Autoconf 2.52 for Debian, which includes an heuristic
&
33 matches
Mail list logo
