On 11/27/2017 07:39 AM, Erik Bray wrote:
>
> One thing I might do differently from your proposal: I have some
> experimental code for an autoconf macro that can slurp in macros from
> multiple sub-directories. The idea being that you could put little
> .m4 files in each build/pkgs/<pkgname> dir with configure-time checks
> for that specific package, rather than cluttering up configure.ac with
> them. Perhaps I could try putting together a ticket for that...?
PHP does this with its extensions, all of which are optional and have
their own configure flags. There's a shell script that essentially does
for f in build/pkgs/*/*.m4; do
echo "include(${f})"
done
and then that shell script is executed in the top-level configure.ac
with esyscmd:
esyscmd(./path/to/that/script)
The result is that the "include" commands get inserted into the
top-level configure.ac file before processing.
On the other hand, if we standardize on the name of the m4 file (i.e.
it's fixed but optional), then you could use "sinclude" to grab them all
at once, ignoring the errors from the ones that don't exist.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
