Including project_options in the installed package for interface libraries about project_options HOT 7 CLOSED

The example in the readme is updated. Now, the FEATURE_TESTS option handles the sanitizer flag exports.

from project_options.

This is impossible in CMake. The interface libraries cannot have private dependencies.

from project_options.

This is impossible in CMake. The interface libraries cannot have private dependencies.

I know, but if you install this interface, it is also impossible to use this header only lib without project_options!

from project_options.

We should also install project_options for header-only libraries.

from project_options.

Well, I don't think we actually need this. package_project already generates the project_options and project_warnings targets:

Running test_install, then looking at myprojTargets.cmake:

from project_options.

If I use a header only lib i.e. boost::asio I will not import there development setting like:

--coverage

-Wpedantic -Werror... or

the worst case: g++ specific warnings, if I want to use clang++

I created this issue to show it is a wrong usage of project_options to export the project_options for every installed lib, independent of it is an interface or a normal lib!

from project_options.

The config files generated by CMake are not portable! They have absolute paths in them, and they are generated based on the options you pass to project_options.

To avoid having test/sanitizer-related flags in the generated config, you should use FEATURE_TESTS flag.

https://github.com/cpp-best-practices/cpp_vcpkg_project/blob/830685f328fba4bbdcfb0540d0fbcecd95aaab5c/CMakeLists.txt#L30-L48

I will add this to the readme if it is not clear.

from project_options.