Hello Charles,
Charles S. Wilson <[EMAIL PROTECTED]> wrote:
CSW> I don't believe the following behavior is possible in the current
CSW> libtool. However, if it is, please correct me.
CSW> In the upcoming libtool (1.4?) it would be nice on cygwin/windows-ish
CSW> platforms, if the libfoo.la file could instruct libtool that it may need
CSW> different -Ddefines when compiling an object file that is to be linked
CSW> to a static lib or to a dynamic lib (dll).
CSW> gcc -c -DZLIB_STATIC -o my-file.o myfile.c
CSW> gcc -static -o my-file.exe my-file.o -L<path> -lz
CSW> gcc -c -o my-file.o myfile.c
CSW> gcc -o my-file.exe my-file.o -L<path> -lz
This behaviour impossible simply because libtool is not used for
compiling client objects, only when compiling library objects, and
linking - both clients and libs. As you understand, it's probably
far-fetched to expect that libtool interface will be changed because
there's such a platform with such a stupid requirement. It is however,
can be trivially and more or less seamlessly worked around *on that
specific platform*, I use CC="libtool gcc" for that. But that
workaround is only one in a long sequence of workarounds which will be
required to support something more or less similar to features libtool
offers on any other platform, workarounds which will be required if
keeping up with stipulations prescribed by microsoft. But it's better to
strike the root of problems - get rid of necessity for __declspec.
CSW> --Chuck
--
Paul Sokolovsky, IT Specialist
http://www.brainbench.com/transcript.jsp?pid=11135
