Table of Contents
You can adjust some configuration settings in the
BuildSetup.cmake bootstrap file.
The following is a list of variables:
Table 4.1. DDS configuration variables
|CMAKE_INSTALL_PREFIX||Install path prefix, prepended onto install directories.(default $HOME/DDS/[DDS_Version])|
|CMAKE_BUILD_TYPE||Set cmake build type. Possible options are: None, Debug, Release, RelWithDebInfo, MinSizeRel (default Release)|
|BUILD_DOCUMENTATION||Build source code documentation. Possible options are: ON/OFF (default OFF)|
|BUILD_TESTS||Build DDS tests. Possible options are: ON/OFF (default OFF)|
Now, prepare a build directory for an out-of-source build and configure the source:
mkdir build cd build cmake -C ../BuildSetup.cmake ..
If for some reason, for example a missing dependency, configuration failed. After you get the issue fixed, right before starting the cmake command it is recommended to delete everything in the build directory recursively. This will guaranty a clean build every time the source configuration is restarted.
Issue the following commands to build and install DDS:
make -j make install
Please note, that by default DDS will be installed in
Users have a possibility to additionally build DDS worker package for the local platform. In case if you have same OS types on all of the target machines and don't want to use WN packages from the DDS binary repository, just issue:
make -j wn_bin make install
the commands will build and install a DDS worker package for the given platform.
We also recommend to build boost without icu library support. This will reduce the size of the WN package dramatically. The following is boost build options you can use to switch of icu:
./bootstrap.sh --without-icu ... ./b2 --disable-icu ...
In order to enable DDS's environment you need to source the
DDS_env.sh script. Change to your newly installed DDS directory and issue:
[DDS INSTALL DIRECTORY]source DDS_env.sh
You need to source this script every time before using DDS in a new system shell. Simplify it by sourcing the script in your bash profile.