Re: [CMake] call already made makefile

2010-11-05 Thread SK
On Fri, Nov 5, 2010 at 1:04 PM, Alan W. Irwin wrote: > I agree the above idea should work, but dropping add_custom_command > completely and moving the COMMAND to add_custom_target instead (and > dropping all file DEPENDS for the custom target) is even a simpler way > to insure COMMAND gets execute

Re: [CMake] header files with visual studio

2010-11-05 Thread John Drescher
> So, the question is actually: > > Is there a way to have CMake automatically add included headers to visual > studio project files or do you need to use a dependency system to generate > the lists by hand? > Take a look at this: http://stackoverflow.com/questions/1167154/listing-header-files-in-

Re: [CMake] header files with visual studio

2010-11-05 Thread Oliver kfsone Smith
Michael Jackson said the following on 11/4/2010 12:34 PM: Like, others have stated: You MUST include them in the add_executable or add_library call. The macro I give above can help keep those files organized in the Project/Solution file if you want the organization to mimic the file system for

Re: [CMake] Using gcov/lcov and valgrind with cmake

2010-11-05 Thread Bill Lorensen
It should be done in the CMakeCache.txt file. In most projects, with multiple developers and multiple platforms, you would not want to perform coverage on every build. Look at VTK: http://www.cdash.org/CDash/index.php?project=VTK or ITK: http://www.cdash.org/CDash/index.php?project=Insight These to

Re: [CMake] call already made makefile

2010-11-05 Thread Alan W. Irwin
On 2010-11-05 14:12-0400 David Cole wrote: On Fri, Nov 5, 2010 at 2:00 PM, SK wrote: On Thu, Nov 4, 2010 at 9:23 PM, SK wrote: On Thu, Nov 4, 2010 at 6:09 PM, Alan W. Irwin wrote: then the custom make command should always be run (since it has no DEPENDS option), Alan, you are absolutely

Re: [CMake] call already made makefile

2010-11-05 Thread Alan W. Irwin
On 2010-11-05 11:00-0700 SK wrote: On Thu, Nov 4, 2010 at 9:23 PM, SK wrote: On Thu, Nov 4, 2010 at 6:09 PM, Alan W. Irwin wrote: then the custom make command should always be run (since it has no DEPENDS option), Alan, you are absolutely right!! No, sorry. Only if the add_custom_comman

Re: [CMake] call already made makefile

2010-11-05 Thread David Cole
On Fri, Nov 5, 2010 at 2:00 PM, SK wrote: > On Thu, Nov 4, 2010 at 9:23 PM, SK wrote: >> On Thu, Nov 4, 2010 at 6:09 PM, Alan W. Irwin >> wrote: >>> then the custom make command >>> should always be run (since it has no DEPENDS option), >> >> Alan, you are absolutely right!! > > No, sorry.  Onl

Re: [CMake] call already made makefile

2010-11-05 Thread SK
On Thu, Nov 4, 2010 at 9:23 PM, SK wrote: > On Thu, Nov 4, 2010 at 6:09 PM, Alan W. Irwin > wrote: >> then the custom make command >> should always be run (since it has no DEPENDS option), > > Alan, you are absolutely right!! No, sorry. Only if the add_custom_command output does not exist as o

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

2010-11-05 Thread Bill Hoffman
On 11/5/2010 10:48 AM, Rolf Eike Beer wrote: 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.4 and scheduled to have an "rc1" release candidate in approximately mid-January, 2011, target date: Wed. 1/12/

Re: [CMake] findAtlas cmake

2010-11-05 Thread luxInteg
On Thursday 04 November 2010 16:00:05 Michael Wild wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 11/04/2010 05:10 PM, luxInteg wrote: > > On Wednesday 03 November 2010 05:37:45 Michael Wild wrote: > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA1 > >> > >> Hi > >> > >> On

[CMake] cmake gfortran project question

2010-11-05 Thread luxInteg
Greetings, I have a little learning progect using cmake with gfortran. SOURCE files: .f, .f xxx.f and .f .y I want to do the following:- a) create a shared library libFFF.so and a static one libFFF.a (from say xxx.f and yyy.f) b) find installed fortran librar

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

2010-11-05 Thread Marcel Loose
Hi David, I've got one more, one that I just entered in Mantis. #11410 - Result of IF() is inconsistent Regards, Marcel Loose. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.

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

2010-11-05 Thread Rolf Eike Beer
Am Freitag, 5. November 2010 schrieb Marcel Loose: > Hi David, > # 8466 - Provide finer control than pass/fail for a test program CTest +1 from me for this one signature.asc Description: This is a digitally signed message part. ___ Powered by www.kitw

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

2010-11-05 Thread Luigi Calori
On 04/11/2010 21.48, Kalev Lember wrote: Hi, I would love to have support for CFBundle (.plugin) on Mac. http://www.vtk.org/Bug/view.php?id=11295 Me too, +1 for this bug also, for using the same project (FireBreath) +1 for FindBoost support to "CMakeified" version of Boost at "http://gito

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

2010-11-05 Thread Marcel Loose
Hi David, Since you asked, I would really like the following issues to be addressed: #11368 - Let CTest return with an error status when compiler errors occur #10335 - FIND_XXX problem with symlinks when using ENV # 8466 - Provide finer control than pass/fail for a test program CTest Best rega

Re: [CMake] EXECUTABLE_OUTPUT_PATH is empty in Nightly target

2010-11-05 Thread Rolf Eike Beer
Am Freitag, 5. November 2010 schrieb Gerhard Gappmeier: > Hi What relationship does this question have to the mail you are quoting below? Don't top-post. Start new threads for new discussions. Otherwise it is a pain to follow discussions. > when you checkout the tutorial you'll see that the Nig

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

2010-11-05 Thread Rolf Eike Beer
Am Donnerstag, 4. November 2010 schrieb David Cole: > Hi all, > > Now that we have released CMake 2.8.3, *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

Re: [CMake] EXECUTABLE_OUTPUT_PATH is empty in Nightly target

2010-11-05 Thread Bill Lorensen
David, Thanks, I did mean CMakeCache.txt. Bill On Fri, Nov 5, 2010 at 10:38 AM, Gerhard Gappmeier wrote: > Hi > > when you checkout the tutorial you'll see that the NightlyMemcheck > target does not work. > (git clone git://github.com/gergap/helloworld.git) > > All tests fail because I'm using

[CMake] EXECUTABLE_OUTPUT_PATH is empty in Nightly target

2010-11-05 Thread Gerhard Gappmeier
Hi when you checkout the tutorial you'll see that the NightlyMemcheck target does not work. (git clone git://github.com/gergap/helloworld.git) All tests fail because I'm using the EXECUTABLE_OUTPUT_PATH variable to find the test executable. e.g. ADD_TEST(SimpleTest ${EXECUTABLE_OUTPUT_PATH}/hello

Re: [CMake] Using gcov/lcov and valgrind with cmake

2010-11-05 Thread Gerhard Gappmeier
Sorry, I meant "David and Bill" ;-) Am 05.11.2010 13:39, schrieb David Cole: > Bill means your CMakeCache.txt file, not your CMakeLists.txt file. > (Pretty sure...) :-) > > > On Fri, Nov 5, 2010 at 8:30 AM, Bill Lorensen wrote: >> Try adding these (with proper paths) to your CMakeLists.txt file

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

2010-11-05 Thread Michael Jackson
___ Mike Jackson www.bluequartz.net Principal Software Engineer mike.jack...@bluequartz.net BlueQuartz Software Dayton, Ohio On Nov 5, 2010, at 10:06 AM, Andreas Pakulat wrote: On 05.11.10 09:36:

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

2010-11-05 Thread Andreas Pakulat
On 05.11.10 09:36:39, Michael Jackson wrote: > I have an idea for a feature that might help resolve some of the > "Find***" issues. I would like to see CMake implement some sort of > "Software Update" mechanism where you could tell CMake to check a > central server for any updated FindXXX.cma

Re: [CMake] Using gcov/lcov and valgrind with cmake

2010-11-05 Thread Gerhard Gappmeier
Hi David and Cole, I don't understand how it should help to add this to CMakeCache.txt. This file is only temp file and is not checked in the repo. Can the MEMORY_CHECK options also be set in the CMakeLists.txt? I have the coverage test working at the moment using this construct in the CMakeLists

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

2010-11-05 Thread Michael Jackson
I have an idea for a feature that might help resolve some of the "Find***" issues. I would like to see CMake implement some sort of "Software Update" mechanism where you could tell CMake to check a central server for any updated FindXXX.cmake files and then download them into the cmake inst

Re: [CMake] Using gcov/lcov and valgrind with cmake

2010-11-05 Thread David Cole
Bill means your CMakeCache.txt file, not your CMakeLists.txt file. (Pretty sure...) :-) On Fri, Nov 5, 2010 at 8:30 AM, Bill Lorensen wrote: > Try adding these (with proper paths) to your CMakeLists.txt file: > CMAKE_BUILD_TYPE:STRING=Debug > COVERAGE_COMMAND:FILEPATH=/usr/bin/gcov > CMAKE_C_FLA

Re: [CMake] Using gcov/lcov and valgrind with cmake

2010-11-05 Thread Bill Lorensen
Try adding these (with proper paths) to your CMakeLists.txt file: CMAKE_BUILD_TYPE:STRING=Debug COVERAGE_COMMAND:FILEPATH=/usr/bin/gcov CMAKE_C_FLAGS:STRING=-g -O0 -fprofile-arcs -ftest-coverage CMAKE_CXX_FLAGS:STRING=-g -O0 -fprofile-arcs -ftest-coverage CTEST_MEMORYCHECK_COMMAND:FILEPATH=/usr/

Re: [CMake] Linking Boost on Linux on 64bit host and 32bit target

2010-11-05 Thread Philip Lowman
On Thu, Nov 4, 2010 at 12:31 PM, Michael Jackson < mike.jack...@bluequartz.net> wrote: > Clean out your build folder first. > export BOOST_ROOT=/home/kknox/sdk/boost_1_44_0 > ==> that needs to be an actual "installation", a staged area will probably > NOT work to find boost as FindBoost is looking

Re: [CMake] Using gcov/lcov and valgrind with cmake

2010-11-05 Thread Gerhard Gappmeier
Thanks for your answer. I also made some progress meanwhile. One reason why coverage didn't work was ccache :-( Now it basically works, but only when settings the CFLAGS and LDFLAGS manually in the CMakeLists.txt. I expected this would be done automatically when using NightlyCoverage... I prepare

Re: [CMake] call already made makefile

2010-11-05 Thread David Cole
On Fri, Nov 5, 2010 at 5:17 AM, Michael Hertling wrote: > On 11/05/2010 05:23 AM, SK wrote: > > On Thu, Nov 4, 2010 at 6:09 PM, Alan W. Irwin > wrote: > >> then the custom make command > >> should always be run (since it has no DEPENDS option), > > > > Alan, you are absolutely right!! I missed t

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

2010-11-05 Thread Adam J Richardson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi David, > Replies requested. CMake is already pretty awesome from my POV, but since you ask... > Replies on this thread should just be a collector for bug numbers. Afraid I don't have a bug number, but I can explain quickly. > If you have a part

Re: [CMake] call already made makefile

2010-11-05 Thread Michael Hertling
On 11/05/2010 05:23 AM, SK wrote: > On Thu, Nov 4, 2010 at 6:09 PM, Alan W. Irwin > wrote: >> then the custom make command >> should always be run (since it has no DEPENDS option), > > Alan, you are absolutely right!! I missed this since the external > makefile I need actually does have a depen

Re: [CMake] call already made makefile

2010-11-05 Thread Michael Hertling
On 11/05/2010 02:09 AM, Alan W. Irwin wrote: > On 2010-11-04 16:29-0700 SK wrote: > >> On Sat, Oct 30, 2010 at 8:31 AM, Alan W. Irwin >> wrote: >>> On 2010-10-29 20:50-0700 mina adel wrote: >>> Hi All I have an open source code that I use in my project. This open source code >