nel-all
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nel] libXML, the bane of my project...


From: Andi [ Debug ]
Subject: Re: [Nel] libXML, the bane of my project...
Date: Thu, 30 Sep 2004 08:14:08 -0500

this means you are missing the
 
iconv.lib
 
and
 
zlib.lib
 
libraries, if they are in your link path in visual studio add them to the list of libraries to link to.
 
you can compile libxml2 without these requiremetns using the options iconv=no and zlib=no
 
but i would keep at least the zlib
 
hope this helps sorry i cannot respond faster :)
 
----- Original Message -----
Sent: Thursday, September 30, 2004 7:36 AM
Subject: RE: [Nel] libXML, the bane of my project...

HI Andi,

 

  Thank you for your response. The libraries I compiled are static. Yes I used the static=yes option and my libraries are massively different in size:

 

Libxml2.lib = 230KB

Libxml2_a.lib = 2,65KB

 

  I changed the linking on the client project in the snowballs2 build to be (I am compiling in debug mode so I can do some debugging on future modifications):

 

freetype.lib libxml2_a.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 /incremental:no /pdb:"Debug/snowballs.pdb" /debug /machine:I386 /out:"Debug/snowballs.exe" /pdbtype:sept

 

  I then get the following errors:

 

--------------------Configuration: client - Win32 Debug--------------------

Linking...

MSVCRTD.lib(cinitexe.obj) : warning LNK4098: defaultlib "msvcrt.lib" conflicts with use of other libs; use /NODEFAULTLIB:library

libxml2_a.lib(xmlIO.obj) : error LNK2001: unresolved external symbol _gzopen

libxml2_a.lib(xmlIO.obj) : error LNK2001: unresolved external symbol _gzdopen

libxml2_a.lib(xmlIO.obj) : error LNK2001: unresolved external symbol _gzread

libxml2_a.lib(xmlIO.obj) : error LNK2001: unresolved external symbol _gzwrite

libxml2_a.lib(xmlIO.obj) : error LNK2001: unresolved external symbol _gzclose

libxml2_a.lib(xmlIO.obj) : error LNK2001: unresolved external symbol _deflateEnd

libxml2_a.lib(xmlIO.obj) : error LNK2001: unresolved external symbol _crc32

libxml2_a.lib(xmlIO.obj) : error LNK2001: unresolved external symbol _deflateInit2_

libxml2_a.lib(xmlIO.obj) : error LNK2001: unresolved external symbol _deflate

libxml2_a.lib(encoding.obj) : error LNK2001: unresolved external symbol _libiconv

libxml2_a.lib(encoding.obj) : error LNK2001: unresolved external symbol _libiconv_close

libxml2_a.lib(encoding.obj) : error LNK2001: unresolved external symbol _libiconv_open

libxml2_a.lib(xpath.obj) : error LNK2001: unresolved external symbol __ftol2

libxml2_a.lib(xpointer.obj) : error LNK2001: unresolved external symbol __ftol2

Debug/snowballs.exe : fatal error LNK1120: 13 unresolved externals

Error executing link.exe.

 

snowballs.exe - 15 error(s), 1 warning(s)

 

 I have attached the config file that I used to compile the libXML2 libraries with. As you can see I opted for all options including the static ones. If I am missing something please let me know. Its also weird that I don’t have this problem building any other part of NEL or NELS and most of the tools. I only have this issue with the Object Viewer and snowballs2.

 

  I am using libXML2 2.4.26, should I be using another version? I am looking at the link you sent and will see if there is anything there that may help. Thank you and I just wanted to make clear how I was compiling and what I was using to compile with.

 

 

Timoth H. Schilbach

Alpha Omega Design Inc.

address@hidden

Visit our website at www.aodinc.com

 


From: address@hidden [mailto:address@hidden] On Behalf Of Andi [ Debug ]
Sent: Thursday, September 30, 2004 12:20 AM
To: Developer's list for the NeL platform
Subject: Re: [Nel] libXML, the bane of my project...

 

that sounds like both libs are not static or more to the point that the _a is either not static or not being linked to...

 

did you compile it with the static=yes option?

also check you are modifying the right build mode

 

its no good changing the library to link against in debug build mode options then compiling in release debug for example you would be surprised how many people fall for that one. note it defaults to the ACTIVE build mode when you goto properties you should alter all modes to link to the correct library.

 

also you can ignore the nodefault library warning one OR the other option is to force the library you intended

 

 

this is a guide on how to do so.

 


_______________________________________________
Nel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/nel-all


_______________________________________________
Nel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/nel-all

reply via email to

[Prev in Thread] Current Thread [Next in Thread]