Hi Kevin,
I've run through the libtool code again, and I think that I was wrong
about the ML branch bypassing the part of libtool that drops static
libs. AFAICT, the ML branch simply adds the libraries it detected
from the internal C++ compiler link commands, and adds them to the
list of libraries that libtool's inter-library dependency analyzer
goes through. This means that libtool should be dropping the static
libs from the dependency list. Do you get a warning message from
Libtool such as:
*** Warning: This library needs some functionality provided by <some lib>.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
or do you get this warning:
*** Warning: Linking the shared library <some lib> against the
*** static library <some dep lib> is not portable!
Do you get any warning from libtool?
Thanks,
-Ossama
--
Ossama Othman <[EMAIL PROTECTED]>
Distributed Object Computing Laboratory, Univ. of California at Irvine
1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8
