how do I specify a static import library with a
*.lib extension to be used by libtool for resolving the symbols provided
by a non-libtool DLL when building a dependent DLL with libtool?
Any help would be appreciated even if I am doing something totally stupid,
wtj
as
set to the path of the .dll file but it was not loadable.
I should probably add that my DLL loader functions correctly for similar
libtool modules I build that do not require linking against any 3rd
party .lib files.
wtj
Earnie Boyd wrote:
Tim Van Holder wrote:
Bill Jones wrote:
So
appropriate to have libtool conform to that spec under Windows
(MinGW/Cygwin in particular) as I am sure that this will occur
frequently. Thanks for the response.
wtj
Tim Van Holder wrote:
Bill Jones wrote:
So the basic question is how do I specify a static import library with
a *.lib extension to
tj
Earnie Boyd wrote:
Tim Van Holder wrote:
Bill Jones wrote:
So the basic question is how do I specify a static import library
with a *.lib extension to be used by libtool for resolving the
symbols provided by a non-libtool DLL when building a dependent DLL
with libtool?
The trivial solution
g wrong is greatly appreciated.
wtj
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Bill Jones [EMAIL PROTECTED]
Mail Stop 125 Data Analysis and Imaging Branch
15 Langley Boulevard Systems Engineering Competency
NASA Langley Research Center
uses it
throughout libltdl. Therefore, you must use the LT_SCOPE macro for any
symbols in file.c that need also to be exported. An alternative is to
simply pass "--export-all-symbols" to GNU ld assuming that all symbols
need export.
wtj
Bill Jones wrote:
I am trying to build a DLL
this to be actually
fixed at some point? Is there a work around for using libtool
convenience libraries in building shared libtool libraries?
Any help would be appreciated,
wtj
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Bill Jones
