Files
rippled/Builds/containers
Mike Ellery 13a4fefe34 Travis CI improvements:
FIXES: #2527

* define custom docker image for travis-linux builds based on
  package build image
* add macos builds
* add windows builds (currently allowed to fail)
* improve build and shell scripts as required for the CI envs
* add asio timer latency workaround
* omit several manual tests from TravisCI which cause memory exhaustion
2019-08-16 10:33:08 -07:00
..
2019-08-16 10:33:08 -07:00
2019-07-24 13:53:09 -07:00
2019-08-16 10:33:08 -07:00
2019-08-16 10:33:08 -07:00
2019-03-18 16:44:54 -07:00

rippled Packaging and Containers

This folder contains docker container definitions and configuration files to support building rpm and deb packages of rippled. The container definitions include some additional software/packages that are used for general build/test CI workflows of rippled but are not explicitly needed for the package building workflow.

CMake Targets

If you have docker installed on your local system, then the main CMake file will enable several targets related to building packages: rpm_container, rpm, dpkg_container, and dpkg. The package targets depend on the container targets and will trigger a build of those first. The container builds can take several dozen minutes to complete (depending on hardware specs), so quick build cycles are not possible currently. As such, these targets are often best suited to CI/automated build systems.

The package build can be invoked like any other cmake target from the rippled root folder:

mkdir -p build/pkg && cd build/pkg
cmake -Dpackages_only=ON ../..
cmake --build . --target rpm

Upon successful completion, the generated package files will be in the build/pkg/packages directory. For deb packages, simply replace rpm with dpkg in the build command above.