This might be my fault If you're building a paraview app. I had SET (CMAKE_INSTALL_DEBUG_LIBRARIES ON) from a month ago that I didn't remove. I'll do that right now.
On Wed, Jan 5, 2011 at 1:54 PM, Michael Jackson <mike.jack...@bluequartz.net > wrote: > OK.So how do I NOT package them? So far they _are_ getting put into the > installer even if I set Visual Studio to "Release". I have this at the top > of my CMake code that sets up CPack: > > if (MSVC) > SET (CMAKE_INSTALL_DEBUG_LIBRARIES OFF) > INCLUDE (InstallRequiredSystemLibraries) > endif() > > ___________________________________________________________ > Mike Jackson www.bluequartz.net > Principal Software Engineer mike.jack...@bluequartz.net > BlueQuartz Software Dayton, Ohio > > On Jan 5, 2011, at 1:31 PM, David Cole wrote: > > > Just as an FYI: > > > > The Debug libraries for MSVC are not redistributable components. Do > > not build them into an installer. People who need to use them are > > required to have a corresponding Visual Studio installation on their > > machine. > > > > We provide access to those for INSTALL simply for testing the make > > install tree of a debug build, possibly even copying it over to > > another machine for testing. > > > > But it is not intended that the MSVC Debug libraries be packaged... > > > > > > On Wed, Jan 5, 2011 at 1:20 PM, Michael Jackson > > <mike.jack...@bluequartz.net> wrote: > >> I am working on my CPack code for my project. What I have noticed is > that the MSVC runtime libs for both Debug and Release are included when I do > an INSTALL and are NOT included when I try to run the PACKAGE project. > Again, this is probably something simple to solve but I just am not sure > what all I should be using from CMake or creating on my own. > >> > >> Any pointers? I'll start wading through both the CMake projects and the > ParaView projects and see what if those yield any clues. > >> ___________________________________________________________ > >> Mike Jackson www.bluequartz.net > >> Principal Software Engineer mike.jack...@bluequartz.net > >> BlueQuartz Software Dayton, Ohio > >> > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > >> > >> Follow this link to subscribe/unsubscribe: > >> http://www.cmake.org/mailman/listinfo/cmake > >> > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > > > Follow this link to subscribe/unsubscribe: > > http://www.cmake.org/mailman/listinfo/cmake > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake