On Mon, 16 Aug 2004, Gary V. Vaughan wrote:
Hi Bob, Joe, libtoolers:
Bob Friesenhahn wrote:It seems that the only valid test to determine the default output architecture is to compile code and then use 'file' or some other utility to determine the architecture. In order to produce multilib output, libtool would need to know the specific options necessary to obtain each desired variant. These options are compiler and linker specific.
I agree. Much like the options to produce shared libraries at all involves compiler and linker specific options :-) This is libtool's raison d'etre, and we should aim to have support for multilib in our roadmap. It has been in our TODO file for as long as I've been involved with libtool (pushing 7 years now).
When building a multilibed library, a variant of the library could be built for every possible architectural option, or a subset of the libraries could be built. It seems to me that being able to choose from a subset of possible library build options is valuable since many build options may offer no value to the user. I am not sure how options would be presented to the installer of the package, but it should be as easy as possible to select which variants are build, and it should even be possible for the person who installs the library to define custom multilib variants to satisfy local requirements.
Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen
_______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/libtool
