boostorg / boostorg/build

clang-win with 'runtime-debugging=on' generates '-d-' instead of '-gd'

Open
#586 5 comments 0 reactions 0 assignees View on GitHub
transition
Dominant language
C++
Stars
251
Forks
63
PR merge metrics
No merged PRs in 30d

Description

From the documentation, I would expect building with `runtime-debugging=on` would create libs with names:
`boost_chrono-clangw10-mt-gd-x64-1_73.lib`

But they are built as:
`boost_chrono-clangw10-mt-d-x64-1_73.lib`

Doc:
https://www.boost.org/doc/libs/1_73_0/more/getting_started/windows.html

As an alternative, is there a way to direct Visual Studio to link with '-d-' libs?

Building with:
`b2 toolset=clang-win variant=debug,release address-model=64 threading=multi link=shared runtime-link=shared runtime-debugging=on --with-atomic --stagedir=c:\boostlibs`

I saw someone else with the same problem:
https://stackoverflow.com/questions/59375923/how-to-build-debug-boost-static-libraries-with-clang-win-toolset

I have no trouble with the Release libs, just Debug.

I also have no luck building 32 bit libs with `address-model=32`, but I see those builds are not running on CI (appveyor), so they are not supported?
https://github.com/boostorg/boost-ci/blob/af9e44d4c5ddc26cd698fcc830954fe20b448673/.appveyor.yml

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.