Can anyone tell me whether any work has been done in libtool to better support cross-compile environments?
I'm working in such an environment where _ALL_ of our code is generated by cross-compilers. For various reasons a chroot solution is not practical for us, so we are constantly installing things into "image trees" which are complete root filesystems, but instead of being rooted at "/" they are rooted at $ROOT (which is variable). We manage to work quite straightfowardly with all they autotools _EXCEPT_ libtool; libtool is a constant source of frustration for us in our environment. It is so bad that we cringe whenever we need to integrate a 3rd party library that uses libtool. There is no way to parameterize or override the data in the .la file, and trying to follow the convoluted logic at the intersection of autoconf and libtool is virtually impossible. Although packages using old-time shared library configurations are sometimes more complicated for the user to set up, they are virtually always more flexible and can be worked into our environment without much hassle, so we prefer it. Admittedly we are currently using libtool 1.4.3 which is 11 months old or so. I've looked at the newest (1.5.10) documentation and NEWS files and there is no mention of any cross-compilation capabilities. I'm wondering if there is any attempt to better support it in the 2.x versions? -- ------------------------------------------------------------------------------- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org "Please remain calm...I may be mad, but I am a professional." --Mad Scientist _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/libtool
