Re: [CMake] CPack - Windows 7 x64

On Tue, Jan 3, 2012 at 8:05 PM, Nicholas Yue wrote: > Hi, > >    I am building and installing full 64bit applications and libraries. > >    When I package it up as an installer via NSIS, it installs to "C:\Program > Files (x86)\" > >    What CPACK_ variables do I need to inform cpack that it shoul

Re: [CMake] CPack - Windows 7 x64

On Tue, Jan 3, 2012 at 8:05 PM, Nicholas Yue wrote: > > Hi, > >    I am building and installing full 64bit applications and libraries. > >    When I package it up as an installer via NSIS, it installs to "C:\Program > Files (x86)\" > >    What CPACK_ variables do I need to inform cpack that it sh

[CMake] CPack - Windows 7 x64

Hi, I am building and installing full 64bit applications and libraries. When I package it up as an installer via NSIS, it installs to "C:\Program Files (x86)\" What CPACK_ variables do I need to inform cpack that it should be installed in "C:\Program Files\" Regards -- Nichola

Re: [CMake] Bug fix requests for the *next* release of 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 sub

Re: [CMake] Bug fix requests for the *next* release of CMake...

On Monday 02 January 2012, David Cole wrote: > Hi all, > > Replies requested. Short replies only. 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

Re: [CMake] Running coverage analysis

There are ITK Utilities scripts that I plan to move into VTK. For the time being, you can run them on VTK if you have an ITK checkout. I have been doing this with some VTK classes I plan to add. The computeCodeCoverageLocallyForOneTest.sh is especially useful if you want to check coverage on a few

Re: [CMake] Incorrect implicit library selections in generated link statements

On Tue, Jan 3, 2012 at 2:30 PM, Schuchard, Matthew wrote: > I have a large static library comprised of C, C++, Fortran, and Ada source > files. > > I have a number of C, C++, Fortran, and Ada executables linking against this > library. > > > > When CMake generates the link statements in link.txt,

[CMake] Incorrect implicit library selections in generated link statements

I have a large static library comprised of C, C++, Fortran, and Ada source files. I have a number of C, C++, Fortran, and Ada executables linking against this library. When CMake generates the link statements in link.txt, the implicit libraries selected to be linked against from the possibiliti

Re: [CMake] Bug fix requests for the *next* release of CMake...

http://public.kitware.com/Bug/view.php?id=8438 http://public.kitware.com/Bug/view.php?id=11258 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://w

Re: [CMake] CMake still broken post-2.8.1

I'm back to this. I never got (or never understood!) an answer to this part of the thread, which is where the breakage occurred: -- If I comment out line 29 in CMakeDetermineCompilerId.cmake, it works with my old toolchain file, but fails later with the new one, because it appears to cal

[CMake] Setting a HTTP header when uploading test results

n: Attempt 3 of 3 Error when uploading file: /home/maciej/src/opencsw/pkg/cmake/trunk/work/solaris9-sparc/build-isa-sparcv8/cmake-2.8.7/Testing/20120103-1755/Build.xml Error message was: The requested URL returned error: 417 Problems when submitting via HTTP Errors while running CTe

Re: [CMake] Bug fix requests for the *next* release of CMake...

Might be nice to decide about this one: Sean -- 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.cmak

Re: [CMake] CMake 2.8.7-rc2 ready for testing!

On Friday 30 December 2011, Eric Noulard wrote: > 2011/12/30 David Cole : > > There is no conservative course here. There is a choice of whether to > > make CMake 2.8.7 behave the same as 2.8.6 or the same as 2.8.5. > > > > For this to be a showstopper it would have had to be reported before we >

Re: [CMake] on find_package and building dependencies

2012/1/3 Alexander Neundorf : >> you basically want: >> set(CMAKE_FIND_ROOT_PATH "/you/local/install/dir") >> before calling find_package(...) > > No, please don't. > CMAKE_FIND_ROOT_PATH is intended for cross-compiling, to tell cmake where the > root of the target file system is located. Ok my ba

Re: [CMake] on find_package and building dependencies

On Thursday 29 December 2011, Eric Noulard wrote: > 2011/12/29 Ryan Lewis : > > Hi, > > > > I really like CMake's find_package() utility for finding dependencies, > > but for some projects I have a > > separate local copy of the installed libraries, and I want to point > > find_package at a partic

Re: [CMake] CMake 2.8.7-rc2 ready for testing!

On Friday 30 December 2011, Alan W. Irwin wrote: > On 2011-12-30 11:06+0100 Eric Noulard wrote: > > 2011/12/27 Alan W. Irwin : > > > > Hi Alan, > > > >> The issue is that if I set CMAKE_LIBRARY_PATH to find a special > >> version of lapack/blas, only the lapack part of that is honored. For > >>

Re: [CMake] compiling problem cmake

hi, thnx for helping. interesting to see you use the 251 cmake unaltered for 256 and it works. I guess the path building problem is a mingw thing indeed. why would it create another CMakeFiles in CMakeTmp? Where can I find the script that prescribes this? I just added a screenie of explorer and

Re: [CMake] Wiki: version compatibility matrix

The Cite extension is now installed on the CMake wiki. See this page to see what mediawiki extensions are available: http://www.cmake.org/Wiki/Special:Version HTH, David On Mon, Jan 2, 2012 at 12:03 PM, Johannes Zarl wrote: > Hi David, > > I guess I'll have time this week to update the matri

Re: [CMake] Running coverage analysis

The way I have always approached problems like this is to check out what existing scripts are doing that are already successfully submitting coverage results. This one is on the VTK dashboard: http://cdash.org/CDash/viewNotes.php?buildid=1880030 This one on CMake: http://cdash.org/CDash/viewNotes

Re: [CMake] Running coverage analysis

On Tue, Jan 3, 2012 at 9:52 AM, David Cole wrote: > To actually run the coverage testing, you need to have tests added with > add_test in your CMakeLists file, then you need to run a ctest -S script > that calls ctest_coverage, or use one of the predefined coverage dashboard > targets. (Use 'make

Re: [CMake] Running coverage analysis

To actually run the coverage testing, you need to have tests added with add_test in your CMakeLists file, then you need to run a ctest -S script that calls ctest_coverage, or use one of the predefined coverage dashboard targets. (Use 'make help | grep Coverage' to see those.) On Jan 2, 2012, a

Re: [CMake] compiling problem cmake

Hi, On Ubuntu, compiling python 2.5.6 following the instruction listed here [1] works. [1] http://www.vtk.org/Wiki/BuildingPythonWithCMake#Building_Python_for_Linux_or_Windows Somebody with mingw will have to check what's wrong. Step by step: wget http://www.python.org/ftp/python/2.5.6/Python-2