You cant't use VC-build C++ DLLs with C++ Builder (is possible with plain
C). It's not only the library format, it's also because of the different
name mangling. So you have use your own project/library. I set up a project
and got it working. I'm waiting for the next release to test it again and
change my .bpr (Borland projects) files if necessary. If its not included in
the distribution I can send it.

Dietrich Wolf


-----Urspr�ngliche Nachricht-----
Von: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
An: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Datum: Mittwoch, 2. Februar 2000 19:43
Betreff: Re: Xerces-C and Borland


>
>
>
>The Borland header file was fixed, so it should be correct in the
>repository now, and it should all compile as is. You do have to build your
>own version though, since I don't think you can use the VC++ built DLLs and
>Libs directly.
>
>----------------------------------------
>Dean Roddey
>Software Weenie
>IBM Center for Java Technology - Silicon Valley
>[EMAIL PROTECTED]
>
>
>
>Michael Mason <[EMAIL PROTECTED]>@decisionsoft.com on 02/02/2000
>09:54:54 AM
>
>Please respond to [EMAIL PROTECTED]
>
>Sent by:  [EMAIL PROTECTED]
>
>
>To:   xerces-dev mailing list <[EMAIL PROTECTED]>
>cc:
>Subject:  Xerces-C and Borland
>
>
>
>We've been trying to use Xerces-C 1.0.1 with Borland C++ Builder 4, and
>have run into a problem with xerces-c_1.0.lib included in the
>pre-compiled Win32 distribution.
>
>The Borland linker reckons it's not in OMF format, and suggests using
>the coff2omf utility to convert it. Unfortunately coff2omf reports that
>it's not a valid coff file either.
>
>We've also had to play with the Borland-specific header file to get it
>working -- there's a missed off close quote (right at the end of the
>file) and it's not typedef'ing XMLUInt16 or XMLUInt32 (we've copied the
>declarations from the VCPP header instead).
>
>Had anyone had any luck with Borland?
>
>Cheers,
>Mike.
>
>--
>Mike Mason, Software Engineer
>XML Script Development Team                    Office: 44-1865-203192
>http://www.xmlscript.org/                      Mobile: 44-7050-288923
>
>
>

Reply via email to