Don,

       Your latest version of the following files are in CVS now, please
help to verify.

        XercesLib.bpr
        XercesLib.cpp
        XercesLib.mak

>Is it possible for you folks to run a BCB build on a regular basis so
>people only have to download the binaries?

       Hummm... I quote this here simply to draw other's attention.

Regards,

Peiyong Zhang
____________________________________________
XML Parsers Development
IBM Toronto Laboratory email: [EMAIL PROTECTED]
Phone: (416)448-4088; Fax: (416)448-4414; T/L: 778-4088



Don Mastrovito <[EMAIL PROTECTED]> on 08/24/2001
08:48:26 AM

Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: XercesLib and Borland C++Builder 5


Peiyong,

I updated the BCB5 project files to include the recent module additions
mentioned in my previous posting.  I also made an attempt to understand the

problems mentioned by Herb Chong in his mail last week.  The BCB IDE tends
to scramble the include paths when you change *some* project options.  The
amount of damage seems relative to the number of files in the project.  I
removed some extraneous files from the project and minimized the corruption

a bit, but there are still some problems.  I did not address the make file
issues brought up last week for those using the free Borland compiler, but
did include a make file in the attachment which some people might find
useful.

The doc changes look OK.

The attached zip file contains the updated project files plus the CVS difs
and a make file.

Is it possible for you folks to run a BCB build on a regular basis so
people only have to download the binaries?

Thanks for your help.
Don

(See attached file: XercesLib.zip)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

XercesLib.zip

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to