[xml] Delphi bindings for libxml2

Hello all, It is now almost exactly 2 years since the last update of Petr Kozelka's Pascal units for accessing libxml2 and libxslt(available at http://sourceforge.net/projects/libxml2-pas). Those units corresponded to release 2.5.10 of libxml2. Since then, there have been a number of significan

RE: [xml] Delphi bindings for libxml2

> -Original Message- > From: Igor Zlatkovic [mailto:[EMAIL PROTECTED] > Sent: Friday, 4 February 2005 4:49 AM > To: Zurcher, Eric (LI, Black Mountain) > Subject: Re: [xml] Delphi bindings for libxml2 > > > On 03.02.2005 00:05, [EMAIL PROTECTED] wrote: > > Hello all, > > > > It is now alm

[xml] Updated Delphi bindings for libxml2 now released

Hello all, New versions of the Pascal bindings for libxml2 are now available. Petr Kozelka has kindly allowed me to place them on his "libxml2 for pascal" site at http://sourceforge.net/projects/libxml2-pas, and Igor Zlatkovic has also allowed me to keep a copy with his Win32 binaries at ftp://ft

[xml] Delphi bindings now available for XMLSec

Hello all, I have generated Delphi bindings for the XMLSec library (specifically aimed at providing an interface to the Win32 libxmlsec DLL distributed by Igor). These bindings are available (along with Delphi bindings for libxml2, libxlst, and libexslt) at ftp://ftp.zlatkovic.com/pub/libxml/De

RE: [xml] Linker Error in compilation of libxml2 in VC++ 6.0

Arvind, You may need to provide a bit more detail about how you are attempting to compile libxml2. This is normally done by building from the commmand line. But your comment "Even I have set "iconv.h" and "zdll.lib" file in Projects Settings.." suggests that you are working from within the Vis

[xml] Xpath issue when linking with the libxml2 win32

Matthieu, I can't reproduce the problem you describe - the binaries from ftp://ftp.zlatkovic.com/pub/libxml/ work just fine for me. Can you provide a bit more detail about how you have configured the example? Are you working from the VS IDE, or from a command line? Are you sure that you're link

[xml] Problem when building libxml2 with Borland C++ 6

Hi, I have recently learned that the libxml2 does not build with BCB6. The problem is the result of the inclusion of the Windows header file ws2tcpip.h by wsockcompat.h. The ws2tcpip.h header file (apparently supplied to Borland by Microsoft) uses a macro, WS2TCPIP_INLINE, which on non-Microsoft c

RE: [xml] Problem when building libxml2 with Borland C++ 6

OK. Here's a patch that works, and while still somewhat ugly, isn't completely replusive: Index: include/wsockcompat.h === RCS file: /cvs/gnome/libxml2/include/wsockcompat.h,v retrieving revision 1.3

[xml] RE: win32 file support for building libxml

Manish, On Win32, libiconv can be built either as a DLL (with associated import library) or as a "static" library. The zip file includes the results of both builds: iconv.lib is the import library for iconv.dll; iconv_a.lib is the static library. The iconv_a.lib file is what you get when you use t

[xml] RE: win32 file support for building libxml

Hi Manish, You don't really need the iconv_a.lib file at all. The libxml2 MSVC make procedure just looks for a file named "iconv.lib" when linking (assuming iconv support has been selected during configuration). The DLL import library version would normally be used, and that's all that is required

RE: [xml] libxml2-2.6.22 static vs. dynamic on Windows

I cannot replicate this problem (though I tested with current CVS source rather than 2.6.22 source). Can you provide a bit more detail about when this occurs? What is being linked at the time? Does the build procedure succeed in generating any (or all) of the "test" applications? I note that your

[xml] libxml2 compiling problem with Borland compiler 6.0

Hi Guillermo, The BCB makefile was never updated to include schematron support. Embedded here a patch to correct this oversight. Daniel, can this be applied? - Index: win32/Makefile.bcb === RCS file:

Re: [xml] Pascal bindings outdated?

Hi Andreas, My apologies for not keeping the Delphi bindings a bit more up-to-date. I'm a bit lazy about this, but there is also little point in releasing the bindings for new versions before Igor releases the corresponding Windows DLLs (and his most recent is currently 2.6.23). The API has not

Re: [xml] Problems with file names in UTF-8 on Windows

Hi Daniel, Unfortunately, this patch breaks libxml2 when compiled on Windows with the Borland C compiler (and probably any other Windows compiler which uses its own IO library, rather than Microsoft's). The FILE* returned from the Windows _wfopen function is not compatible with the Borland fread,

Re: [xml] Problems with file names in UTF-8 on Windows

Hello again, Daniel, Looking into things a bit more, my earlier patch for the Borland compiler should be done differently. The Borland libraries do provide versions of the _wfopen and _wstat functions. But explicitly loading the functions from msvcrt.dll is clearly the wrong thing to do; as pointe

Re: [xml] Necessary steps involved in validating against an

Hi, Regaring Delphi programmer Erik Andersen's query about using an XSD when using libxml2, I offer the code below, based on testSchemas.c, as a simple example of how to accomplish this in a Delphi application (although it wasn't entirely clear from his original question whether Erik is developing

Re: [xml] BCB6 libxml project

Hi Andrew, When you're building the libxml2 library, the usual procedure, for both the MSVC and Borland compilers, is to do so from the command line, rather than via a project. I don't know of anyone actively maintaining a BCB project file for library compilation. Eric Zurcher CSIRO Plant Industr

[xml] XML parser benchmarks

Hi all, A series of benchmarks comparing XML parsers is described in two articles at www.xml.com : http://www.xml.com/pub/a/2007/05/09/xml-parser-benchmarks-part-1.html http://www.xml.com/pub/a/2007/05/16/xml-parser-benchmarks-part-2.html Part 1 compares event-driven (SAX-like) parsers; part 2 c

Re: [xml] libxml2 with borland builder 5.0

Hi, It should be possible to build and use libxml2 with Borland builder 5.0. Can you provide more detail regarding the problem you're having? To give you help, I would need to know a few more things: Are you using libraries built with the Borland compiler, or are you trying to link to the pre-

[xml] libxml2 win64

Hi Fabrice, I am not aware of anyone providing 64-bit Windows binaries for libxml2, but it would be useful if someone were to do so. If you succeed in your recompilation, perhaps you could pass your binaries on to Igor for broader distribution. Eric Zurcher CSIRO Plant Industry Canberra, Australi

[xml] Building libxml2 with the Borland/CodeGear/Embarcadero toolset

Hello Daniel et al. It has been a while since I've tried compiling libxml2 with the "Borland" (the compilers are now in the hands of Embarcadero) C compiler, but I've recently had reason to do so, and have a few very minor patches that I'd like to apply. I've been using the compiler and toolset

[xml] Minor patch for conditional defines in threads.c

After struggling with git to obtain the new sources, I've just tried re-building libxml2-2.7.5 under Windows with the 2007 version of CodeGear ("Borland") compiler, and found one very minor problem. In threads.c, there are two lines reading: #elif HAVE_WIN32_THREADS The CodeGear compiler doesn

Re: [xml] Minor patch for conditional defines in threads.c

Daniel, The current git head builds fine for me now. Thanks! Eric Zurcher CSIRO Plant Industry Canberra, Australia eric.zurc...@csiro.au | -Original Message- | From: Daniel Veillard [mailto:veill...@redhat.com] | Sent: Thursday, 1 October 2009 8:16 AM | To: Zurcher, Eric (PI, Black Mo

Re: [xml] Availability of libxm2-2.9.0 release candidate 1

I've had a quick try at building 2.9.0 on a 32-bit Windows system using MS Visual Studio 2010 from the command line. There was a minor problem in that none of the Win32 Makefiles seem to have been updated to include the recent addition of the buf.c module. I think it needs to be added to: Makefi

Re: [xml] Availability of libxm2-2.9.0 release candidate 1

| -Original Message- | From: Daniel Veillard [mailto:veill...@redhat.com] | Sent: Tuesday, 14 August 2012 6:25 PM | To: Zurcher, Eric (PI, Black Mountain) | Cc: xml@gnome.org | Subject: Re: [xml] Availability of libxm2-2.9.0 release candidate 1 | | ... | | ah, good point ! Sorry I n

Re: [xml] Availability of libxm2-2.9.0 release candidate 1

Attached are patches for getting builds on Windows (whether by MSVC, BCB, or MinGW) to compile buf.c. Eric Zurcher CSIRO Plant Industry Canberra, Australia eric.zurc...@csiro.au 0001-Basic-changes-for-Win32-builds-of-release-2.9.0-comp.patch Description: 0001-Basic-changes-for-Win32-builds-o

Re: [xml] Availability of libxm2-2.9.0 release candidate 1

Attached are a few more changes to get testlimits working with the Windows builds. The only other change I had to make was to revert GetProcAddressA (in xmlmodule.c) back to GetProcAddress, an issue which someone else mentioned recently. I think that GetProcAddressA is only available in Windows

Re: [xml] Using LIBXML2 in Windows environment

Tony, You don't indicate what toolset you are using (Visual Studio? MinGW?), but in any case, I would suggest looking at win32\Readme.txt. Unless you're using Cygwin (or something similar), libxml2 compilation on Windows doesn't work quite the same way as on Unix. Eric Zurcher Software develop

Re: [xml] Using LIBXML2 in Windows environment

Tony, Libxml2 works quite well in Windows, and can readily be compiled with Visual Studio 2013. Can you be more specific about where you are running into problems? If you want assistance, it would also be useful to know whether you are attempting to build a 32-bit or 64-bit version. Eric Zurch