Torsten Kurbad wrote:
Hi,
I'm currently maintaining the binary builds (eggs) of python-ldap
(http://python-ldap.sf.net). So far I built the Windows versions using
MingW, and therefore have to deliver an extra package of DLLs (sasl,
OpenLDAP, openssl, ...).
To circumvent this, I now try to build everything statically using
Visual Studio .NET. For some parts, e.g. openssl, this works like a
charm, but trying to build static cyrus-sasl-libs I ran into problems.
To build the library, I introduced a new target in lib/NTMakefile:
libsasl.lib: $(libsasl_objs) $(libsasl_res)
lib /out:"libsasl.lib" /subsystem:console \
$(SYS_LIBS) $(EXTRA_LIBS) $(libsasl_objs) $(libsasl_res)
Doing so (and leaving out the .dll part, that would indirectly build
libsasl.lib as an import library, everything seems fine. But as soon as
I try to link against libsasl.lib, I get:
saslpasswd.obj : error LNK2019: unresolved external symbol __imp__sasl_errstring
referenced in function _exit_sasl
Hi,
Dunno if you've already solved the problem?
Those __imp functions are related to DLL import, ie. you need to change
with the includes so that they do not "declspec(dllimport)" the functions.
Your other problem is that you also need the plugins compiled in
statically. Previously this wasn't supported for the win32 build. I made
a patch for an older version some years back, but I seem to have lost
it, I'll see if I can find it again.
/Mvh Morten
--
Morten Sylvest Olsen, System Developer
Medical Insight A/S, Krumtappen 4,3.th,2500 Valby, Denmark
Phone:+4546550444, Mobile:+4551573092,Mail: mso@xxxxxxxxxxxxxxxxxxx
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Some people, when confronted with a problem, think "I know, I'll use XML"
Now they have two problems.
-- Usenet true-ism
