Skip to content

Adjust third-party boost build for different toolset choices

Michael Turner requested to merge fix/boost-compiler into master

When using a compiler which is not in PATH with nektar++, boost will continue to use the first compiler it finds in path for its build. This fix addresses this issue by writing an explicit user-config.jam file to enforce compiler selection.

Edited by Dave Moxey

Merge request reports