Understanding the --test-config option

[eldiener]

The documentation says that "Running the following command will run all tests against each compiler known." Does "each compiler known" refer to each toolset specified in the --test-config=user-config.jam file, or does it mean something else ? In other words if the --toolset option is not used when invoking b2, which compiler toolsets are tested ? Also, and probably related, what does the --test-config option do ?

[tee3]

Hi @eldiener, thanks for taking the time to look into this. I have to familiarize myself with this again :)

I mentioned in the README for boost-build-nvcc that it was tested using this, but I actually hadn't done that yet for this one. I'm working on getting it pushed up in a branch now.

To answer your questions:

• "each compiler known" is the compilers called out in the project-config.jam file. This file contains the default compiler for each platform (msvc for Windows, gcc for Linux, clang for macOS). Each branch contains a single other toolset, such as nvcc to test.

• the user-config.jam file is empty to ensure that nothing from your ~/user-config,jam affects the tests.

• the --test-config option is used here to suppress loading the users ~/user-config.jam.

[tee3]

Also, note that this takes a long time to run as it is building a system (a library, executable, etc.) using all combinations of features for each compiler configured in project-config.jam and called out on the command line with toolset=.

There are lots of warnings for nvcc currently. These warnings indicate a missing functionality in the nvcc toolset such as not supported shared library builds. If you look in the bin directory after it runs you will see a lot of directories with hashes that contain the output of the tests. It is very hard to tell which succeeded and failed this way, but it does allow one to work through resolving issues. I would typically limit the features via the command line until I know which are broken.

[tee3]

I finally ran this and all tests pass against the laster master of boost-build-nvcc with link=static on Linux with CUDA 9.1. The command line below uses 8 cores to speed up the build.

bjam --test-config=user-config.jam --hash --verbose-test -j 8 link=static 

[tee3]

@eldiener Did you have any success with this? How about with https://github.com/tee3/boost-build-nvcc?