On Wed, 2009-10-07 at 07:56 -0400, Scott Lawrence wrote: > From a user perspective, I'd rather see this list be available as an > output of the existing sipx-config script (sipx-config --components). > That could be done similarly to what you've already done by having the > top level Makefile.am have a rule to create a file COMPONENTS that just > has the list of components in it, and then in the rule for building > sipx-config, incorporate that list in the localization step. This is > similar to what is already done for incorporating the build stamp > information.
Doing it precisely that way would not be particularly well-structured, as there isn't a good way to insert creating the file into the Makefile. Currently, the top-level Makefile is used only for sequencing build operations, and one need not execute it at all if one wants to build only one component. (And the buildstamps are not done that way -- the Makefile at the top of each component calculates the component's buildstamp.) I've implemented an alternative, which is to have the top-level configure.ac perform the substitution into the script. This requires that one execute the top-level ./configure before building sipXecs, rather than that one execute the top-level Makefile before building sipXecs, but the latter requires less work and fits better with (my) common workflows. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
