Commit 3336d828 authored by Dion Häfner's avatar Dion Häfner

[ci skip] Added instructions for building in parallel

parent d0e3b379
......@@ -48,8 +48,12 @@ This way, you can access the content of the (still empty) folder of the virtual
Next, use `git clone` to download the DORiE repository into the shared folder. Enter the container, and execute
dunecontrol --only=dorie all
to build DORiE, or
MAKE_FLAGS="-j <N>" dunecontrol --only=dorie all
to build DORiE. Lastly, install the DORiE binaries by calling
to build in parallel on `N` processes. Lastly, install the DORiE binaries by calling
dunecontrol --only=dorie make install
......@@ -134,12 +138,12 @@ These instructions are suitable for a clean **Ubuntu** or **Mac OS X** setup. Th
sudo -H python -m pip install virtualenv sphinx==1.3.6 breathe --ignore-installed
3. **Mac OS X** only:
1. The Apple Clang compiler shipped with CMake is not suitable for compiling DUNE and UG. Before proceeding, call
The Apple Clang compiler shipped with CMake is not suitable for compiling DUNE and UG. Before proceeding, call
export CC=gcc-6
export CXX=g++-6
export CC=gcc-6
export CXX=g++-6
to enfore the Homebrew'd GCC compiler. Note that this variable export only lasts for your current terminal session. Always make sure that the configuration tool actually finds GCC instead of the Apple Clang.
to enfore the Homebrew'd GCC compiler. Note that this variable export only lasts for your current terminal session. Always make sure that the configuration tool actually finds GCC instead of the Apple Clang.
3. Clone the specified version of UG into a suitable folder on your machine. Install it by calling
......@@ -149,9 +153,9 @@ These instructions are suitable for a clean **Ubuntu** or **Mac OS X** setup. Th
4. Clone the DUNE modules and DORiE into a suitable folder on your machine. Make sure that you check out the correct branches (2.4 release branch). Enter the parent folder, and call
./dune-common/bin/dunecontrol all
MAKE_FLAGS="-j <N>" ./dune-common/bin/dunecontrol all
If you installed software into paths not appended to your `PATH` variable, you will have to add a custom options file to make sure that CMake finds all packages. See the [DUNE Installation Instructions](https://dune-project.org/doc/installation/) for details. CMake will throw an error if required packages are not found.
to build all DUNE modules in parallel on `N` processes. If you installed software into paths not appended to your `PATH` variable, you will have to add a custom options file to make sure that CMake finds all packages. See the [DUNE Installation Instructions](https://dune-project.org/doc/installation/) for details. CMake will throw an error if required packages are not found.
5. To install all DUNE packages into system locations (so you can call `dunecontrol` and `dorie` from anywhere), you can run
......@@ -171,7 +175,7 @@ The following software packages are cross-platform, so you should be able to fin
## Start an interactive Docker session
In case you built DORiE using Docker and want to start an interactive session, e.g. to build the documentation or do some debugging, you can do so by specifying a custom entrypoint for the container:
In case you built DORiE using `docker build` and want to start an interactive session, e.g. to build the documentation or do some debugging, you can do so by specifying a custom entrypoint for the container:
docker run -i -t --entrypoint=/bin/bash -v <dir>:/sim dorie
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment