|
From: | Timothy H. Schilbach |
Subject: | RE: [Nel] libXML, the bane of my project... |
Date: | Thu, 30 Sep 2004 09:47:39 -0500 |
HI Andi,
Great response and dont worry about the response times. I took your
suggestion (as I have both current versions of zlib and iconv) and linked those
into my project:
freetype.lib libxml2_a.lib iconv.lib zlib.lib kernel32.lib user32.lib
gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib
oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows
/pdb:none /machine:I386 /out:"Release/snowballs.exe"
Great news is I have all but cut out all of my errors except for 4
of them:
--------------------Configuration: client - Win32
Release--------------------
Linking... libxml2_a.lib(xpath.obj) : error LNK2001: unresolved external symbol __ftol2 libxml2_a.lib(xpointer.obj) : error LNK2001: unresolved external symbol __ftol2 libxml2_a.lib(xmlschemastypes.obj) : error LNK2001: unresolved external symbol __ftol2 Release/snowballs.exe : fatal error LNK1120: 1 unresolved externals Error executing link.exe. snowballs.exe - 4 error(s), 0 warning(s)
I downloaded the libxml-2.6.11 release and compiled it with static
options and all libraries included. I then replaced all files in my include path
with the new ones and all but the remaining 4 errors exist now. This is an
awesome breakthrough as we have just one set of errors left, YAY!
Any idea what is causing the last ones? I am wondering what ftol2
connects too. I am looking that up in google now in homes to solve that last
error. Thank you once again for all the hep you have rendered. With any luck,
this will help others in the future :-)
-Timothy
|
[Prev in Thread] | Current Thread | [Next in Thread] |