Rhys,
I think I understand your problem, but it was a little hard to follow. You
keep mentioning BC++, but that is a very different product from
BCB. However, your path statement contains references to CBuilder and you
are trying to use the BCB5 stuff, so I'll assume you are really running
BCB5. Also path includes names like XML4C. Are you really trying to build
XML4C or Xerces. They are similar, but I'm not familiar with the build
requirements for XML4C. I rather doubt that the Xerces project files will
work with with XML4C. I'll assume you really want to build Xerces.
Your path statement is pretty ugly. Lots of programs have problems with
exceedingly long path statements. There are even limits on the length
imposed by a DOS box. In addition, there are a number of command line
utilities that do not function properly if directory or file names include
dashes ("-"). Command line utilities like BCC32, TLINK32, and ILINK32 do
not always tolerate dashes in directory or file names because they look
like switches. This is especially true for pre-BCB6 compilers and
linkers. Even then, BCB6 ILINK32 still has one such bug where an offensive
path is contained within an environmental variable. Things like
xml4c-src4_0_0 should be renamed. If possible, reset your path to what
would have normally been there before you added the Xerces paths. Try this
(carriage returns added for clarity):
C:\WINDOWS;
C:\WINDOWS\COMMAND;
C:\jdk1.3.0_02\bin;
C:\PROGRA~1\ULTRAE~1;
C:\PROGRA~1\BORLAND\CBUILD~1\BIN;
C:\PROGRA~1\BORLAND\CBUILD~1\PROJECTS\BPL
The BCB5 version of XercesLib.bpr (the project file) will correctly build
Xerces 1.6.0 provided the directory structure used by the CVS build tree is
not altered. Open XercesLib.bpr in the IDE. Go to your project options
and click on the "Directory/Includes" tab. Observe the Include
paths. Note that they are all defined as relative paths with respect to
the project directory. You will find the same is true for the library
paths. This means there is no need to modify the system path to include
any additional directories. Due to a buggy project manager, it is wise not
to modify Xerces project options from within the IDE. The pre-BCB6 PM has
problems with very large projects. Close (cancel) the options box, select
"Project|Build" and you should end up with a usable DLL.
The workaround you mention has to do with path modifications within the
project environment itself and not those referenced externally (such as the
system path). It only applies to version BCB6.
I would also suggest you stick with Xerces 1.6.0 if you have BCB5. The
older stuff had a number of problems (getting it to build and in using it)
and I have no plans to update the project file to work with 1.7.0.
HTH,
Don
At 09:21 PM 3/10/2002 -0800, you wrote:
<snip>
>My specific problem:
>
>My utility for Xerces is to use the dom components
>and/or sax components to persist data in various forms
>in an XML format. I am somewhat experienced in using
>and structuring XML, yet have only about 6 months
>experience with coding C++ ( though I have been
>independantly studying programming languages for two
>years, now ). The compiler that I have been using (
>and the only one I have access to ) is Borland C++
>professional 5.0 . In attempting to use Xerces, I
>downloaded both formats of version 1.4.0 for windows (
>stable source and stable binary ), and more recently
>1.6.0 and 1.7.0 .
>
>I have been able to get programs to compile using
>header files and including their respective .cpp files
>within the program's project, many of which I have
>written, myself. I admit, I did expect to just be
>able to have the .cpp and .h files located somewhere
>in my path, and just explicitly reference the .h
>files, and still have the program compile, but what do
>I know? In the end, I got it to run by having
>everything I used under the same directory as the
>project, and both including header files and adding
>the .cpp's to the project. It strikes me that this is
>not ideal and that I am probably missing something,
>but up 'til now I have been figuring things out
>myself, having no one suitable to ask for help.
<snip>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
