On Thu, 2019-10-03 at 17:08 -0400, stefan wrote: > Yes, that is exactly what I'm trying to do, but it doesn't seem to > have any effect. That is, `dpkg --info ...` doesn't list the > additional dependency, and correspondingly, running `apt-get install > ...` on the component package file will install the package without > first installing the prerequisite component. > Consider this declaration: > set(CPACK_COMPONENTS_ALL runtime development mstool) > If I now write > set(CPACK_COMPONENT_DEVELOPMENT_DEPENDS runtime) > I will see no effect. That is, the "development" package still does > not depend on the "runtime" package. > So I try this: > set(CPACK_COMPONENT_DEVELOPMENT_DEPENDS RUNTIME) > in case capitalization is required. Now the "runtime" component seems > to get packaged twice (as per the cmake logs), but still no correct > dependencies. > Is it time for a bug report ?
Please send us a minimal CMakeLists.txt that reproduces the issue. Kyle -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
