Skip to content

Latest commit

 

History

History
70 lines (53 loc) · 1.7 KB

building.md

File metadata and controls

70 lines (53 loc) · 1.7 KB
Raw

Building on Windows

mkdir build
cd build
cmake .. -G "Visual Studio 16 2019" -A x64
msbuild verona-rt-all.sln /m /P:Configuration=Debug
msbuild verona-rt-all.sln /m /P:Configuration=Release
msbuild verona-rt-all.sln /m /P:Configuration=RelWithDebInfo

On Windows, a separate directory is used to keep the binaries for each build configuration.

Building on Linux

mkdir build_ninja
cd build_ninja
cmake .. -GNinja -DCMAKE_BUILD_TYPE=Debug
ninja

Switch the cmake line to either

cmake .. -GNinja -DCMAKE_BUILD_TYPE=Release
cmake .. -GNinja -DCMAKE_BUILD_TYPE=RelWithDebInfo

to provide the other configurations.

On Linux, only the binaries for the most recent build configuration are kept.

Running the test suite

The test suite can be run from the build or build_ninja directories:

ctest

Use the options -j N to run N jobs in parallel, and -R <regex> to run tests that match the regular expression <regex>.

Individual tests can be run from their build directories, for example:

build\src\rt\Debug\func-sys-diningphilosophers.exe

or on Linux

build/func-sys-diningphilosophers

will run a unit test with systematic testing. And

build\src\rt\Debug\func-con-diningphilosophers.exe

will run it with an actually concurrent runtime.

Systematic testing tests take parameters --seed n and --seed_count m to run the seed range n to n+m-1. If you provide a --seed_count 1 (which it defaults to, if not provided), then it will print the trace for that seed. If you don't provide --seed it will pick a random starting seed.

CMake Feature Flags

These can be added to your cmake command line.

-DSANITIZER=address // Use Address sanitizer on Clang