MSVC 2022 Static Linking Problem
envgap__jbeder__yaml-cpp-1354
01 / FAILURE SIGNATURE
As reported upstream
I used cmake to generate the yaml-cpp MSVC solution and project files. Perhaps it's user error, but I had to go and change each project to use "Multi-Threaded" instead of "Multi-Threaded DLL" to actually get a static library that linked with my static MFC project.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
5bef9aa0038acaf85c7d5f7d8ffa303d926726a2- Manifest
CMakeLists.txt- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
jbeder/yaml-cpp #1354 · read the original issue
Including yaml-cpp as a static library in my statically-linked MFC project caused some problems. I used cmake to generate the yaml-cpp MSVC solution and project files. Perhaps it's user error, but I had to go and change each project to use "Multi-Threaded" instead of "Multi-Threaded DLL" to actually get a static library that linked with my static MFC project.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]