Skip to content

Latest commit

 

History

History
231 lines (127 loc) · 13.6 KB

INSTALL.md

File metadata and controls

231 lines (127 loc) · 13.6 KB
Raw

Install

This project provides pre-build binaries or an installation package. See the tags section for details. If the binaries for your platform are not available, the source code must be compiled and copied to the appropriate directory.

The following steps show how to install the library:

  1. Download the source code from an existing tags and extract the content to a local directory (for example c:\projects\bin2cpp or ~/dev/bin2cpp).

  2. Build the source code according to the Build Steps instructions specified in this document.

  3. Navigate to the build directory and execute the 'install' command for your platform:

    1. On Windows, enter cmake --build . --config Release --target INSTALL.
    2. On Linux or macOS, enter sudo make install.

Build

This section explains how to compile and build the software and how to get a development environment ready.

Prerequisites

Software Requirements

The following software must be installed on the system for compiling source code:

Linux & macOS Requirements

These are the base requirements to build and use bin2cpp:

  • GNU-compatible Make or gmake
  • POSIX-standard shell
  • A C++98-standard-compliant compiler

Windows Requirements

  • Microsoft Visual C++ 2010 or newer

Build steps

The project uses the CMake build system to generate a platform-specific build environment. CMake reads the CMakeLists.txt files that you'll find throughout the directories, checks for installed dependencies and then generates files for the selected build system.

To build the software, execute the following steps:

  1. Build and install all software prerequisites before building this software.

  2. Get a copy of the source code by using one of the following methods:

    • Download the source code of the project from an existing tags and extract the downloaded zip file to a local directory (for example c:\projects\bin2cpp or ~/dev/bin2cpp).
    • Clone the github repository by running git clone "http://github.com/end2endzone/bin2cpp".

  3. Generate the project files for your build system. From your source code directory, enter the following commands:

mkdir build
cd build
cmake ..

Note: See CMake Quick Tips section for more details on building the library.

  1. Build the source code:
    1. On Windows, run cmake --build . --config Release or open the generated .sln file with Visual Studio.
    2. On Linux, run make command.

Building scripts for Linux & macOS

The project provides scripts to facilitate the build process. The scripts can be found in ci/linux directory and can be used on Linux and macOS platforms. There are 2 master scripts, one for building in debug and another for building in release. The scripts are named

  • build_all_debug.sh
  • build_all_release.sh

If you do not know about debug and release configurations, then you probably need to build in release mode. If you plan to contribute to the project or a project that requires this library, you should be building in debug.

Launch one of the 2 scripts to fully build bin2cpp with all dependencies using default options.

Also, there are other scripts which are designed to be called by the 2 master scripts:

  • install_bin2cpp.sh
  • install_googletest.sh
  • install_rapidassist.sh
  • test_script.sh

They can be called individually but they require the following environment variables to be set:

Name Value
BIN2CPP_SOURCE_DIR Directory where you cloned the repository or extracted the source code.
BIN2CPP_BUILD_TYPE Release or Debug

Once the environment variables are set, you should be able to execute each script one by one.

During the compilation process, project dependencies will be cloned in third_parties directory (for example, $BIN2CPP_SOURCE_DIR/third_parties/googletest. At the end of the build process, the project's binaries will be located in directory $BIN2CPP_SOURCE_DIR/build/bin.

You can see the latest build log example at the following locations:

Building scripts for Windows

The project provides scripts to facilitate the build process. The scripts can be found in ci/windows directory. There are 2 master scripts, one for building in debug and another for building in release. The scripts are named

  • build_all_debug.bat
  • build_all_release.bat

If you do not know about debug and release configurations, then you probably need to build in release mode. If you plan to contribute to the project or a project that requires this library, you should be building in debug.

Double click on one of the 2 scripts to fully build RapidAssist with all dependencies using default options.

Also, there are other scripts which are designed to be called by the 2 master scripts:

  • install_bin2cpp.bat
  • install_googletest.bat
  • install_rapidassist.bat
  • test_script.bat

They can be called individually but they require the following environment variables to be set:

Name Value
BIN2CPP_SOURCE_DIR Directory where you cloned the repository or extracted the source code.
CONFIGURATION Release or Debug
PLATFORM x64 or Win32
PLATFORMTOOLSET An empty value or a valid platform toolset like Windows7.1SDK, v140, v141 or v142.

Once the environment variables are set, you should be able to execute each script one by one.

During the compilation process, project dependencies will be cloned in third_parties directory (for example, %BIN2CPP_SOURCE_DIR%\third_parties\googletest). At the end of the build process, the project's binaries will be located in directory %BIN2CPP_SOURCE_DIR%\build\bin\%CONFIGURATION%.

You can see the latest build log example on AppVeyor bin2cpp page or GitHub Actions page.

CMake Quick Tips

The following section explains typical issues that you might run into when trying to build the project.

CMake default install directory requires administrator rights

If you do want to specify a custom directory where this project should be installed, you can provide an extra option to CMake using the property CMAKE_INSTALL_PREFIX. The property must be specified at CMake configuration time. For example, the command cmake -DCMAKE_INSTALL_PREFIX=c:\projects\install .. will install the project binaries into directory c:\projects\install\[NAME OF THE PROJECT].

If you do not specify a custom install directory, CMake will install the binary files into its default location, which differs from system to system.

On Windows, the default CMake installation directory is C:\Program Files (x86)\[NAME OF THE PROJECT] which requires administrator privileges.

On Linux, the default CMake installation directory is /usr/local/[NAME OF THE PROJECT and also requires administrator privileges (sudo).

Tell CMake where to find depdendencies

If you installed your library dependencies into a directory other than CMake's default installation directory, CMake will not be able to find your dependencies automatically.

For example, on Windows, the CMake default installation directory is C:\Program Files (x86)\${PROJECT_NAME}. This makes the installation directory different for each dependency and create unnecessary complication when using CMake.

There are 2 different ways to tell CMake where to look for when searching for libraries:

  1. Using environment variables.

The installation path of specific dependency can be specified manually by defining the environment variable [NAME OF DEPENDENCY]_DIR to the right installation directory. For instance, to specify the installation directory of rapidassist dependency, one can define the rapidassist_DIR environment variable which will instruct CMake to look at this location for already installed libraries. By specifying the install directory manually, the find_package() command will be able to resolve the path of the dependency and locate the include directory and library files.

A different environment variable must be specified for all required dependencies.

  1. Define the CMAKE_PREFIX_PATH property.

The installation path of all dependencies can be specified manually by defining the CMAKE_PREFIX_PATH property. This property must be set at configuration time. For example, the command cmake -DCMAKE_PREFIX_PATH=c:\dependencies\install .. will instruct CMake to use c:\dependencies\install directory (and subdirectories) while searching for installed dependency binaries.

You can provide multiple path in CMAKE_PREFIX_PATH property by delimiting each individual path using ; (semicolon). See this Stack Overflow article for details.

Install project binaries and dependencies in same directory

For some project, it may be a better option to install the project and all its dependencies into the same directory. This is a convenient option when one wants to deploy an application without relying on the system's pre-installed binaries. The runtime environment stays the same even if the user update system libraries. For instance, Portable Apps deploys application using this method: all required binaries are included in the deployed package.

To use such a configuration, all dependencies must be reinstalled to a common directory. To follow best practices, it is suggested to re-download all dependencies, extract the sources to a new temporary directory and recompile all of them to make sure that no system library is used while compiling.

Users should define the property CMAKE_INSTALL_PREFIX of each dependency to the common installation directory (identical across all dependencies) and recompile all dependencies. The property must be specified at CMake configuration time. For example, the command cmake -DCMAKE_INSTALL_PREFIX=c:\projects\install ...

With this method, users do not have to define environment variable such as [NAME OF DEPENDENCY]_DIR or CMAKE_PREFIX_PATH property. CMake will be able to locate all library files since the property CMAKE_INSTALL_PREFIX is one of the directories that is searched when CMake is looking for a dependency.

Build options

The following table shows the available build option supported:

Name Type Default Usage
CMAKE_INSTALL_PREFIX STRING See CMake documentation Defines the installation folder of the library.
BIN2CPP_BUILD_TEST BOOL OFF Enable/disable the generation of unit tests target.
BIN2CPP_BUILD_DOC BOOL OFF Enable/disable the generation of API documentation target.

To enable a build option, run the following command at the cmake configuration time:

cmake -D<BUILD-OPTION-NAME>=ON ..

Testing

bin2cpp comes with unit tests which help maintaining the product stability and level of quality. Tests validates multiple combinations to make sure that any input file is always encoded and decoded without errors.

Test are build using the Google Test v1.8.0 framework. For more information on how googletest is working, see the google test documentation primer.

Test are disabled by default and must be manually enabled. See the Build Options for details on activating unit tests.

Test are automatically build when building the solution.

To run tests, navigate to the build/bin folder and run bin2cpp_unittest executable. For Windows users, the executable is located in build\bin\Release.

Test results are saved in junit format in file bin2cpp_unittest.x86.debug.xml or bin2cpp_unittest.x86.release.xml depending on the selected configuration.

The latest test results are available at the beginning of the README.md file.