Add Namespace to your target
envgap__jbeder__yaml-cpp-661
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
5b3e30bfe9462f839f3585af72dd47b5b289b45d- Manifest
CMakeLists.txt- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
jbeder/yaml-cpp #661 · read the original issue
Nearly two years ago you merged a [pull request](https://github.com/jbeder/yaml-cpp/pull/344) which added some support for *more modern* CMake.
A step toward the right direction I think, but unfortunately the CMake code now includes variables like `YAML_CPP_LIBRARIES` which leads to spaghetti code somehow...
It would be beneficial if you would export your targets instead, this is considered **best practice**, is there any good reason why you don't do it yet? If not, I can try to come up with a patch.
Have a look at https://pabloariasal.github.io/2018/02/19/its-time-to-do-cmake-right/#good-boys-export-their-targets
If ready, one could import the library and all necessary includes, flags,... via
```
find_package(yaml-cpp 0.6.0 REQUIRED)
target_link_libraries(${PROJECT_NAME}
PRIVATE
yaml-cpp::yaml-cpp
)
```
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]