C++ Builder IDE, problems linking xerces xalan Boost with BCB6 on XP

borland.public.cppbuilder.ide -


C++ Builder IDE >> problems linking xerces xalan Boost with BCB6 on XP

by mary » Fri, 18 Nov 2005 01:50:15 GMT

Hi,

I'm working on different scientific programs and I need to use external
librairies such as xerces, xalan and Boost with BCB6 on platform Windows XP.
I finally find on internet a way to build a lib (and dll) with xerces (v
2_7_0) using the make.exe with BCB5 and hoppefully it's OK with BCB6.
But I haven't this chance with xalan or Boost (v 1_32_0).
For Boost, I still have a problem with vector.hpp with definition of zero_
and one_.
Is there someone who can help me ?
Thanks in advance,

Mary



Top

C++ Builder IDE >> problems linking xerces xalan Boost with BCB6 on XP

by Tom » Fri, 18 Nov 2005 17:50:04 GMT


Boost is too new for Builder 6 and requires new ANSI compatibilities in the
compiler.







Top

C++ Builder IDE >> problems linking xerces xalan Boost with BCB6 on XP

by Duane Hebert » Fri, 18 Nov 2005 19:01:00 GMT





Boost 1_30 works with BCB6. I think most of 1_31 works as well.
Perhaps the OP can find an older version of Boost. Of course
it depends on which boost libs are needed. Not all of them work
with BCB.



Top

problems linking xerces xalan Boost with BCB6 on XP

by Mike » Sun, 20 Nov 2005 23:26:19 GMT





I just installed Boost 1_31 and much of it works...notable exception
being the Lambda library.

Top

problems linking xerces xalan Boost with BCB6 on XP

by Duane Hebert » Sun, 20 Nov 2005 23:59:26 GMT






I think that I had problems with the regular expression library.
There was also something with boost::format causing problems
with some std stuff. Mostly confusing functions from std lib
with similar functions in global namespace. Sorry, I don't remember
exactly which ones. Something to do with std::toUpper() normally
found in <locale> and ::toUpper() normally found in <ctype>.

There were some problems with boost::threads as well but that
was due to our static lib builds. In 3.1 boost started generating
warnings when using threads and not using dlls.

The rest works well and with 3.0 we didn't have the problems
that I mentioned here.



Top
Similar Threads

1. Cannot validate a ".xsd" file (Xerces 2.7.0 C++ on Windows XP)

2. "PROJECTS macro in BPG missing" in BCB6 for xerces - C++ Builder IDE

3. "PROJECTS macro in BPG missing" in BCB6 for xerces -- more info 

That "MakeBuildDirs" term in the PROJECTS line is a BAT file that creates a
directory structure.

4. Xalan C++ Problems with XPathEvaluator/SimpleXPathAPI

5. Library Linking Problem (BCB6 PRO) 

Hope someone can shed light on a problem I have.  I'm building a legacy 
embedded C application, trying not to change the code and the way it is 
structured and built.  It basically takes the directory form as follows:

    \Lib_A
        File1.C
        File2.C etc
        ...
    Lib_B
        ...
    \Configuration
        Lib_A_Config.C
        Lib_B_Config.C

Anyway, I've made some library projects, building each library, files 1...x, 
and the appropriate config file.  Then link the library into a test harness 
for unit testing, or to build the whole system to run under Win32.  The 
project option "force c++" is used to build all the files.

The config files contain const arrays and data, originally built into ROM. 
The declarations are for example:
        extern const BYTE lib_a_xxx_mask [XSIZE];
        extern const BYTE lib_a_yyy_mask [YSIZE];
and in the config file
        const BYTE lib_a_xxx_mask [XSIZE] = {.....};
        const BYTE lib_a_yyy_mask [YSIZE] = {.....};

The problem I have is that in the final link (for the application or test 
harness), all externals etc are resolved apart from the const data in the 
config files.  Its almost as if the library project is compiling the file, 
and then discarding it when making the *.LIB file.  The only way I've been 
able to get around it is building the config files in the final application 
project, but I don't really want to do that for 26 libraries.

What am I missing or messing up?

Paul.

6. Problem: BCB6 + XP + Athlon 64 -> freeze - C++ Builder