Description
Currently, installed artifacts in POCO are not clearly separated and end up effectively undefined in terms of packaging purpose.
For integration into larger systems, it is important to distinguish between two logical components:
• Runtime – artifacts required to run applications (shared libraries, executables, runtime resources)
• SDK – artifacts required for development (headers, CMake configs, export targets, development libraries)
Without this separation:
• packaging (e.g. via CPack) becomes difficult
• runtime distributions may include unnecessary development files
• SDK distributions may miss required export information for find_package
Proposal
Introduce clear component-based installation:
• assign install targets to either:
• Runtime
• Sdk
This would allow:
• clean packaging of runtime vs development artifacts
• easier integration into umbrella SDKs
• proper downstream usage via CMake (find_package)
Description
Currently, installed artifacts in POCO are not clearly separated and end up effectively undefined in terms of packaging purpose.
For integration into larger systems, it is important to distinguish between two logical components:
• Runtime – artifacts required to run applications (shared libraries, executables, runtime resources)
• SDK – artifacts required for development (headers, CMake configs, export targets, development libraries)
Without this separation:
• packaging (e.g. via CPack) becomes difficult
• runtime distributions may include unnecessary development files
• SDK distributions may miss required export information for find_package
Proposal
Introduce clear component-based installation:
• assign install targets to either:
• Runtime
• Sdk
This would allow:
• clean packaging of runtime vs development artifacts
• easier integration into umbrella SDKs
• proper downstream usage via CMake (find_package)