Re: [CMake] Not matching versions of MSVC Runtime Libraries in Manifest
Very cool! +1 On Tue, Aug 9, 2011 at 3:28 PM, David Cole david.c...@kitware.com wrote: On Tue, Aug 9, 2011 at 3:27 PM, clin...@elemtech.com wrote: Here's my (not so complete) understanding... Public assemblies are searched before private ones. http://msdn.microsoft.com/en-us/library/aa374224(v=vs.85).aspx So, on your machine, you have the required CRT libraires in the winsxs folder. You also have a redirection that says to use a newer CRT library if a particular older one is requested. If another machine that you copy this software to doesn't have a shared CRT that will work, it falls back to the one you copied next to your application. So its a way to get updates and bug fixes to the CRT via windows updates, but still allow your application to work on older machines without the newer dlls, by using the ones you provided. Clint - Original Message - Yes, I think part of the issue is what is mentioned and I do have plugins (Qt based) and have taken the steps he lays out. But I am still curious as to why Dependency Walker says it is using one version of the runtime libraries when the Manifest (both external and embedded) says to use another. I am probably just missing something basic in all of this. ___ Mike Jackson www.bluequartz.net Principal Software Engineer mike.jack...@bluequartz.net BlueQuartz Software Dayton, Ohio On Aug 9, 2011, at 3:07 PM, Michael Wild wrote: On Tue 09 Aug 2011 06:48:34 PM CEST, Michael Jackson wrote: Not sure if this is a CMake issue or not but I'll give it a shot. I am packaging up my application using CPack (zip) and all seems fine. I get the MSVC runtime libraries copied and the manifest file created and all seems to run just fine. If I use Dependency Walker to look at exactly _which_ C/C++ runtime DLLs are being loaded it seems to indicate a newer version than what the manifest is saying. My Application seems to be requesting version 9.0.21022.8 in its manifest and in the executable itself (Embedded Manifest) but Dependency Walker says it is really loading the 9.0.30729.490 version from the winsxs folder. I am still really new to this with Visual Studio so I am not sure if I am doing something incorrect when writing the CPack code, something in Visual Studio, how I compiled all the dependent libraries or what but any help or pushes in a better direction would be greatly appreciated. System: Windows 7 X64 Pro. Visual Studio 2008. Compiling everything as 64 bit. The actual executables can be downloaded from http://dream3d.bluequartz.net. Thanks in advance. Not sure, but could it be the issue mentioned in Bills blog? http://www.kitware.com/blog/home/post/4 Michael ___ 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 Thanks for this pointer, Clinton. I'll add a comment to Bill's blog article that also points to this Microsoft page... Good reference. :-) David ___ 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
Re: [cmake-developers] Bug fix requests for the *next* release of CMake...
When using external_project, if GIT_TAG is modified the entire source tree is removed and re-cloned causing a full rebuild of said project. http://cmake.org/Bug/view.php?id=11403 On Tue, Mar 29, 2011 at 1:56 PM, David Cole david.c...@kitware.com wrote: Hi all, Now that we have released CMake 2.8.4, *now* would be a great time to prioritize bug fixes for the next release of CMake. Replies requested. Read on. *Just a short reply with bug numbers* or links to the bugs is all we need here. Please move specific discussions into the bugs themselves or start a new thread to talk about it... Replies on this thread should just be a collector for bug numbers. We are aiming for quarterly releases from now on, scheduling them every 3 or 4 months. That would make the next release of CMake version 2.8.5, scheduled to have an rc1 release candidate on Wed. April 27, 2011. If you have a particular issue that you think should be fixed for inclusion in 2.8.5, please bring it up by the end of this week. Ideally, each issue will be discussed as needed on the mailing list to come to any consensus about what should be done to fix it, and then an entry in the bug tracker may be used to keep it on the radar screen, and to track activity related to it. Patches are always welcome. Patches that include testing of any new features, or tests that prove a bug is really fixed on the dashboards, basically any patch with testing is preferred over a patch with no testing. Also, if you are *adding* code, then you also probably need to add *tests* of that code, so that the coverage percentage stays as is or rises. Please discuss issues here as needed, and add notes to existing issues in the bug tracker that you are interested in seeing fixed for 2.8.5 -- we will be looking at the mailing list and activity in the bug tracker to help prioritize the bug fixes that will occur over the next 4 weeks. Thanks, David Cole Kitware, Inc. P.S. - as a nice summary of what we accomplished in the CMake 2.8.4 release, see here: http://public.kitware.com/Bug/changelog_page.php -- it currently lists 127 issues that we resolved: nice job, everybody! (Many of those were specifically addressed because somebody brought it up in response to my similar email from just after 2.8.3... Don't be shy!) ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [CMake] [cmake-developers] Bug fix requests for the *next* release of CMake...
When using external_project, if GIT_TAG is modified the entire source tree is removed and re-cloned causing a full rebuild of said project. http://cmake.org/Bug/view.php?id=11403 On Tue, Mar 29, 2011 at 1:56 PM, David Cole david.c...@kitware.com wrote: Hi all, Now that we have released CMake 2.8.4, *now* would be a great time to prioritize bug fixes for the next release of CMake. Replies requested. Read on. *Just a short reply with bug numbers* or links to the bugs is all we need here. Please move specific discussions into the bugs themselves or start a new thread to talk about it... Replies on this thread should just be a collector for bug numbers. We are aiming for quarterly releases from now on, scheduling them every 3 or 4 months. That would make the next release of CMake version 2.8.5, scheduled to have an rc1 release candidate on Wed. April 27, 2011. If you have a particular issue that you think should be fixed for inclusion in 2.8.5, please bring it up by the end of this week. Ideally, each issue will be discussed as needed on the mailing list to come to any consensus about what should be done to fix it, and then an entry in the bug tracker may be used to keep it on the radar screen, and to track activity related to it. Patches are always welcome. Patches that include testing of any new features, or tests that prove a bug is really fixed on the dashboards, basically any patch with testing is preferred over a patch with no testing. Also, if you are *adding* code, then you also probably need to add *tests* of that code, so that the coverage percentage stays as is or rises. Please discuss issues here as needed, and add notes to existing issues in the bug tracker that you are interested in seeing fixed for 2.8.5 -- we will be looking at the mailing list and activity in the bug tracker to help prioritize the bug fixes that will occur over the next 4 weeks. Thanks, David Cole Kitware, Inc. P.S. - as a nice summary of what we accomplished in the CMake 2.8.4 release, see here: http://public.kitware.com/Bug/changelog_page.php -- it currently lists 127 issues that we resolved: nice job, everybody! (Many of those were specifically addressed because somebody brought it up in response to my similar email from just after 2.8.3... Don't be shy!) ___ cmake-developers mailing list cmake-develop...@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers ___ 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
Re: [CMake] Why is ExternalProject trigger-happy about re-downloading source?
http://cmake.org/Bug/view.php?id=11403 On Wed, Mar 9, 2011 at 2:50 PM, kent williams nkwmailingli...@gmail.comwrote: I've been running into this every since we updated to CMake 2.8.4, but I don't know if it's revision specific. Sometimes if I change CMakeLists.txt in various directories so that make will re-run cmake to pickup CMakeLists.txt changes, it triggers re-downloading VTK ITK from scratch. Is using GIT_REPOSITORY dumber than CVS_REPOSITORY SVN_REPOSITORY? If I set UPDATE_COMMAND to , it never re-downloads. But GIT_REPOSITORY seems to blow away the downloaded source for an external project and re-download it, even if the CMakeLists.txt change is unrelated to to the ExternalProject in question. Is there a way to suppress this behavior? ___ 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
Re: [cmake-developers] VS2010 fortran composer
I just tried this on a remote machine with the compiler and can confirm what John is seeing. That said. If you run msbuild on the top level solution you get a slightly more informative error. c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1msbuild Console1.sln Microsoft (R) Build Engine Version 3.5.30729.1 [Microsoft .NET Framework, Version 2.0.50727.4206] Copyright (C) Microsoft Corporation 2007. All rights reserved. Build started 3/7/2011 10:10:25 AM. Project c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1\Console1.sln on node 0 (default targets). Building solution configuration Debug|Win32. c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1\Console1.sln.cache : warning MSB4078: The project file Console1\Console1.vfproj is not supported by MSBuild and cannot be built. Done Building Project c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1\Console1.sln (default targets). Build succeeded. c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1\Console1.sln (default target) (1) - (Console1 target) - c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1\Console1.sln.cache : warning MSB4078: The project file Console1\Console1.vfproj is not supporte d by MSBuild and cannot be built. 1 Warning(s) 0 Error(s) Time Elapsed 00:00:00.01 On Mon, Mar 7, 2011 at 9:42 AM, Bill Hoffman bill.hoff...@kitware.comwrote: On Mon, Mar 7, 2011 at 9:17 AM, Biddiscombe, John A. biddi...@cscs.ch wrote: Bill What if you run DevEnv.exe from the command line with the /Upgrade on the vfproj file? Does it change it? Does it work with MSBuild after? No change. Still fails. http://software.intel.com/en-us/forums/showthread.php?t=81140 This is explained in the release notes for the Fortran compiler. Please read the section on VS2010.. yes I found this report - unfortunately it does not tell us anything useful. It deals with dependencies, which is different from our problem. I checked to see the the ALL_BUILD project was referencing the cmTryComile, (and it is), but changing this makes no difference - when running msbuild.exe we only treat the cmtrycompile and deleting all the other stuff doesn't solve anything. I'll file a bug report with intel and for now, use makefiles to kick off the generator and then switch.- could we not just use nmake always for the compiler detection step? When you file the report, do not include any mention of CMake. I would just tell them that you did this: 1. create a new hello world application with the IDE 2. run msbuild on the application 3. you get an error We can not use nmake to kick off the generator, it would not even be testing the same setup that the generator is creating. Might as well disable all try-compiles because it would not even be testing what the user would be seeing during the real build We might be able to use devenv /build, however in earlier versions of VS 2010 using devenv for running the tests of CMake caused devenv to crash multiple times... -Bill JB snippet from release notes below 3.6.2 Adjusting Project Dependencies If you are converting a project from an earlier version of Visual Studio and had established Project Dependencies, these are converted to References by Visual Studio 2010. A Fortran project that is referenced by a C/C++ project will prevent the C/C++ project from building, with an MSB4075 error. To solve this: 1. Right click on the C/C++ project and select References. 2. If any Fortran project is shown as a reference, click Remove Reference. Repeat this for all Fortran projects shown as a reference. Click OK. 3. Repeat the above steps for any other C/C++ project Now you have to reestablish project dependencies. 1. Right click on the C/C++ project and select Project Dependencies. 2. Check the box for each project that is a dependent of this project. 3. Click OK. 4. Repeat the above steps for any other C/C++ project that has dependencies. Unlike earlier versions of Visual Studio, Visual Studio 2010 does not automatically link in the output library of dependent projects, so you will need to add those libraries explicitly to the parent project under Linker Additional Dependencies. You can use the Visual Studio macros $(ConfigurationName) and $(PlatformName) as required to qualify the path. For example: ..\FLIB\$(ConfigurationName)\FLIB.lib Where $(ConfigurationName) will expand to Release or Debug, as appropriate. Similarly, $(PlatformName) will expand to Win32 or x64 as appropriate. ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [CMake] Cmake with Cray Fortran
FYI, if you want to build static on cray, Brad just checked in a fix into CMake yesterday that addresses -Bdynamic link flags showing up in the link line even though you're trying to build static, often resulting in your executable prefering to link against shared system libraries rather than static. This was causing issues linking static while building ParaView on Jaguar. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5abfb571843dba949e010f3b2840d8882d0f3d73 On Sat, Mar 5, 2011 at 11:21 AM, Eric Noulard eric.noul...@gmail.comwrote: 2011/3/5 Tim Gallagher tim.gallag...@gatech.edu: Eric, Excellent! Thanks! I don't know a whole lot about CMake (yet) -- would it be possible to make older versions aware of the compiler if I were to package only the updated files rather than install my own version of CMake? In other words, was it something simple like changing the CMakeFortranCompilerId.F file and if so, could I tell another version of CMake to use my own copy of that file? I don't know I am not the author of the fix, I think Brad King was the one who did this, may be he will answer that. It would be a lot easier if I only had to make our users put a few extra files somewhere than have them all install their own version of CMake in their home directories on all these Cray machines. May be deploying CMake 2.8.4 globally on each machine and set up appropriate module would even be easier for the users? Or may be this is not an option because you don'thave administrative privilege on those machines? -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ 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
Re: [CMake] Any issues using CMAKE with virus control?
I've had problems using CMake's external project feature and Antivirus (on Windows 7). When external project would download a tarball and extract it, often it would fail because the realtime protection would still be holding on to some of the files. The compromise was to excluding realtime protection on my development directories. On Thu, Jan 6, 2011 at 8:20 AM, Caron, Michael C. (US SSA) michael.ca...@baesystems.com wrote: My company has been tightening up the security of our systems and we have had some new security settings and new security software added to our machines. I've been using CMAKE to build both Linux and Windows deliverables for close to a year now with no significant problems. I tried to launch a windows build last night and when I came in this morning the build progress was hung at like 86%. This build has always built flawlessly in the past. Since we have seen some other issues where our security improvements have been less than helpful from a workflow stand point I'm thinking this is another such case. Anyone else have any experience with overly draconian security messing with a previously happy CMAKE system? Or perhaps issues getting CMAKE to work in a strict permissions and virus scanner environment? Michael Caron ___ 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
Re: [CMake] Detecting fmpich
FindMPI is getting a major facelift for CMake 2.8.4 in which finding fortran related libraries/compilers is a new feature. Stay tuned! On Thu, Jan 6, 2011 at 9:23 AM, ycollette.nos...@free.fr wrote: Hello, Is it possible to detect fmpich using find_package(MPI) ? I haven't found any solution yet ... Best regards, YC ___ 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
Re: [CMake] Packaging on Windows with VS2008 and ZIP - Runtime Libraries Inclusion
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
Re: [CMake] Packaging on Windows with VS2008 and ZIP - Runtime Libraries Inclusion
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 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 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? Right, infact, if you run your app and look at process explorer I am pretty sure you'll see it loaded msvcr9blahblah.dll from C:\Windows\winsxs\blah and not from the runtimes you have sitting right next to your executable. 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. 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. -- Mike Jackson www.bluequartz.net On Jan 5, 2011, at 2:09 PM, David Partyka wrote: 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
Re: [CMake] InstallRequiredSystemLibraries Comment
You override this behavior by setting CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP
to ON and then providing your own install rules. See the following chunk
from ParaView.
# Add install rules for required system runtimes such as MSVCRxx.dll
SET (CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP ON)
INCLUDE(InstallRequiredSystemLibraries)
IF (CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS)
INSTALL(FILES ${CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS}
DESTINATION ${PV_INSTALL_BIN_DIR}
PERMISSIONS OWNER_WRITE OWNER_READ OWNER_EXECUTE GROUP_READ
GROUP_EXECUTE WORLD_READ
COMPONENT Runtime)
# Install the runtimes to the lib dir as well since python modules are
# installed in that directory and the manifest files need to present there
as
# well.
INSTALL(FILES ${CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS}
DESTINATION ${PV_INSTALL_LIB_DIR}
PERMISSIONS OWNER_WRITE OWNER_READ OWNER_EXECUTE GROUP_READ
GROUP_EXECUTE WORLD_READ
COMPONENT Runtime)
ENDIF (CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS)
On Wed, Jan 5, 2011 at 2:30 PM, Michael Jackson mike.jack...@bluequartz.net
wrote:
From the CMake 2.8.3 release I am using inside the
InstallRequiredSystemLibraries.cmake file all the way at the bottom is this:
IF(WIN32)
INSTALL_PROGRAMS(/bin ${CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS})
ELSE(WIN32)
INSTALL_PROGRAMS(/lib ${CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS})
ENDIF(WIN32)
Which FORCES me to install all my programs in bin on windows. Having
another directory under the main installation directory, IMHO, isn't needed
for some smaller projects. Besides hacking CMake, are there any plans to
make the installation location a variable? For instance I would like to just
install them into . instead of bin. Should I file a bug/feature request?
Thanks
___
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
