-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Alexandre,
Alexandre Duret-Lutz wrote: >>>>"Tom" == Tom Howard <[EMAIL PROTECTED]> writes: > > > [...] > >>>> don't use include. Instead try to use AC_SUBST_FILE, or (IMHO better) > >>>> something like AC_CONFIG_FILES([Makefile:Makefile.in:fragment.mk]). > [...] > Tom> automake complains that fragement.mk is not found. I can just touch the > Tom> file before running autoreconf, but is there a nice way to tell automake > Tom> that it can ignore that this files is missing? > > No. If Automake requires a file, it's because it wants to > distribute it. If fragment.mk is generated, it should not be > distributed (touching the file or adding rules will not prevent > this). > > In 1.9.x, the only way Automake can recognize that the input > file of an AC_CONFIG_FILES is generated is if this input file is > also the output file of another AC_CONFIG_FILES. > > In the future Automake 1.10 you should be able to hide arbitrary > inputs to Automake using shell variables, but this workaround > not work with 1.9.x. (I'm appending the 1.10 documentation for > AC_CONFIG_FILES for reference.) > > I guess that leaves you with AC_SUBST_FILE... Dang. The AC_CONFIG_FILES technique is much nicer (less files to change). Are there some bad side effects of using touch fragment.mk && autoreconf that I'm not aware of? > Or maybe explain > what is the actual problem you are trying to solve, in case > somebody has a solution? Sorry, though I did. I'm generating fragment.mk (actually it used to be called aminclude.am and now I'm calling it include.mk, but the name of the file doesn't matter) from some autoconf macros and would like to have fragment.mk appended to each Makefile in the project. There is no secrecy intended, you can check out the first attempt at what I'm trying to do in the "automake support" (poorly named; my bad. Will try to rename to something like "make extensions") section of the gnu autoconf archive <http://www.gnu.org/software/ac-archive/macros-by-category.html#AUTOMAKE>. Basically they add make targets to automate stuff like committing to cvs (creates a template ChangeLog entry for you and uses it for the commit log), making a release (adds appropriate ChangeLog entry, tags it in cvs, and updates the version number), make rpms (creates the files list for the spec file for you and converts the ChangeLog to a suitable format for the spec file, before creating the actual rpm), etc. Cheers, - -- Tom Howard Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x433B299A -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCB/xew1G4ZUM7KZoRAkM3AKCy9Najy7RY03LFzAKJcLrvJeC3DQCgqLcy MgE8CCQeAGXcqiFWX/7wxKw= =L/TL -----END PGP SIGNATURE-----
begin:vcard fn:Tom Howard n:Howard;Tom email;internet:[EMAIL PROTECTED] tel;work:+61 2 8218 1500 tel;fax:+61 2 8218 1507 tel;cell:+61 402 756685 note;quoted-printable:Public Key: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0x433B2= 99A=0D=0A= =0D=0A= Microsoft Messenger ID: [EMAIL PROTECTED] Yahoo! Messenger ID: bjandtomau x-mozilla-html:FALSE version:2.1 end:vcard
