Re: [CMake] Request for added script intelligence
Let's see if anybody else chimes in with an opinion. I've already given mine, and I don't think there's a good argument for making installing the debug runtime libraries any easier than it already is. You can certainly write a wrapper script around the existing CMake InstallRequiredSystemLibraries that has additional logic surrounding it. Whatever the case, if any change to CMake is proposed, it should take Visual Studio generator usage into account: i.e. -- do not rely on CMAKE_BUILD_TYPE, as it is typically empty/not set in a multi-configuration VS build. Thanks, David C. -- 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: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Request for added script intelligence
I don't think that's a good idea. The Debug libraries are supposed to be non-redistributable. (At least that used to be true... is it still true?) To Debug a VS-built project, you have to run it on a machine with VS installed, so there's not a compelling need to install the debug libraries anyway. The capability is in there if you *must* have an install tree with Debug libraries in it for some reason, but it's not supposed to be the norm, and I don't think we should make it easy to do. If you're going to go against the license terms, you should have to do it explicitly in your own code... not as a side effect of a default behavior that CMake provides. Just my opinion, David C. -- 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: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Request for added script intelligence
Then it should be default in debug build not copy the release libraries which are unreferenced anyway. 'sides that... I'm only asking for the leading intelligence before the include, and not including the INSTALL line. I'm not asking to change having to add a INSTALL rule... just having a better default list of what should be copied. On Mon, Sep 8, 2014 at 5:40 PM, David Cole dlrd...@aol.com wrote: I don't think that's a good idea. The Debug libraries are supposed to be non-redistributable. (At least that used to be true... is it still true?) To Debug a VS-built project, you have to run it on a machine with VS installed, so there's not a compelling need to install the debug libraries anyway. The capability is in there if you *must* have an install tree with Debug libraries in it for some reason, but it's not supposed to be the norm, and I don't think we should make it easy to do. If you're going to go against the license terms, you should have to do it explicitly in your own code... not as a side effect of a default behavior that CMake provides. Just my opinion, David C. -- 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: http://public.kitware.com/mailman/listinfo/cmake
