RE: [xml] DUmb questions about using libxml2 with Borland C_++

["Redding, Matthew" <Matthew Redding dpi qld gov au>]

Thanks Eric, 

I have built the package under BCB, thanks to the excellent configuration 
script, and infor in the win32 directory.

It seems to be working, I have some problems with the xpath example 
application.  I have obtained binaries of iconv, and used COFF2OMF
as you have described to me to convert them to a BCB useable
form, but I am not convinced that all is OK, so I will obtain
the source for iconv, and see if I can easily build it with BCB.  
Perhaps there are similar problems with COFF2OMF for iconv as there 
are for libxml2.

I have been wondering if the BCB utility implib might somehow be connected/offer
a solution to this problem.

Thanks for your help.

Matt R. Redding
Senior Environmental Scientist, Intensive livestock and sheep
Agency for Food and Fibre Sciences
Department of Primary Industries

Telephone 07 4688 1372  Fax 07 4688 1192
Email matthew redding dpi qld gov au
Website  http://www.dpi.qld.gov.au/ilsu/  Call Centre 13 25 23
 

-----Original Message-----
From: Eric Zurcher csiro au [mailto:Eric Zurcher csiro au]
Sent: Wednesday, 26 November 2003 10:11 AM
To: xml gnome org
Cc: Redding, Matthew
Subject: RE: [xml] DUmb questions about using libxml2 with Borland C_++


To try to clarify things a bit on use of libxml2 with BCB:

While it is possible to use Igor's pre-compiled Win32 libxml2 DLL with BCB,
there are a couple of problems with doing so. The first problem is that
Borland uses OMF rather than COFF format, so the import library provided
with the DLL won't work directly with the Borland compiler. Fortunately,
Borland provides a utility called "coff2omf" which can be used to generate
an import library in Borland format from the original. The second problem is
not so readily circumvented: some of the functions in the libxml2 API (e.g.,
xmlDebugDumpString) take a FILE * as a parameter. Since a FILE struct in BCB
is not equivalent to one in MSVC, these functions cannot be safely called
from a BCB application. As it happens, this means that nearly all the
standard test applications, like xmllint, won't work if you use this
approach.

However, it's easy enough to build libxml2 using BCB, and that's probably
the best thing to do if you're working with BCB exclusively. Just watch out
for potential problems with DLL conflicts: if you have other applications
installed which make use of the MSVC version of libxml2, they won't work
very well if they happen to load a BCB version of the DLL.

On Tue, Nov 25, 2003 at 09:06:43AM +1000, Redding, Matthew wrote:
> HI All, 
>
> I have been hunting around for info on using the library
> with Borland C++.  No success on the newsgroups, can't even find good 
> documentation on using third party libraries with BOrland (why is that not
in the 
> docs that come with the program?  Support for open source is always
better).  
> I have it going nicely at home, under red hat, 
> but here I have to operate in an MS environment :{.
>
> I see that there is a web site with win ports, but 
> I am not sure that these libs will work with borland.
> Will they, and what do I have to do to get them to work?
>
> If they won't work, I suppose I need to work from the source...and
> I am likely to need advice on how to use the make file in the borland
environment.
> I guess I might be pushing my luck asking these questions, but 
> there might be someone else here who has just been through this sort of
thing.

Eric Zurcher
CSIRO Livestock Industries
Canberra, Australia
Eric Zurcher csiro au 

********************************DISCLAIMER****************************
The information contained in the above e-mail message or messages 
(which includes any attachments) is confidential and may be legally 
privileged.  It is intended only for the use of the person or entity 
to which it is addressed.  If you are not the addressee any form of 
disclosure, copying, modification, distribution or any action taken 
or omitted in reliance on the information is unauthorised.  Opinions 
contained in the message(s) do not necessarily reflect the opinions 
of the Queensland Government and its authorities.  If you received 
this communication in error, please notify the sender immediately and 
delete it from your computer system network.