I've been generally seeing with favor the approach Rivet used to
delegate configuration and generation of build scripts to Makefile.am's
located in the directories where the actual code resides.
The task they are supposed to do is generally very easy though. This
approach eventually lead to a subtle problem with the distclean target
(yes, sometime it's useful to wipe out the whole set of generated files)
after the code was reorganized in order to have specific components
separated in different directories. The 'distclean' target assumes
rivetParser.so to belong to both the build processes in src/parser and
src/apache-2, as the same file is listed in both Makefile.am's. Since
the first in the execution chain removes the object, the second fails
attempting to delete a non existing file.
I reworked the src/Makefile.am so that all the whole machinery of
building librivet.so librivetparser.so and mod_rivet.so is now stored in
there.
There shouldn't be side-effects. Not committed yet, waiting for your
comments.
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
