Re: Status of non-recursive automake
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.7.6 and 1.7.9 J' -- PGP Public key ID: 1024D/2DE827B3 fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://wwwkeys.pgp.net or any PGP keyserver for public key. pgp0.pgp Description: PGP signature
Re: Status of non-recursive automake
On Thu, 4 Dec 2003, John Darrington wrote: 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.7.6 and 1.7.9 The underscore rule applies to the names to the *left* of the '=', not the right. Paths on the right are just fine. If your target library/program resides in a subdirectory, you will soon experience what I have been complaining about. :-) Bob == Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen
Re: Status of non-recursive automake
On Wed, 3 Dec 2003, John Darrington wrote: 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? 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 location as the source files. An issue with the 'clean' target has been reported for the case where the makefile is also recursive (SUBDIRS is used). Objects get unnecessary funny naming in the case where TARGET_CPPFLAGS is used but this doesn't seem to break anything. Since the '/' in target definitions are not make syntax compatible, all the '/'s in target definitions need to be manually smashed to '_'. This is very tedious and error prone, and is something that Automake should fix. Bob == Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen
Re: Status of non-recursive automake
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 location as the source files. An issue with the 'clean' target has been reported for the case where the makefile is also recursive (SUBDIRS is used). Objects get unnecessary funny naming in the case where TARGET_CPPFLAGS is used but this doesn't seem to break anything. Since the '/' in target definitions are not make syntax compatible, all the '/'s in target definitions need to be manually smashed to '_'. This is very tedious and error prone, and is something that Automake should fix. Is there anything else that's required? I made a simple Makefile.am : AUTOMAKE_OPTIONS=subdir-objects bin_PROGRAMS=atl atl_SOURCES=src1_foo.c src2_bar.c But the resulting Makefile produces: make: *** No rule to make target `src1_foo.c', needed by `src1_foo.o'. Stop J' -- PGP Public key ID: 1024D/2DE827B3 fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://wwwkeys.pgp.net or any PGP keyserver for public key. pgp0.pgp Description: PGP signature
