I have a general opensource packaging/build question that is sort of related to libtool (I think) and was hoping someone could answer it or provide me with a pointer.
For an opensource package that consists of one or more libraries and that uses configure, automake, libtool, and the usual packaging tools, is there a standard way to say that you want multiple versions of a library built? For example with GCC there are GCC specific variables and macros you set to build multiple versions of libgcc and put them in different directories; say a 32 bit version in one directory and a 64 bit version in another. I belive these macros are specific to GCC, and are not something handled generically by any tool used in the packaging of GCC and I was wondering if there was a more generic way of handling this for simpler packages? So for example, if I was shipping an opensource product that consisted of sources that get built into a single library and I wanted the user to be able to build two versions of that library, one 32 bits and one 64 bits, what would I do? Should I just tell the user to do two builds, with different options and different install directories? Or could I use the -print-multi-lib option on GCC to see what versions I should build? What if the user isn't using GCC? Or is there some better way to handle this that I don't know about? Is libtool even involved in this question at all? Steve Ellcey [EMAIL PROTECTED] _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool