On 18-04-12 14:20, SF Markus Elfring wrote:
Can this limitation be changed if the macro call
"AM_INIT_AUTOMAKE([foreign -Wall -Werror])" would be added to the
configuration specification?
We are not using automake - just autoconf. What actually worked is
writing an empty toplevel Makefile.am that specifies the correct
parameters for aclocal. Autoreconf promises to read that parameter,
while on the other hand not preprocessing the file when the file is not
referenced from configure.ac.
So, it's now (next release candidate) possible to regenerate all that
using autoreconf (e.g. autoreconf --force). But, I'll advice against
that and would just use the generated configure script...
How do you think about adjustments like the following?
- Replace command with backticks by "$(cat ./version)"
It's already changed to m4_esyscmd, which is the only allowed official
way in this particular context:
m4_esyscmd([cat ./version | tr -d '\n'])
There is an important semantic difference between this macro and
backticks/subshell: the execution of the latter would be delayed until
the version variable is used somewhere, whereas here you actually want
to have the version number.
Update: I just received your other email: yes, we do it now like that.
- Addition of the macro calls "AC_CONFIG_AUX_DIR([build.aux])" and
"AC_CONFIG_MACRO_DIR([m4])"
The latter one is convenient to add, so that I can move some files to
the setup subdir. The former one does not seem relevant, but why not, I
added it anyway.
- Pass the file names for the macro "AC_CONFIG_FILES" in one call
- Delete the lines 438-440
Can't hurt. Couple of characters less code...
Thanks.
Arie
_______________________________________________
Cocci mailing list
[email protected]
http://lists.diku.dk/mailman/listinfo/cocci
(Web access from inside DIKUs LAN only)
