Clone this wiki locally
Getting Started with BDE
A supported C++ toolchain, including compiler, preprocessor, linker
Operating Systems and Compilers
See Caveats for:
The BDE library itself builds fairly quickly and does not consume a significant amount of resources (CPU time or memory), but the BDE unit test drivers are substantially larger. It is not unusual for an optimized build of one of the BDE container test drivers to have a working set of more than 1GB of RAM. If a parallel build is invoked, it is quite possible for the build process to consume 4GB (or more) of RAM at its peak.
BDE uses a build system based on waf. Building software with waf works in two steps: First you configure the source code, and then you build it. (This two-step process will feel familiar to users of autoconf.) Waf can build libraries directly, or it generate project files for Visual Studio or Xcode.
The waf based build system is located in the BDE Tools repository, which must be set up before the build system can be used:
- Make sure that python 2.6 - 2.7 are installed on the system.
- Download BDE Tools and add the
<bde_tools_repo_root>/binto the system
PATHenvironment variable. Make sure the first
wafcommand found in
PATHis a script from that path.
Once the waf based build system has been set up. The following commands can be used to configure and build the BDE repository:
From the root of this source repository, run:
To build the libraries, but not the test drivers, run:
To also build the test drivers, run:
waf build --test build
To build and run the test drivers, run:
waf build --test run
Waf Build Commands
The waf commands are executed with the following syntax:
waf [command] [options]
The waf based build tool provides the following commands:
Configure the source code for the specified options on the current system. This command must be run before building the libraries.
Build the source code using the previously configured options.
Install the libraries (including the associated pkg-config and header files).
Remove all build artifacts (object and library files).
Remove the build output directory.
Generate a Visual Studio 2010 solution file.
Generate a Visual Studio 2008 solution file.
Generate an Xcode project file.
You can view the list of options available for each command by running:
Detailed Build Instructions
For detailed descriptions of commands and build options available for the waf based build system, please see the relevant wiki page from the bde-tools repository: Waf-Based Build System
RHEL (Red Hat Enterprise Linux) 5 includes Python 2.4.x, which is too old to be able to run waf to generate the BDE build system. Python 2.6 can be installed from the "Extra Packages for Enterprise Linux" (EPEL) repository to satisfy this requirement. In the command box above where waf is executed, the builder will need to execute the script using python26 instead of just python.
Questions, Comments, and Feedback
If you have questions, comments, suggestions for improvement or any other inquiries regarding BDE or this wiki, feel free to open an issue in the issue tracker.
BDE Wiki by Bloomberg Finance L.P. is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.