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

[Timothy H. Schilbach]

HI andi,

 

  Well that did it!

 

  I added that code snippet to the following file (top of them)

 

xmlschemastypes.c

xpath.c

xpointer.c

 

  And recopiled them. Seems to have taken care of the issue. I also learned this important lesson in working with VC++.

 

1.  If you compile libraries using VC 7.1 and then try and use them in a VC++ 6.0 project, you will get the ftol2 errors since ftol2.obj is a part of VC 7.1 and is used in the background when compiling in VC 7.1. Since I did not have access to the libraries that VC 7.1 had access too, it gave me those ftol2 errors.

 

2.  Either you need to incorporate that line of code into each .c file that you get the error with or compile everything with the same compiler.

 

  I hope my mistake can help anyone else out there. Thank you very much Andi as this allows me to explore how NEL is really put togeather. By running the envirnments and see how all the libraries act, I can figgure out how to incorportae my characters and my unique game functions into NEL.

 

  Thank you all once again for your help and have a very blessed day.

 

-Timothy

 

-----Original Message-----
From: address@hidden on behalf of Andi [ Debug ]
Sent: Thu 9/30/2004 12:24 PM
To: Developer's list for the NeL platform
Cc:
Subject: Re: [Nel] libXML, the bane of my project...

had some ideas check your project settings

 

code generation should be set to blended

and you are compiling as Multi Threaded DLL

 

also make sure directX includes are directly below STLPort includes which should be at the top of the include directory list

 

about __ftol and __ftol2

 

this is a compiler generated command to convert long to float in VC7 > it was renamed __ftol2 to prevent version clashes mist likely with changes to the command.

 

you can try adding this to the very top of your code or in precompiled header to prevent it.

 

 

#if (_MSC_VER >= 1300) && (WINVER < 0x0500)
//VC7 or later, building with pre-VC7 runtime libraries
extern "C" long _ftol( double ); //defined by VC6 C libs
extern "C" long _ftol2( double dblSource ) { return _ftol( dblSource ); }
#endif

 

 

----- Original Message -----

From: Timothy H. Schilbach

To: Developer's list for the NeL platform ; Developer's list for the NeL platform

Sent: Thursday, September 30, 2004 9:47 AM

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

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

-----Original Message-----
From: address@hidden on behalf of Andi [ Debug ]
Sent: Thu 9/30/2004 8:14 AM
To: Developer's list for the NeL platform
Cc:
Subject: Re: [Nel] libXML, the bane of my project...

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 :)

---

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