CMake Target-Based Dependencies and External Package Interoperability

Managing Dependency Boundaries

A project utilizing modern CMake (version 3.15+) aims to transition from global directory-based configurations to a strict target-based architecture. The goal is to ensure that usage requirements, such as include directories and compile definitions, are propagated only to the specific targets that link against a dependency.

The current challenge involves integrating external libraries discovered via find_package in Config-mode. While target_link_libraries handles the linking, there is uncertainty regarding the most maintainable way to map external imported targets to internal project targets without polluting the global namespace or relying on legacy variables.

• Constraints: Avoid include_directories in favor of target_include_directories.
• Requirement: Maintain strict separation between build-time requirements and installation-time usage requirements.

Which approach best ensures that imported target properties are correctly propagated to downstream consumers during the install phase? How should INTERFACE properties be managed to prevent leakage of absolute paths from the build machine to the deployment environment?