From: Matt E. <ma...@au...> - 2003-06-18 18:09:32
|
Hi, Is anyone else having link errors compiling the example in v0.24 with or without the visual studio patch installed? I have verified the /Tp flag is set per the win32 documentation. MSVC compiler output: --------------------Configuration: dom_build - Win32 Release-------------------- Linking... libxml++.lib(document.obj) : error LNK2001: unresolved external symbol __imp__xmlIndentTreeOutput libxml++.lib(keepblanks.obj) : error LNK2001: unresolved external symbol __imp__xmlIndentTreeOutput Thanks, Matt Esterly PS very nice work on the API |
From: Ephraim V. <ef...@ep...> - 2003-06-19 06:49:03
|
could it be you are using an old version of libxml2 ? this doesn't happen with libxml2 2.5.4 -eff ----- Original Message ----- From: "Matt Esterly" <ma...@au...> To: <lib...@li...> Sent: Wednesday, June 18, 2003 8:09 PM Subject: [libxml++] Win32 link error (v0.24.0 + msvc patch) > Hi, > Is anyone else having link errors compiling the example in v0.24 with > or without the visual studio patch installed? I have verified the /Tp > flag is set per the win32 documentation. > > MSVC compiler output: > --------------------Configuration: dom_build - Win32 > Release-------------------- > Linking... > libxml++.lib(document.obj) : error LNK2001: unresolved external symbol > __imp__xmlIndentTreeOutput > libxml++.lib(keepblanks.obj) : error LNK2001: unresolved external > symbol __imp__xmlIndentTreeOutput > > Thanks, > Matt Esterly > > PS very nice work on the API > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > Libxmlplusplus-general mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libxmlplusplus-general > |
From: Christophe de V. <cde...@al...> - 2003-06-19 09:33:54
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Jeudi 19 Juin 2003 09:50, Ephraim Vider a =E9crit : > could it be you are using an old version of libxml2 ? > this doesn't happen with libxml2 2.5.4 > Strange, the xmlIndentTreeOutput variable is quite old in libxml. Was libxml2.dll compiled with the same compiler, same version ? Cheers, Christophe =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+8YOSB+sU3TyOQjARAj9rAKDXvXk5mPUHyYoee7spG7vxdflvvQCfaLaC TUF7voOqSvQoA8uPHBR7TjU=3D =3DsnqN =2D----END PGP SIGNATURE----- |
From: Matt E. <ma...@au...> - 2003-06-19 20:44:40
|
On Thursday, June 19, 2003, at 02:34 AM, Christophe de VIENNE wrote: > Le Jeudi 19 Juin 2003 09:50, Ephraim Vider a =E9crit : >> could it be you are using an old version of libxml2 ? >> this doesn't happen with libxml2 2.5.4 > Strange, the xmlIndentTreeOutput variable is quite old in libxml. > Was libxml2.dll compiled with the same compiler, same version ? I am using libxml2 2.5.7 from=20 http://www.zlatkovic.com/projects/libxml/binaries.html per the readme .=20= It appears xmlIndentTreeOutput is not exported in the xmlib2.dll, I=20 commented out or hard coded the references and libxml++ and the=20 examples compile and run like champs. It appears the binaries are=20 compiled using the MS DDK and I am using MSVC 6.0 which has not been an=20= issue in the past. attempts to build 2.5.7 from scratch get a couple=20 link errors as well so... rolling back to 2.5.4 may be the best option. Has anyone had success with libxml2 2.5.7? thanks >m= |
From: Christophe de V. <cde...@al...> - 2003-06-19 23:28:50
|
Le Jeudi 19 Juin 2003 22:44, Matt Esterly a =E9crit : > > It appears xmlIndentTreeOutput is not exported in the xmlib2.dll, > Well, but we have in globals.h at line 268 : LIBXML_DLL_IMPORT extern int xmlIndentTreeOutput; This line is skipped by the preprocessor if thread are enabled, but I don't= =20 think this binary is compiled with thread support. Try to compile and link a single program : #include <libxml/globals.h> int main() { printf("%d", xmlIndentTreeOutput); } If this doesn't work, you may have some more help on the libxml mailing-lis= t. Good luck, Christophe |
From: Ephraim V. <ef...@ep...> - 2003-06-24 14:15:21
|
Ok, I have found the problem, The prebuilt libxml2 2.5.7 was compiled with thread support (as opposed to 2.5.4) so the "globals" are accessed differently. You need to add _REENTRANT to the libxml++ project preprocessor definitions in order to activate the thread support in the header and have access to the global variables. -eff ----- Original Message ----- From: "Christophe de Vienne" <cde...@al...> To: <lib...@li...> Sent: Friday, June 20, 2003 1:25 AM Subject: Re: [libxml++] Win32 link error (v0.24.0 + msvc patch) Le Jeudi 19 Juin 2003 22:44, Matt Esterly a écrit : > > It appears xmlIndentTreeOutput is not exported in the xmlib2.dll, > Well, but we have in globals.h at line 268 : LIBXML_DLL_IMPORT extern int xmlIndentTreeOutput; This line is skipped by the preprocessor if thread are enabled, but I don't think this binary is compiled with thread support. Try to compile and link a single program : #include <libxml/globals.h> int main() { printf("%d", xmlIndentTreeOutput); } If this doesn't work, you may have some more help on the libxml mailing-list. Good luck, Christophe ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Libxmlplusplus-general mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libxmlplusplus-general |
From: Christophe de V. <cde...@al...> - 2003-06-24 15:36:44
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mardi 24 Juin 2003 17:14, Ephraim Vider a =E9crit : > Ok, I have found the problem, Great ! > The prebuilt libxml2 2.5.7 was compiled with thread support (as opposed to > 2.5.4) so the "globals" are accessed differently. > > You need to add _REENTRANT to the libxml++ project preprocessor > definitions in order to activate the thread support in the header and have > access to the global variables. > So we'll have the same problem on unixboxes when libxml is compiled with=20 thread support. Question for autotools gurus: =2D - Is there a way at configure time to now wether or not libxml2 has bee= n=20 compiled with thread-support ? subquestion: =2D - Does defining _REENTRANT and link against a libxml2 without threads w= ill be=20 a problem ? I don't think so but we need to test. Cheers, Christophe =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE++HAiB+sU3TyOQjARAmflAKCYpmbs+REvFCoAjgk693H+t3nncACeNC1u 0jSz6DiOR77XLgYLVE/WhKU=3D =3DXpij =2D----END PGP SIGNATURE----- |