Why not just write it as:
a_SOURCES = aprog/main.c \
aprog/foo.c \
aprog/bar.c \
aprog/baz.c ...
??
On Mon, Jul 17, 2023 at 12:55:59AM +0200, Jan Engelhardt wrote:
> Given
>
> a_SOURCES = aprog/main.c aprog/foo.c aprog/bar.c aprog/baz.c ...
>
> The more source files there ar
Hi Ralf and others,
I like to use a non-recursive makefile structure for my projects. However, if
the project also uses gettext, I end up having to constantly fight against both
gettext and auto{conf,make}.
If AM_GNU_GETTEXT appears in the configure.ac file, then automake refuses to
run, but g
The automake manual says:
Sometimes an info file actually depends on more than one .texi
file. For instance, in GNU Hello, hello.texi includes the file
gpl.texi. You can tell Automake about these dependencies using the
texi_TEXINFOS variable. Here is how GNU Hello does it:
info_TEXINFOS
By default, the info_TEXINFOS primary causes info files to be created
and installed uncompressed.
How can I change it so that compressed versions are installed instead?
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://pgp.mit.e
pkg.m4 doesn't behave in a very rational way, when configured with
--host=xyzzy
All the PKG_CHECK_MODULES macros continue to find the local modules,
not the ones for target xyzzy.Consequently, the build fails when
the compiler/linker can't find the header/library for the necessary
packages.
[ CCing to automake@gnu.org as this is an automake issue ]
I had similar problems after upgrading to automake-1.10, which
(because it wasn't available in Debian etch) I installed in /usr/local
whereas all the m4 macros were in /usr.
The solution I used was to create a file
/usr/local/share/acloca
On Wed, Jul 12, 2006 at 02:33:21PM +0200, Stepan Kasal wrote:
Hello,
On Wed, Jul 12, 2006 at 08:13:06PM +0800, John Darrington wrote:
> $(top_builddir)/subdir/mystuff.c: $(top_srcdir)/subdir/mystuff.x
> cp $(top_srcdir)/subdir/mystuff.x
$(top_builddir)/
My project is getting a number of complaints that the makefiles dont
work on BSD (and one or two other platforms). It seems that
automake generates non-portable makefiles when it comes to built sources.
Our build system is rather large, but a simplified one is somthing
like:
$(top_builddir)/
I've been trying to convert a rather largish automake controlled
project from a recursive style build system, to a non-recursive one.
I was rather suprised to see that automake decides to put all the
object files in the root directory; not only ugly, but destroys the
namespaces afforded by each dir
Recent versions of auto{make,conf} have become a pain to use.
Especially if you're using gettext too.
I think that some of these tools are trying to be just a little bit
too clever.
One particular problem is the way in which they modify each other's
input files. After a while, your Makefile.am lo
On Sun, Dec 07, 2003 at 09:24:30AM -0600, Bob Friesenhahn wrote:
On Sun, 7 Dec 2003, John Darrington wrote:
> Is there any way to instruct automake to only use relative pathnames
> in its makefile? This way, one could actually use the VPATH feature,
> which is
Is there any way to instruct automake to only use relative pathnames
in its makefile? This way, one could actually use the VPATH feature,
which is essential if you're building a project under certain CM
systems.
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285
On Wed, Dec 03, 2003 at 02:38:52PM -0600, Bob Friesenhahn wrote:
Does src1/foo.c exist?
Yes.
Are you using Automake 1.7.9?
No. I was using 1.7.6 and it seemed that atl_SOURCES=src1/foo.c
works fine with this version. So presumably the underscore thing was
introduced between 1.
On Tue, Dec 02, 2003 at 07:43:01PM -0600, Bob Friesenhahn wrote:
Based on my recent experience, non-recursive builds are working very
well in the current automake release. Use 'subdir-objects' in
AUTOMAKE_OPTIONS if you want the objects to be placed at the same
relative locat
Hi folks,
Is non-recursive currently supported in automake or is it still in
development/ideas stage? If it's already working, what version do I
need, and what documentation exists?
I've been trying to follow some threads in this list to gleem an
insight, but I joined late ... so I'd be obliged
With the new ftp upload procedures, shouldn't the automake targets be
changed appropriately? In particular:
The dist target should generate the package.tar.gz.asc file and the
dist-check target should verify that this signature is indeed valid.
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerp
16 matches
Mail list logo
