FYI, I just merged removal of setting CMAKE_INSTALL_DEBUG_LIBRARIES from ParaView.<div><br><div class="gmail_quote">On Wed, Jan 5, 2011 at 2:24 PM, Michael Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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.<br>
<br>
From the looks of it, if I am "installing" on my local machine then by definition I have all the needed runtime libraries in all the right places because I have installed Visual Studio which means placing copies of them in my installation location is probably NOT really needed. Right? Wrong?<br>
</blockquote><div><br></div><div>Right, infact, if you run your app and look at process explorer I am pretty sure you'll see it loaded msvcr9<blahblah>.dll from C:\Windows\winsxs\blah and not from the runtimes you have sitting right next to your executable.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Package/Installer Generation: This is meant to be served/given to others so the runtime libraries ARE needed, and NOT the Debug libraries (at least not officially) which means I should be using which CMake mechanism to make sure my installer is built correctly. Most of the time I am creating simple Zip installers as some of my clients can not run actual installers on their machines. Is there a tutorial some where? At this point I'll write one if someone can set me straight. Tired of spinning my wheels.<br>
</blockquote><div><br></div><div>I use clean VMs with nothing installed to test ParaView binaries. This is particularly good at showing you when you somehow didn't include the msvc runtime dlls.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
--<br>
</font><div class="im">Mike Jackson <<a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a>><br>
<br>
</div><div><div></div><div class="h5">On Jan 5, 2011, at 2:09 PM, David Partyka wrote:<br>
<br>
> 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.<br>
><br>
> On Wed, Jan 5, 2011 at 1:54 PM, Michael Jackson <<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>> wrote:<br>
> 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:<br>
><br>
> if (MSVC)<br>
> SET (CMAKE_INSTALL_DEBUG_LIBRARIES OFF)<br>
> INCLUDE (InstallRequiredSystemLibraries)<br>
> endif()<br>
><br>
> ___________________________________________________________<br>
> Mike Jackson <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
> Principal Software Engineer <a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a><br>
> BlueQuartz Software Dayton, Ohio<br>
><br>
> On Jan 5, 2011, at 1:31 PM, David Cole wrote:<br>
><br>
> > Just as an FYI:<br>
> ><br>
> > The Debug libraries for MSVC are not redistributable components. Do<br>
> > not build them into an installer. People who need to use them are<br>
> > required to have a corresponding Visual Studio installation on their<br>
> > machine.<br>
> ><br>
> > We provide access to those for INSTALL simply for testing the make<br>
> > install tree of a debug build, possibly even copying it over to<br>
> > another machine for testing.<br>
> ><br>
> > But it is not intended that the MSVC Debug libraries be packaged...<br>
> ><br>
> ><br>
> > On Wed, Jan 5, 2011 at 1:20 PM, Michael Jackson<br>
> > <<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>> wrote:<br>
> >> 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.<br>
> >><br>
> >> Any pointers? I'll start wading through both the CMake projects and the ParaView projects and see what if those yield any clues.<br>
> >> ___________________________________________________________<br>
> >> Mike Jackson <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
> >> Principal Software Engineer <a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a><br>
> >> BlueQuartz Software Dayton, Ohio<br>
> >><br>
> >> _______________________________________________<br>
> >> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
> >><br>
> >> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
> >><br>
> >> Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
> >><br>
> >> Follow this link to subscribe/unsubscribe:<br>
> >> <a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
> >><br>
> > _______________________________________________<br>
> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
> ><br>
> > Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
> ><br>
> > Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
> ><br>
> > Follow this link to subscribe/unsubscribe:<br>
> > <a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
><br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
><br>
<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br></div>