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
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
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()
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
That is where I pulled the code from so I must have grabbed that version. But I
think I am misunderstanding what should be used when with respect to
BundleUtilities and INSTALL when on MSVC.
From the looks of it, if I am installing on my local machine then by
definition I have all the needed
FYI, I just merged removal of setting CMAKE_INSTALL_DEBUG_LIBRARIES from
ParaView.
On Wed, Jan 5, 2011 at 2:24 PM, Michael Jackson mike.jack...@bluequartz.net
wrote:
That is where I pulled the code from so I must have grabbed that version.
But I think I am misunderstanding what should be used
On Jan 5, 2011, at 2:36 PM, David Partyka wrote:
FYI, I just merged removal of setting CMAKE_INSTALL_DEBUG_LIBRARIES from
ParaView.
On Wed, Jan 5, 2011 at 2:24 PM, Michael Jackson mike.jack...@bluequartz.net
wrote:
That is where I pulled the code from so I must have grabbed that
