Bob Friesenhahn <[EMAIL PROTECTED]> wrote: > What is needed is a "database" which acts as a registry of installed > packages. This would be updatable by 'make install' as well as > binary packaging tools.
<URL:http://cr.yp.to/slashpackage.html> > A tool would be provided to formulate the optimum -I, -L, and -llibs > options required to build using a set of libraries. For the packages I've written, I have configurable paths to the other packages I need. Then the Makefile creates symlinks pointing to those paths. I use the symlinks' names for #include paths, linking, etc. > The database would need to be distributable across multiple prefixes > in order to handle the case where libraries are provided by the > system, installed to a common local directory, and installed in a > private directory. The system/common-local distinction isn't necessary with slashpackage. The private directory option is accounted for in some packages by the configurability of the paths to other packages. paul _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
