Re: [CMake] continuous builds best practices?

I use ctest scripts. Most itk and vtk dashboards are driven by ctest scripts. Here is the one I use for a continuous Borland build. You need to start it once a day. ctest will do the proper continuous checking of the repository: http://www.cdash.org/CDash/viewNotes.php?buildid=305082 Here is one

Re: [CMake] continuous builds best practices?

On Thu, Apr 2, 2009 at 5:06 PM, Alexander Neundorf wrote: > On Wednesday 01 April 2009, Philip Lowman wrote: > > Is there a best practices for kicking off Continuous builds using ctest? > > What do most people do for this? > > > > I know about svn hooks but I don't want multiple builds spawned for

Re: [CMake] perennial question, how to setup environment for simple tests

On Thu, Apr 2, 2009 at 3:19 PM, Ian Monroe wrote: > I've seen this question in the archives, but I was wondering if > there's been any progress since I last saw it asked (>1 year ago). > > I have some unit tests. I need to run a command or two and set some > environmental variables before all the

Re: [CMake] Need advice for unit test structure

On Apr 2, 2009, at 11:04 PM, Philip Lowman wrote: On Thu, Apr 2, 2009 at 5:07 PM, Robert Dailey wrote: If there was some way for CMake to utilize "solution folders" in Visual Studio, we could easily organize unit tests into a hierarchy. This way the solution explorer would not be cluttered

Re: [CMake] Need advice for unit test structure

On Thu, Apr 2, 2009 at 5:07 PM, Robert Dailey wrote: > If there was some way for CMake to utilize "solution folders" in Visual > Studio, we could easily organize unit tests into a hierarchy. This way the > solution explorer would not be cluttered and we'd still be able to have 1 > project per uni

[CMake] Disabling RTTI in a portable way

Is there a portable way of disabling Runtime Type Information (RTTI) through CMake? I hope I don't have to strangle CMake too much to get this basic functionality... ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.k

Re: [CMake] CMake could really use a debugger...

On Thursday 02 April 2009, Robert Dailey wrote: > That's the thing that has the "Returning to" and "Entering" messages right? No, it prints every cmake line which is executed. Alex ___ Powered by www.kitware.com Visit other Kitware open-source projects

Re: [CMake] Output directory for generated ui_Header.h from Header.ui

On Thursday 02 April 2009, Ivan Chupahin wrote: > Hi,folks! > > My project uses Qt4 and i need to generate *.h files from *.ui files. For > that i use QT4_WRAP_UI macro. But it generete *.h files in a derectory > where CMake is running. Maybe exit some CMake variable for point an output > directory

Re: [CMake] link_libraries() deprecated. Why?

On Thursday 02 April 2009, Brad King wrote: > Alex, > > Looking at history I see this was deprecated by a patch you sent me. > Originally we called the command 'discouraged'. Why did we change > to 'deprecated'? I don't remember why we changed the wording. The "deprecated" commands are commands w

Re: [CMake] continuous builds best practices?

On Wednesday 01 April 2009, Philip Lowman wrote: > Is there a best practices for kicking off Continuous builds using ctest? > What do most people do for this? > > I know about svn hooks but I don't want multiple builds spawned for each > commit, just the latest commit when the machines are idle. A

Re: [CMake] Need advice for unit test structure

If there was some way for CMake to utilize "solution folders" in Visual Studio, we could easily organize unit tests into a hierarchy. This way the solution explorer would not be cluttered and we'd still be able to have 1 project per unit test. On Thu, Apr 2, 2009 at 4:03 PM, Daniel Blezek wrote:

Re: [CMake] How to pass values up to parent CMakeLists.txt

On Wednesday 01 April 2009, James Bigler wrote: ... > You can also look into define/get/set_property, but I've never used those. Yes, I'd suggest a GLOBAL property for this. It's IMO the cleanest way to do it. Alex ___ Powered by www.kitware.com Visit

Re: [CMake] Need advice for unit test structure

Hi Robert, I don¹t have any suggestions about the compile time unit tests, but we¹ve been using the Google testing framework for the last 6 months and have been very happy with it. I wrote up some details related to ITK here: http://www.itk.org/Wiki/Proposals:Increasing_ITK_Code_Coverage#Googl

Re: [CMake] CMake could really use a debugger...

haha, good one. I replied on an impulse. I didn't even think about googling it :) Thanks for the link ;) On Thu, Apr 2, 2009 at 2:55 PM, Sean McBride wrote: > On 4/2/09 2:49 PM, Robert Dailey said: > > >What is GDB? > > Sorry, can't resist: > > > -- > __

[CMake] Need advice for unit test structure

Hi, Currently we have a directory called "test" under each project we have. Each source file (CPP) results in 1 unit test project being created. So if we have a project named "foobar", it would be structured like this on the filesystem: foobar/test/test1.cpp foobar/test/test2.cpp foobar/test/test3

Re: [CMake] CMake could really use a debugger...

On 4/2/09 2:49 PM, Robert Dailey said: >What is GDB? Sorry, can't resist: -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Sof

Re: [CMake] CMake could really use a debugger...

On Thu, Apr 2, 2009 at 1:38 PM, Jed Brown wrote: > On Thu 2009-04-02 13:17, Robert Dailey wrote: > > It would be great to see CMake provide some more debug-related commands > later. > > Perhaps CMake could even implement its own prompt. > > It would be extremely useful to be able to set watchpoin

[CMake] perennial question, how to setup environment for simple tests

I've seen this question in the archives, but I was wondering if there's been any progress since I last saw it asked (>1 year ago). I have some unit tests. I need to run a command or two and set some environmental variables before all the tests start. Does CMake have a solution for this yet? Are th

Re: [CMake] CMake could really use a debugger...

On Thu 2009-04-02 13:17, Robert Dailey wrote: > It would be great to see CMake provide some more debug-related commands later. > Perhaps CMake could even implement its own prompt. It would be extremely useful to be able to set watchpoints and breakpoints. Basically the GDB commands break, watch,

Re: [CMake] CMake could really use a debugger...

Good idea, but this requires domain knowledge. For someone completely unfamiliar with the CMake code-base, this would be impractical. However I still appreciate the thought! It would be great to see CMake provide some more debug-related commands later. Perhaps CMake could even implement its own pr

Re: [CMake] Core dump after "- Check for working C compiler" on OS400 ( i5/OS PowerPC 32bit) with 2.6.2

Bill Hoffman schrieb: Can you run cmake in a debugger? It did not tell me much. Maybe because the custom compiled one lacked debug info. I did not follow up on this. From what I guessed based on "grepping" through the source it could be something super simple that is causing the exception, s

Re: [CMake] CMake could really use a debugger...

On Thu, Apr 2, 2009 at 11:51 AM, Robert Dailey wrote: > That's the thing that has the "Returning to" and "Entering" messages right? > If it is, that's somewhat helpful but not anywhere near what I'm asking > for. Think of how visual studio debugs C++ code. That's exactly the most > optimal debugg

Re: [CMake] CMake could really use a debugger...

That's the thing that has the "Returning to" and "Entering" messages right? If it is, that's somewhat helpful but not anywhere near what I'm asking for. Think of how visual studio debugs C++ code. That's exactly the most optimal debugging method I would like to see for CMake. Here's a couple of abi

Re: [CMake] incrementally adding source file properties

On 2 Apr 2009, at 19:12, Bill O'Hara wrote: Is it possible to incrementally add new properties to source files? In two parts of a large build there are cases where it'd be very convenient to be able to do this: set_source_file_properties(foo.c PROPERTIES COMPILE_FLAGS "-m32") set_source_fi

Re: [CMake] incrementally adding source file properties

2009/4/2 Eric Noulard : > 2009/4/2 Bill O'Hara : >> Is it possible to incrementally add new properties to source files? In two >> parts of a large build there are cases where it'd be very convenient to be >> able to do this: >> >> set_source_file_properties(foo.c PROPERTIES COMPILE_FLAGS "-m32") >>

Re: [CMake] incrementally adding source file properties

2009/4/2 Bill O'Hara : > Is it possible to incrementally add new properties to source files? In two > parts of a large build there are cases where it'd be very convenient to be > able to do this: > > set_source_file_properties(foo.c PROPERTIES COMPILE_FLAGS "-m32") > > set_source_file_properties(fo

[CMake] incrementally adding source file properties

Is it possible to incrementally add new properties to source files? In two parts of a large build there are cases where it'd be very convenient to be able to do this: set_source_file_properties(foo.c PROPERTIES COMPILE_FLAGS "-m32") set_source_file_properties(foo.c PROPERTIES COMPILE_FLAGS "-g")

Re: [CMake] CMake could really use a debugger...

Robert Dailey wrote: I can't tell you how hard it is to hunt down strange behavior in CMake. Often times I would save myself 30 minutes of time on each of the hard bug fixes if I could just step through each line of logic as it was being executed and view the values of variables in a "watch" wi

Re: [CMake] Win32: Find location of VS redistributable runtime files ?

James Bigler wrote: > On Thu, Apr 2, 2009 at 7:49 AM, Stephen Collyer > mailto:scoll...@netspinner.co.uk>> wrote: > > > 2009/4/2 Philip Lowman mailto:phi...@yhbt.com>> > > On Thu, Apr 2, 2009 at 7:00 AM, Stephen Collyer > mailto:scoll...@netspinner.co.uk>> > wrote: > >

[CMake] CMake could really use a debugger...

I can't tell you how hard it is to hunt down strange behavior in CMake. Often times I would save myself 30 minutes of time on each of the hard bug fixes if I could just step through each line of logic as it was being executed and view the values of variables in a "watch" window of some sort. Does a

Re: [CMake] Win32: Find location of VS redistributable runtime files ?

On Thu, Apr 2, 2009 at 7:49 AM, Stephen Collyer wrote: > > 2009/4/2 Philip Lowman > > On Thu, Apr 2, 2009 at 7:00 AM, Stephen Collyer > > wrote: >> >>> In the course of installation, I want to copy the redistributable C++ >>> runtime libs >>> directory from VS into my deliverable package. However

Re: [CMake] cpack and PackageMaker

Benne, Kyle wrote: Hello CMake Users, Quick question. Does CPack support pre and post flight scripts with the PackageMaker generator? Yes, it does, CMake uses this for installing the command line tools. SET(CPACK_POSTFLIGHT_SCRIPT "@CMAKE_POSTFLIGHT_SCRIPT@") SET(CPACK_POSTUPGR

[CMake] cpack and PackageMaker

Hello CMake Users, Quick question. Does CPack support pre and post flight scripts with the PackageMaker generator? Regards, Kyle ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource

Re: [CMake] Core dump after "- Check for working C compiler" on OS400 ( i5/OS PowerPC 32bit) with 2.6.2

Bill Hoffman schrieb: Ulf Wendel wrote: Hi, CMake 2.6.2 gives me a crash on OS/400 (i5/OS PowerPC 32bit): -- The C compiler identification is VisualAge -- The CXX compiler identification is VisualAge -- Check for working C compiler: /QOpenSys/vac600/usr/vacpp/bin/xlc_r terminate called after t

Re: [CMake] Win32: Find location of VS redistributable runtime files ?

2009/4/2 Philip Lowman > On Thu, Apr 2, 2009 at 7:00 AM, Stephen Collyer > wrote: > >> In the course of installation, I want to copy the redistributable C++ >> runtime libs >> directory from VS into my deliverable package. However, this should work >> with >> both VS8 and VS9. Could someone tell

Re: [CMake] autoheader

Thanks for the clarifications. Perhaps my err in this discussion is by referencing the Find functions too generally, and early on too specifically... Philip Lowman wrote: 1. Just because you call find_package() on a package doesn't mean that you need a preprocessor definition in your code in ord

Re: [CMake] link_libraries() deprecated. Why?

Alex, Looking at history I see this was deprecated by a patch you sent me. Originally we called the command 'discouraged'. Why did we change to 'deprecated'? Marcel Loose wrote: Thanks for your reply. Your solution is ok, but it looks a bit like a workaround for a feature that is missing, but

Re: [CMake] Core dump after "- Check for working C compiler" on OS400 ( i5/OS PowerPC 32bit) with 2.6.2

Ulf Wendel wrote: Hi, CMake 2.6.2 gives me a crash on OS/400 (i5/OS PowerPC 32bit): -- The C compiler identification is VisualAge -- The CXX compiler identification is VisualAge -- Check for working C compiler: /QOpenSys/vac600/usr/vacpp/bin/xlc_r terminate called after throwing an instance of

[CMake] Core dump after "- Check for working C compiler" on OS400 ( i5/OS PowerPC 32bit) with 2.6.2

Hi, CMake 2.6.2 gives me a crash on OS/400 (i5/OS PowerPC 32bit): -- The C compiler identification is VisualAge -- The CXX compiler identification is VisualAge -- Check for working C compiler: /QOpenSys/vac600/usr/vacpp/bin/xlc_r terminate called after throwing an instance of 'std::logic_error'

Re: [CMake] Win32: Find location of VS redistributable runtime files ?

On Thu, Apr 2, 2009 at 7:00 AM, Stephen Collyer wrote: > In the course of installation, I want to copy the redistributable C++ > runtime libs > directory from VS into my deliverable package. However, this should work > with > both VS8 and VS9. Could someone tell me how I can detect the build > env

Re: [CMake] link_libraries() deprecated. Why?

On Thu, Apr 2, 2009 at 4:03 AM, Marcel Loose wrote: > Hi Philip, > > Thanks for your reply. Your solution is ok, but it looks a bit like a > workaround for a feature that is missing, but was once there: > link_libraries(). > > To me, it's not really clear why link_libraries() has been deprecated

Re: [CMake] Output directory for genereated ui_Header.h files

Hi, I wrote this macro to generate my ui.[ch] and moc files in my source directory. Use it as a QT4_WRAP_UI replacement. The macro also creates a "ui" target which generates all these files. (Note: I use it with Qt 3, and did not check if uic is used the same way on Qt 4. #

[CMake] Win32: Find location of VS redistributable runtime files ?

In the course of installation, I want to copy the redistributable C++ runtime libs directory from VS into my deliverable package. However, this should work with both VS8 and VS9. Could someone tell me how I can detect the build environment and locate the appropriate directory to do this ? For examp

Re: [CMake] Output directory for genereated ui_Header.h files

On 02.04.09 16:46:51, Ivan Chupahin wrote: > Hi,folks! > > My project uses Qt4 and i need to generate *.h files from *.ui files. For > that i use QT4_WRAP_UI macro. But it generete *.h files in a derectory where > CMake is running. That is the correct place. All generated files should be in the b

[CMake] Output directory for genereated ui_Header.h files

Hi,folks! My project uses Qt4 and i need to generate *.h files from *.ui files. For that i use QT4_WRAP_UI macro. But it generete *.h files in a derectory where CMake is running. Maybe exist some CMake variable for point an output directory for that generated files or some other tools? ___

Re: [CMake] Xcode generator

On 2 Apr 2009, at 02:14, E. Wing wrote: As you can see, when a rebuild is done, the template gets copied to "main.cpp" which in turn is compiled and linked. This works great in Xcode. But, whenever I change the template, i.e. my CUDA sources, I have to run the build twice to make the changes ap

Re: [CMake] link_libraries() deprecated. Why?

Hi Philip, Thanks for your reply. Your solution is ok, but it looks a bit like a workaround for a feature that is missing, but was once there: link_libraries(). To me, it's not really clear why link_libraries() has been deprecated and, for example, include_directories() has not. IMHO, using targe

Re: [CMake] how-to get cmake command line after running ccmake

If you do create this script, would you mind sharing it in this list?. I think it may come in handy to many of us at one time or another. Thanks in advance! Adolfo On Wed, Apr 1, 2009 at 11:06 PM, Darren Weber wrote: > > Yes, this is the feature that I'm looking for. I want to use ccmake for >

[CMake] Output directory for generated ui_Header.h from Header.ui

Hi,folks! My project uses Qt4 and i need to generate *.h files from *.ui files. For that i use QT4_WRAP_UI macro. But it generete *.h files in a derectory where CMake is running. Maybe exit some CMake variable for point an output directory for that generated files or some other tools?