Re: [cmake-developers] Failures re bzip2 in the dashboard

2013-02-20 Thread Richard Wackerbarth
ctest version 2.8.10.20121106-g262ff I blew away the CMake-build tree. New revision of repository is: aaa9ccf325b386d8b500c0b95a2cac1409375d51 It failed again. Richard On Feb 20, 2013, at 12:19 PM, Brad King brad.k...@kitware.com wrote: On 02/20/2013 01:06 PM, Richard Wackerbarth wrote

Re: [cmake-developers] ReactOS: Important filed bug reports went to backlog en masse

2012-08-14 Thread Richard Wackerbarth
Colloquy http://colloquy.info/downloads.html works well for me. On Aug 14, 2012, at 10:18 AM, David Cole wrote: Sorry about that -- I did indeed miss that you were asking to chat with me by IRC or some other IM. How about just a G+ chat session? Or can you recommend a Mac or Windows IRC

[cmake-developers] CMake + Ninja working almost everywhere

2012-07-19 Thread Richard Wackerbarth
On Jul 19, 2012, at 9:32 AM, Bill Hoffman wrote: On 7/19/2012 12:30 AM, Claus Klein wrote: I am happy to see it works now and Ninja is eanabled and Mac Yes, it is passing all test on the Mac. There was one build error last night but I see that has been fixed this morning. So, thanks to

Re: [cmake-developers] CMake + Ninja working almost everywhere

2012-07-19 Thread Richard Wackerbarth
That's the kind of effect that I suspected. So, is this an error in CMake, Ninja, or FreeBSD ? On Jul 19, 2012, at 10:19 AM, Bill Hoffman wrote: On 7/19/2012 10:55 AM, Richard Wackerbarth wrote: The remaining issue is that the FreeBSD build seems to show some random failures on the coverage

Re: [cmake-developers] Why not disable the Unix Makefiles generator for Darwin?

2012-07-14 Thread Richard Wackerbarth
By default, Ninja is disabled on Darwin because it has NEVER worked for a number of the scenarios in the test suite. These have to do with building OSX packages, etc.) If YOU need to use certain ninja capabilities and are not affected by those shortcomings, you can easily build a version with

Re: [CMake] Strange behavior with Nightly builds

2012-06-22 Thread Richard Wackerbarth
and revise your expectations. The only difference is that the nightly builds starts from an empty build directory (the directory content are removed). A typical distinction. Thanks in advance Best Regards Am 21. Jun 2012 um 20:20 schrieb Richard Wackerbarth rich...@nfsnet.org: From

Re: [CMake] Strange behavior with Nightly builds

2012-06-22 Thread Richard Wackerbarth
are removed). A typical distinction. Thanks in advance Best Regards Am 21. Jun 2012 um 20:20 schrieb Richard Wackerbarth rich...@nfsnet.org: From reading this, I get the distinct impression that your are not interpreting the meaning of nightly in the same way that the rest of us are doing

Re: [CMake] Strange behavior with Nightly builds

2012-06-21 Thread Richard Wackerbarth
From reading this, I get the distinct impression that your are not interpreting the meaning of nightly in the same way that the rest of us are doing so. Let's assume the following: At 15 minutes past each hour, a new commit is added to the repository. For the sake of description, the zeroth

Re: [CMake] Strange behavior with Nightly builds

2012-06-14 Thread Richard Wackerbarth
the last command line argument (-r{2012-06-12 23:00:00 +})? Thanks in advance Best Regards Am 06. Jun 2012 um 23:31 schrieb Richard Wackerbarth rich...@nfsnet.org: NoRulez, A better question is Why was revision 8 not included in the nightly run? Using one source tree for both

Re: [CMake] Strange behavior with Nightly builds

2012-06-06 Thread Richard Wackerbarth
NoRulez, A better question is Why was revision 8 not included in the nightly run? Using one source tree for both continuous and nightly assumes that there will be no continuous runs between the last update incorporated in the nightly run and the time at which the nightly run is performed. It

Re: [CMake] cmake self build with ninja works on Darwin, but a view tests fail

2012-05-27 Thread Richard Wackerbarth
Claus, Can you try to set this up to submit to the dashboard? Since you think that many of the problems are not related to Ninja, please also try it without using ninja, but rather Unix makefiles and everything else the same. It will be interesting to see what fails under those conditions.

Re: [CMake] Why is Ninja generator disabled by default?

2012-05-22 Thread Richard Wackerbarth
One of the differences that shows up in the dashboard is that there is a compile test which passes with normal Unix file paths, but fails when there is a space in one of the directory names. Perhaps we need to add an explicit test for everyone, ninja or otherwise, to test that compiles work

Re: [CMake] Why is Ninja generator disabled by default?

2012-05-22 Thread Richard Wackerbarth
Yes, you changed the test configuration and that configuration will work. However, for other generators, you do not need to add the -DMAKE_SUPPORTS_SPACES Richard On May 22, 2012, at 5:18 PM, Claus Klein claus.kl...@arcormail.de wrote: claus-kleins-macbook-pro:CompileCommandOutput clausklein$

Re: [cmake-developers] ninja bug

2012-04-18 Thread Richard Wackerbarth
Let me know if someone needs information from the run which has not been posted to the dashboard. I can bring the machine online and retrieve things. Richard On Apr 18, 2012, at 11:04 AM, Bill Hoffman wrote: Any of the ninja folks have an idea why this test fails on FreeBSD:

Re: [cmake-developers] ninja status

2012-04-08 Thread Richard Wackerbarth
FYI: Intentionally, Chameleon-00.NFSNet forces the building of CMake to allow, and subsequently use, Ninja. It does so by placing the following line in the configuration set(dashboard_cache CMAKE_ENABLE_NINJA:BOOL=TRUE) As you can see from the recent dashboards, enabling this option does not

Re: [cmake-developers] ninja broken on windows?

2012-02-16 Thread Richard Wackerbarth
What are we trying to accomplish here? I have set up 3 of my machines (1 each MacOSX, FreeBSD, and Linux --- like my housekeeper, I don't do Windows) to submit nightly builds using the Ninja generator. That will test the impact of changes in the generator. But it appears that we may also need

Re: [CMake] [cmake-developers] Ninja help

2012-02-15 Thread Richard Wackerbarth
Last night, David indicated that, after installing Ninja, it should be as simple as running the standard nightly submission for CMake but using Ninja as the CTEST_CMAKE_GENERATOR. I am trying to do that right now, but I am running into a bootstrap issue. I think that I have to first convert my

Re: [cmake-developers] Git fun

2011-12-05 Thread Richard Wackerbarth
James, You have not defined stage as the nickname for the remote repository. If you set it up with `git remote add stage g...@cmake.org:stage/cmake.git`, then your push syntax should work. Alternately, `git push g...@cmake.org:stage/cmake.git CUDAv3.2PathChanges` would push using the full

Re: [cmake-developers] Keeping unit tests useful and splitting feature support from platform support

2011-10-16 Thread Richard Wackerbarth
On Oct 16, 2011, at 6:21 PM, Stephen Kelly wrote: On 10/16/2011 02:56 PM, Richard Wackerbarth wrote: On Oct 16, 2011, at 6:54 AM, Stephen Kelly wrote: Having so many old platforms and compilers on the dashboard going red with failure So, I think I'm talking about two separate issues. One

Re: [CMake] CMake 2.8, Xcode generator and XIB files

2011-10-03 Thread Richard Wackerbarth
I don't think that you want the SOURCE file in the bundle. First, you need to process the source file with configure_file(): Use ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist as input and ${CMAKE_CURRENT_BINARY_DIR}/Info.plist as output. Then you incorporate the configured version into the bundle:

Re: [CMake] CMake 2.8, Xcode generator and XIB files

2011-10-03 Thread Richard Wackerbarth
My apology ... I haven't kept up with the non-explicit implications of the Mac-specific properties. On Oct 3, 2011, at 9:34 AM, David Cole wrote: On Mon, Oct 3, 2011 at 10:14 AM, Richard Wackerbarth rich...@nfsnet.org wrote: I don't think that you want the SOURCE file in the bundle

Re: [CMake] Run/build custom command/target only when input files change

2011-03-08 Thread Richard Wackerbarth
On Mar 8, 2011, at 5:10 AM, mika.raj...@patria.fi wrote: foreach(in_file ${ARGN}) ADD_CUSTOM_COMMAND( OUTPUT ${IDL_OUTPUT_DIR}/${out_file}.h ${IDL_OUTPUT_DIR}/${out_file}.tlb DEPENDS ${in_file} COMMAND(${MIDL_EXECUTABLE} ${in_file}

Re: [CMake] problem with mac linker flags

2010-12-22 Thread Richard Wackerbarth
The problem is that CMake does not call the linker. It invokes the linker by calling the compiler and passing flags through it. In the module, Darwin.cmake, you find: SET(CMAKE_C_LINK_FLAGS -Wl,-headerpad_max_install_names) SET(CMAKE_CXX_LINK_FLAGS -Wl,-headerpad_max_install_names) But in

Re: [CMake] problem with mac linker flags

2010-12-22 Thread Richard Wackerbarth
On Dec 22, 2010, at 3:24 PM, Bill Hoffman wrote: So, Darwin-icc.cmake is for the Intel compiler on the Mac. The intel compiler does not want and can not have the -Wl, syntax. These modules need to be updated to the new way of handling compilers. If you will point me toward an example of

Re: [CMake] problem with mac linker flags

2010-12-22 Thread Richard Wackerbarth
I track next very closely. I looks as if Brad added the -Wl, to both Darwin-GNU and to Darwin-icc. If Bill Hoffman is correct and The intel compiler does not want and can not have the -Wl, syntax., then there is a problem with one of Brad's two edits. However, Bill Cochran should try next (or

Re: [CMake] problem with mac linker flags

2010-12-22 Thread Richard Wackerbarth
to be pushed into the middle-ware. Richard On Dec 22, 2010, at 5:14 PM, Bill Hoffman wrote: On 12/22/2010 6:08 PM, Richard Wackerbarth wrote: I track next very closely. I looks as if Brad added the -Wl, to both Darwin-GNU and to Darwin-icc. If Bill Hoffman is correct and The intel compiler

[CMake] A comment on bug resolution

2010-12-15 Thread Richard Wackerbarth
The following is excerpted from a message that I received this morning. I think that it indicates a direction in the CMake philosophy which concerns me. (See below) On Dec 15, 2010, at 6:34 AM, Mantis Bug Tracker wrote: The following issue has been RESOLVED.

Re: [CMake] A comment on bug resolution

2010-12-15 Thread Richard Wackerbarth
On Dec 15, 2010, at 8:34 AM, David Cole wrote: Having said all that, let me address your specific concern regarding the issue closed: I don't question your motive in closing the issue. I agree that the underlying reason for the request is a valid thing to want, but the request expresses it

Re: [CMake] cmake my_BouncyBall

2010-11-07 Thread Richard Wackerbarth
First let me suggest that you word your request in a more complete manner. What does not work? What were you expecting and what did you get? It is difficult, if not impossible, for us to guess. I suspect that the problem is related to the (specifying the output file in Unix). Are you on a Un*x

Re: [CMake] Questions about the cmake 2.8.3-rc1 release

2010-09-15 Thread Richard Wackerbarth
Bill, Some observations on Dashboard Builds: As you know, I run a number of FreeBSD builds on the Nightly branch. I had not been running 2.8 builds, etc. because it was unclear if my builds would be of any real value, but only consume my CPU time and increase my electric bill without providing

Re: [CMake] Questions about the cmake 2.8.3-rc1 release

2010-09-15 Thread Richard Wackerbarth
sees only the topics that have been merged into it, It cannot reach any of the merges into next, so master should remain quite stable. I hope this helps. Regards Andrew On Thu, Sep 16, 2010 at 9:26 AM, Richard Wackerbarth rich...@nfsnet.org wrote: Bill, Some observations

Re: [CMake] No Native 64-Bit CMake Binaries?

2010-05-06 Thread Richard Wackerbarth
Bill, As for the need of 64-bit binaries, I agree that it is not a performance issue. However, it will be a compatibility issue. Things evolve. Remember MacOSX 10.0, 10.1? Back then, you could have argued that we didn't need a new version of CMake. The binaries from MacOS 9 ran just fine. Now,

Re: [CMake] No Native 64-Bit CMake Binaries?

2010-05-06 Thread Richard Wackerbarth
version should build it from source. I'm sure that the OS distributors that provide CMake all do that already. They don't rely on YOUR binaries when the source is available. Richard On May 6, 2010, at 8:18 AM, Bill Hoffman wrote: On 5/6/2010 9:13 AM, Richard Wackerbarth wrote: Bill

Re: [CMake] No Native 64-Bit CMake Binaries?

2010-05-06 Thread Richard Wackerbarth
See RogueResearch6 and Chameleon00.NFSNet. Both of these machines are reporting errors for some time. Richard On May 6, 2010, at 9:12 AM, Sean McBride wrote: On Thu, 6 May 2010 08:36:41 -0500, Richard Wackerbarth said: Yes, it works for now. However, the 64-bit version for MacOSX 10.6

Re: [CMake] No Native 64-Bit CMake Binaries?

2010-05-06 Thread Richard Wackerbarth
May 2010 11:45:21 -0500, Richard Wackerbarth said: See RogueResearch6 and Chameleon00.NFSNet. Both of these machines are reporting errors for some time. The failing 'Architecture' test on Rogue6 fails on _both_ 32 and 64 bit though. ___ Powered

Re: [CMake] Configure Mac OS X for 32-bit

2010-05-02 Thread Richard Wackerbarth
You might try this approach: Since you want to use 32-bit on MacOSX 10.6, when in debug, set the architecture only in your particular case cmake_minimum_required(VERSION 2.4) PROJECT(Test) IF (${CMAKE_SYSTEM_NAME} MATCHES Darwin) Message(${CMAKE_SYSTEM_VERSION}) STRING (REGEX MATCH ^[^.]+

Re: [CMake] CMake has moved to Git!

2010-03-29 Thread Richard Wackerbarth
Thanks, Just what I needed! Richard On Mar 29, 2010, at 12:01 PM, Brad King wrote: I added a dashboard branch to the cmake.org/cmake.git repository. See here for instructions: http://www.cmake.org/Wiki/CMake/Git#Dashboard I suggest committing your local script to your local repo to

Re: [CMake] CMake has moved to Git!

2010-03-26 Thread Richard Wackerbarth
Brad, Now that the setup scripting is more complex, I'm trying to use your cmake_common.cmake script for my CMake submissions. Tracking changes to that script would be much easier for me if you have it published in a publicly readable git repository. Richard On Feb 22, 2010, at 12:50 PM,

Re: [CMake] How to determine CPU features

2010-03-26 Thread Richard Wackerbarth
I was not aware that the export of ANY of the additional information had ever been implemented. ${CMAKE_HOST_HAS_any_feature} was just my suggestion for a possible naming convention. Richard On Mar 26, 2010, at 8:25 PM, Alexander Tarasov wrote: First of all the ${CMAKE_HOST_HAS_any_feature}

Re: [CMake] How to determine CPU features

2010-03-26 Thread Richard Wackerbarth
This suggestion addresses the potential that the TARGET environment might be able to utilize the feature. Just because I can compile code for a hypothetical target machine, there is no guarantee that the actual target machine will have the necessary features. I recognize that most compilations

Re: [CMake] Policy Scope Question

2009-12-31 Thread Richard Wackerbarth
is for project developers. Use -Wno-dev to suppress it. Checking Project CMake/2_9. On Dec 31, 2009, at 6:57 AM, Alexander Neundorf wrote: On Tuesday 29 December 2009, Richard Wackerbarth wrote: I have a question about policy CMP0011. I have: $ cat Call_process_dashboard.cmake # Call

Re: [CMake] compiling single source with different flags

2009-12-29 Thread Richard Wackerbarth
Not as a real solution, but more as a workaround, you could create a derived source file which is just a copy of the source file and then you would have two separate files to be compiled with the appropriate flags. On Dec 29, 2009, at 2:22 PM, Bart wrote: Hi, I'm trying to find a way to

[CMake] Policy Scope Question

2009-12-29 Thread Richard Wackerbarth
I have a question about policy CMP0011. I have: $ cat Call_process_dashboard.cmake # Call process_dashboard # These files are maintained by Richard Wackerbarth set(maintainer_email_account Richard) set(maintainer_email_domain NFSNet.org) IF(COMMAND CMAKE_POLICY) CMAKE_POLICY(SET CMP0011 NEW

[CMake] Possible CDash configuration problem

2009-11-13 Thread Richard Wackerbarth
Shortly after the Nightly epoch, I start running a number of automated submissions to the CMake, and other, dashboards. On the first machine, from what I can see (below), everything ran as expected and was submitted to the dashboard. However, these results are not on display this morning. All of

Re: [CMake] NMake Generation Error: machine type 'X86' conflicts with target machine type 'x64'

2009-11-13 Thread Richard Wackerbarth
Aaron, Perhaps I have it wrong, but I think that the problem is that you are using CMakeCache.txt that was created on a different machine. CMakeCache.txt acts as a configuration file that overrides the registry, environmental variables, and everything else that has a default value. This allows

Re: [CMake] CTest: another sub-directory issue / coverage test

2009-11-10 Thread Richard Wackerbarth
Johannes, Is there any compelling reason to place the cmake control files in a directory under the root? Foo/ CMakeLists.txt CTestConfig.cmake include Foo.h src Foo.cpp FooTest.cpp is a more conventional structure On Nov 10, 2009, at 2:43 AM, Johannes

Re: [CMake] Invitation to connect on LinkedIn

2009-07-07 Thread Richard Wackerbarth
Yes, a noise suppressor for the mailing list. On Jul 7, 2009, at 4:10 PM, Tyler Roscoe wrote: On Tue, Jul 07, 2009 at 04:52:18PM -0400, Bill Hoffman wrote: Hmmm ... so LinkedIn is a Kitware project now? Yea, CLinkedIn :) I smell a feature request brewing... tyler

Re: [CMake] How to determine the current target?

2009-04-09 Thread Richard Wackerbarth
Jeremy, I think that the problem is that CMake was never oriented toward the situation that you, and many others, have where it is very expensive to have the code under development as a part of a much larger project. When you get to a relatively stable situation, you will appreciate the

[CMake] How To Question

2008-05-13 Thread Richard Wackerbarth
I'm still trying to figure out how to handle the following two situations (simplified): When we run the tests for our Nightly Dashboard, in addition to a number of other tests, consider Test A and Test B. If Test A fails, then I don't even want to attempt to run Test B. The program is

Re: [CMake] How To Question

2008-05-13 Thread Richard Wackerbarth
on the dashboard that Test A passed (with its accompanying metrics) and that Test B failed. Any attempt to have the combined test reported as one entry will suppress valuable information. Richard On May 13, 2008, at 3:12 PM, John Doe wrote: On Tue, May 13, 2008 at 3:00 PM, Richard Wackerbarth [EMAIL

[CMake] Throwing in the towel

2008-01-05 Thread Richard Wackerbarth
OK, I give up! I'm sure that there is a right way to do it that will be obvious, and easy to use, but I haven't found it. I am able to do a respectable job of building across many platforms, and getting the results posted to a Dart(2) dashboard. But, I have two problems that I feel are

[CMake] Dashboards

2007-06-04 Thread Richard Wackerbarth
I have been unable to contact any of the Dart2 dashboards hosted at Harvard. Since I have been using Dart2 for my project, I would like to support efforts that would encourage the replacement of Dart1 installations, and thus shift development emphasis. Have they been discontinued? Or is

[CMake] Hints Requested

2007-05-18 Thread Richard Wackerbarth
Hi. I've been using CMake and Dart2 to do simple builds for some time. It's great! However, I have a few things that are hacks rather than something that looks nice. I'd like to clean it up. I would appreciate it if anyone can point me to examples where someone has addressed a similar

Re: [CMake] EXECUTE_PROCESS problem

2007-05-15 Thread Richard Wackerbarth
I'm not sure, but I think that, in the UNIX case, your executable is not sha1, but rather it is looking for the filename sha1 -r. Try IF(UNIX) SET(CHKSUM_EXECUTABLE /sbin/sha1) SET(CHKSUM_PARAMETERS -r) ELSE(UNIX) SET(CHKSUM_EXECUTABLE /usr/bin/sha1sum) SET(CHKSUM_PARAMETERS

Re: [CMake] Nightly ctest : Neither CVS, nor SVN

2007-05-14 Thread Richard Wackerbarth
On May 14, 2007, at 3:19 AM, Mathieu Malaterre wrote: Hello, We have a project here, handled without CVS or SVN. I would like to get rid of the annoying (which is displayed on the Dart2 Update page): * Update repository: cvs update: No CVSROOT specified! Please use the `-d' option cvs