[cmake-developers] Upcoming What's New in CMake 2.8.7 webinar
The CMake team is hard at work on the 2.8.7 release - we announcedhttp://www.kitware.com/blog/home/post/208 CMake 2.8.7 rc1 on December 8th, and we expect to release the final version by the end of the year. Want to learn more? Then please join us on January 4th from 12:00-12:20 p.m. EST, when I will be presenting a free webinar highlighting what’s new in the CMake 2.8.7 release and giving a preview of what’s in the pipeline. You'll also get a chance to ask the CMake team any questions you may have on this release in particular or CMake in general. You can register for this event through GoToWebinarhttps://www3.gotomeeting.com/register/152723134 . https://www3.gotomeeting.com/register/152723134 Please note that you'll need to attend this webinar from a Windows or Mac computer - GoToWebinar does not yet support Linux. If you can't attend, we'll have the recorded session available within a few days after the webinar at www.cmake.org (under Resources - Webinars). See you online, 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0012637]: RSS feed for CMake news does not validate - contains special characters
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12637 == Reported By:Ryan Pavlik Assigned To: == Project:CMake Issue ID: 12637 Category: Documentation Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2011-12-21 15:37 EST Last Modified: 2011-12-21 15:37 EST == Summary:RSS feed for CMake news does not validate - contains special characters Description: I can't add this feed to Liferea because it does not validate, and it even confuses Chrome. Here's the validation link: http://feedvalidator.org/check.cgi?url=http://www.kitware.com/news/rss/CMake.xml == Issue History Date ModifiedUsername FieldChange == 2011-12-21 15:37 Ryan PavlikNew Issue == -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] [CMake 0012636]: FindwxWidgets.cmake library list is not up-to-date for wxWidgets 2.9.3: doesn't include webview
Mantis Bug Tracker wrote: The following CMake command fails, although it should be valid under wxWidgets 2.9.3: FIND_PACKAGE(wxWidgets COMPONENTS core base html webview REQUIRED) If you update the wx-module, you should consider including a version check, or at least a var that contains the version. -- MfG usw. Werner Mahr -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] CMake 2.8.7-rc2 ready for testing!
The CMake 2.8.7 release candidate stream continues! You can find the source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D This will become the final build of CMake 2.8.7 next Wednesday unless somebody finds and reports a showstopping (crasher, serious behavioral regression) issue between now and then. This email is also available as a blog post: http://www.kitware.com/blog/home/post/216 Some of the notable changes in this release are: - improved Eclipse support - incremental improvements to the AUTOMOC feature added in the previous release - more cryptographic hash implementations (SHA1, SHA224, SHA256, SHA384, SHA512) - file(...) and string(...) command additions for computing hash values - added LINK_PUBLIC and LINK_PRIVATE options to target_link_libraries command - and, as always, various minor bug fixes Similar to the previous release, we do not have pre-built binaries for the SunOS anymore. However, now we have two sets of installers for the Mac. The Darwin versions are for Mac OSX 10.4 and later, and are ppc;i386 universal binaries. The Darwin64 versions are for 10.6 and later, and are x86_64;i386 universal binaries. Following is the list of changes in this rc since the previous one. Please try this version of CMake on your projects and report any issues to the list or the bug tracker. Happy building! -Dave Changes in CMake 2.8.7-rc2 (since 2.8.7-rc1) Alex Neundorf (5): automoc: default to strict mode, use CMAKE_AUTOMOC_RELAXED_MODE automoc: improved warning message in relaxed mode Remove trailing whitespace Add comment about one more problem of the C depency scanner. fix #12262: dependency scanning for ASM files Bill Hoffman (1): Fix the case where cmake --build failed with two project cmds in one file. Brad King (11): KWSys: Correctly handle empty environment variables FortranCInterface: Work around mingw32-make trouble with parens Xcode: Create separate rerun dependencies for subprojects (#12616) Fix Intel Fortran .vfproj files for VS 10 HP: Drive shared library linking with compiler front end Follow all dependencies of shared library private dependencies Do not link private dependent shared libraries on OS X 10.4 Avoid clobbering variable 'OUTPUT' in compiler tests (#12628) Fix and simplify Fortran test compiler compatibility check CTest: Recognize Intel errors without space before colon (#12627) Windows-GNU: Remove extra quotes in GNUtoMS rule variable David Cole (4): Release: Increase timeout for slow-testing cygwin build Modules: Use windres as rc compiler base name for cross-compiles (#12480) Tests: Only really run MFC test if we can build MFC apps (#11213) FindBoost: Quote possibly empty string argument (#12273) Eric NOULARD (1): CPackRPM fix #0012608 and unoticed related bug Johan Fänge (1): CMake: Fix progress reporting for custom targets (#12441) Mike McQuaid (2): Unset configurations variable when no build type. Improve component support and output indentation. Raphael Kubo da Costa (2): Remove the apparently outdated README in Source/QtDialog. QtDialog: Set Ctrl+Q as the shortcut for quitting the program. Tim Gallagher (2): FindLAPACK: Correct CMAKE_FIND_LIBRARY_SUFFIXES spelling (#12624) FindLAPACK: List thread libs to avoid link errors (#12625) Valat Sébastien (1): CTest: Do not get CDash version without drop site (#12618) -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [CMake] Documentation request
I had the same problem a yesterday (or the day before) with the string( FIND ) command... I tried to find the cmake 2.8.4 docs but I couldn't. I think you should do it, or at least to issue a warning (in the documentation) in every command that wasn't introduced in CMake 2.8.0... Yes, the Python way to do this is more organized. Renato 2011/12/21 Rolf Eike Beer e...@sf-mail.de: Am Mittwoch 21 Dezember 2011, 06:14:03 schrieb Michael Wild: OTOH, I think it would be very useful to mention the first version a feature was introduced in the docs directly, similarly to what Python does (see e.g. http://docs.python.org/library/string.html#string-formatting). We already discussed this a while ago (like a year or so) and AFAIR the outcome was to do this for every newly added feature. Seems like nobody did it. Eike -- 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] Documentation request
2011/12/21 Renato Utsch renatout...@gmail.com: I had the same problem a yesterday (or the day before) with the string( FIND ) command... I tried to find the cmake 2.8.4 docs but I couldn't. cmake command **itself** is able to spit out its documentation. So cmake --help-command string will give you the hopefully up to date doc of the currently used cmake. In the same way: cmake --help-full cmake --help-html will give you a doc similar to http://www.cmake.org/cmake/help/cmake-2-8-docs.html but for the currently used cmake. I think you should do it, or at least to issue a warning (in the documentation) in every command that wasn't introduced in CMake 2.8.0... You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. -- 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
Re: [CMake] Documentation request
You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. Sorry, I am not that good with english, I meant as the CMake team with 'you'. But the 'CMake team' could do that with new releases, like, writing this warning with additions in the newer releases. Or, the easier way, to mantain different versions of the documentation at the site. This is not difficult, maybe put the latest doc in the Documentation page and down in the see also of the documentation a link to the older ones, or maybe everything in the documentation page... Renato 2011/12/21 Eric Noulard eric.noul...@gmail.com: 2011/12/21 Renato Utsch renatout...@gmail.com: I had the same problem a yesterday (or the day before) with the string( FIND ) command... I tried to find the cmake 2.8.4 docs but I couldn't. cmake command **itself** is able to spit out its documentation. So cmake --help-command string will give you the hopefully up to date doc of the currently used cmake. In the same way: cmake --help-full cmake --help-html will give you a doc similar to http://www.cmake.org/cmake/help/cmake-2-8-docs.html but for the currently used cmake. I think you should do it, or at least to issue a warning (in the documentation) in every command that wasn't introduced in CMake 2.8.0... You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. -- 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
Re: [CMake] Support for RVDS 4.1: ARM C/C++ and ASM compilers.
Hi Alexander, Just wanted to let you know that, thanks to your assistance, we did some more work on this. Please refer to the issue: http://public.kitware.com/Bug/view.php?id=12614 It would be nice if this work could be integrated in next release of CMake. Cheers, Abdel. -Original Message- From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net] Sent: Thursday, December 08, 2011 9:24 PM To: cmake@cmake.org Cc: Abdelrazak Younes Subject: Re: [CMake] Support for RVDS 4.1: ARM C/C++ and ASM compilers. On Thursday 08 December 2011, Abdelrazak Younes wrote: Hello, We (MARVELL Switzerland) have created some CMake support files in order to use RVDS 4.1 ARM C/C++ and ASM compilers. Cool ! I mean, this is really cool ! :-) Can you please create a ticket for this on http://public.kitware.com/Bug/my_view_page.php , basically with the content of this email ? This way it is ensured that it won't get lost or forgotten. Some comments: Setting all the CMAKE_(C|CXX)_CREATE_* and ARCHIVE variables in the toolchain file should not be necessary. It should be enough to only set CMAKE_C_COMPILER and CMAKE_CXX_COMPILER. Then cmake tries to compile a small executable with it, and tries to detect the compiler, see Modules/CMakeCCompilerID.c.in. Probably there is a macro builtin into this compiler to detect that it is the RVDS compiler ? The cmake compiler ID could then be named RVDS. Then cmake executes Modules/CMakeFindBinUtils.cmake. If the compiler ID has been determined successfully, you can change this file so that if the compiler ID is RVDS, it looks for armar instead of ar. Then, once it has detected this compiler id, it can load Modules/Compiler/RVDS-C.cmake and RVDS-CXX.cmake. There you can put also the variables for linking etc. Thanks a lot :-) Alex -- 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] Documentation request
As I already said, all the old documentation (back to version 1.6, AFAIK) is available on the wiki. Michael On 12/21/2011 01:12 PM, Renato Utsch wrote: You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. Sorry, I am not that good with english, I meant as the CMake team with 'you'. But the 'CMake team' could do that with new releases, like, writing this warning with additions in the newer releases. Or, the easier way, to mantain different versions of the documentation at the site. This is not difficult, maybe put the latest doc in the Documentation page and down in the see also of the documentation a link to the older ones, or maybe everything in the documentation page... Renato 2011/12/21 Eric Noulard eric.noul...@gmail.com: 2011/12/21 Renato Utsch renatout...@gmail.com: I had the same problem a yesterday (or the day before) with the string( FIND ) command... I tried to find the cmake 2.8.4 docs but I couldn't. cmake command **itself** is able to spit out its documentation. So cmake --help-command string will give you the hopefully up to date doc of the currently used cmake. In the same way: cmake --help-full cmake --help-html will give you a doc similar to http://www.cmake.org/cmake/help/cmake-2-8-docs.html but for the currently used cmake. I think you should do it, or at least to issue a warning (in the documentation) in every command that wasn't introduced in CMake 2.8.0... You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. -- 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] Documentation request
Yes, but is not so easy to find. It would be easier to have it in the documentation page (if the page hosts CMake 2.6 or CMake 2.4 documentations, why it doesn't host CMake 2.8.3 documentation? They should be on the wiki too!), easier to find. Renato 2011/12/21 Michael Wild them...@gmail.com: As I already said, all the old documentation (back to version 1.6, AFAIK) is available on the wiki. Michael On 12/21/2011 01:12 PM, Renato Utsch wrote: You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. Sorry, I am not that good with english, I meant as the CMake team with 'you'. But the 'CMake team' could do that with new releases, like, writing this warning with additions in the newer releases. Or, the easier way, to mantain different versions of the documentation at the site. This is not difficult, maybe put the latest doc in the Documentation page and down in the see also of the documentation a link to the older ones, or maybe everything in the documentation page... Renato 2011/12/21 Eric Noulard eric.noul...@gmail.com: 2011/12/21 Renato Utsch renatout...@gmail.com: I had the same problem a yesterday (or the day before) with the string( FIND ) command... I tried to find the cmake 2.8.4 docs but I couldn't. cmake command **itself** is able to spit out its documentation. So cmake --help-command string will give you the hopefully up to date doc of the currently used cmake. In the same way: cmake --help-full cmake --help-html will give you a doc similar to http://www.cmake.org/cmake/help/cmake-2-8-docs.html but for the currently used cmake. I think you should do it, or at least to issue a warning (in the documentation) in every command that wasn't introduced in CMake 2.8.0... You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. -- 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 -- 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] Fwd: Fwd: cpack DragNDrop on OSX 10.7
Dear Clinton and David,
Thanks for your replies. I did notice the COMPONENT discrepancy on my
other project, but I figured out now that I had misunderstood the
first time (or at least I think so). What I wrote then was something
along the lines of (which didn't work):
INSTALL(TARGETS ${mtargets}
BUNDLE DESTINATION .
RUNTIME DESTINATION bin
LIBRARY DESTINATION lib
ARCHIVE DESTINATION lib
COMPONENT Runtime
)
What I just now realized worked was to do instead
INSTALL(TARGETS ${mtargets}
BUNDLE DESTINATION . COMPONENT Runtime
RUNTIME DESTINATION bin COMPONENT Runtime
LIBRARY DESTINATION lib COMPONENT Libraries
ARCHIVE DESTINATION lib COMPONENT Libraries
)
In other words, for every type of target, set the component. This now
works very well for the Mad-X project. I had also done some other
unnecessary complications with the COMPONENT stuff on the other
project, which cluttered things and hid my real problems I think.
What libs does your bundle app depend on? Are they
built into the app with full path names such that an tool -L analysis
will work without any DIRS value?
Currently only X11, sometimes libgfortran (I think it depends on which
gfortran version you are using?). At least for this project, otool -L
solves it all. For my other project which I don't have in a public
place at the moment it looks like I have a bit more problems now (it
worked as well with my previous install). You might have given me a
good hint right there.
To both of you, thank you very much for your time and help!
Best Regards, and a Merry Christmas to everyone on the list,
Yngve
On 21 December 2011 00:33, David Cole david.c...@kitware.com wrote:
Good catch, Clinton. I did not notice the COMPONENT discrepancy.
On Tue, Dec 20, 2011 at 6:26 PM, Clinton Stimpson clin...@elemtech.com
wrote:
This doesn't look right:
INSTALL(TARGETS ${mtargets}
BUNDLE DESTINATION .
RUNTIME DESTINATION bin
LIBRARY DESTINATION lib
ARCHIVE DESTINATION lib
)
INSTALL(CODE
include(BundleUtilities)
fixup_bundle(\${APPS}\ \\ \${DIRS}\)
COMPONENT Runtime)
The target and fixup of the target are in different components, so that can
cause problems at cpack time depending on your generator.
Clint
On Tuesday, December 20, 2011 04:13:35 pm David Cole wrote:
You're doing this:
set(APPS \${CMAKE_INSTALL_PREFIX}/madx${BINARY_POSTFIX}.app) #
paths to executables
set(DIRS )
Then this:
INSTALL(CODE
include(BundleUtilities)
fixup_bundle(\${APPS}\ \\ \${DIRS}\)
COMPONENT Runtime)
Which means that your install code (in cmake_install.cmake) will have
something like this in it:
include(BundleUtilities)
fixup_bundle(${CMAKE_INSTALL_PREFIX}/madxXXX.app )
CMAKE_INSTALL_PREFIX should evaluate to a directory underneath the
_CPack_Packages directory, so that should be ok. But your DIRS
variable is empty. What libs does your bundle app depend on? Are they
built into the app with full path names such that an tool -L analysis
will work without any DIRS value?
Did you run something like cpack -G DragNDrop --verbose to see the
full output of the make install step, and did it seem like
fixup_bundle yielded any output in the --verbose stream...?
Your code looks right, but maybe you need some DIRS for the fixup to
work correctly...
HTH,
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
[CMake] CMake add_subdirectory and recompiling
I've recently been surprised by the behavior of CMake when modifying CMakeLists.txt files pointed to by add_subdirectory() directives. I've asked the question on StackOverflow[1] and have gotten no clean answer. If anyone is interested, there is a small bounty (50 points) on the question expiring in a few hours. The question is tad bit lengthy, so I won't duplicate here. Any reply on either the mailing list or to the linked StackOverflow question is appreciated. Thanks! André [1]: http://stackoverflow.com/questions/8479929/cmake-add-subdirectory-and-recompiling -- 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
[CMake] Target to build only unit tests?
Is there a target generated by CMake to build ONLY unit tests? I'm using Visual Studio 2008. If not, is there a way I can make one? - Robert Dailey -- 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] Documentation request
I like the idea of putting new in #.#.# when features are added, that would at least be an easy reminder on the documentation page that some things are not universal to 2.8.*. I also agree that it's not super clear that back documentation is available on the wiki. If you look at the documentation page, it says things like Documentation for CMake 2.8, Documentation for CMake 2.6 and then at the bottom under Legacy Documentation for CMake there is a section for CMake 2.4. To me that implies that A) documentation holds for all versions of 2.8.* or 2.6.* or 2.4.*; B) there is only documentation for those versions and the wiki would hold other types of information (and if you just go to the main page of the wiki, there is no indication that old versions are documented, I had to search to find it). So, I understand all to well how time consuming writing documentation is. And if space is an issue, how about the following: A) Rename the links on the documentation page so that it says it is for the current version, so it would say Documentation for CMake 2.8.7 when the next is released. B) Under Legacy Documentation, put a link to the CMake_Released_Versions page on the wiki to point people to that documentation. Does that sounds like a reasonable compromise? We've run into this frequently enough that I thought I'd bring it up, but as I said before, if we're the only ones who keep making these mistakes, then we can deal with it internally. Tim - Original Message - From: Renato Utsch renatout...@gmail.com To: cmake@cmake.org Sent: Wednesday, December 21, 2011 8:38:27 AM Subject: Re: [CMake] Documentation request Yes, but is not so easy to find. It would be easier to have it in the documentation page (if the page hosts CMake 2.6 or CMake 2.4 documentations, why it doesn't host CMake 2.8.3 documentation? They should be on the wiki too!), easier to find. Renato 2011/12/21 Michael Wild them...@gmail.com: As I already said, all the old documentation (back to version 1.6, AFAIK) is available on the wiki. Michael On 12/21/2011 01:12 PM, Renato Utsch wrote: You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. Sorry, I am not that good with english, I meant as the CMake team with 'you'. But the 'CMake team' could do that with new releases, like, writing this warning with additions in the newer releases. Or, the easier way, to mantain different versions of the documentation at the site. This is not difficult, maybe put the latest doc in the Documentation page and down in the see also of the documentation a link to the older ones, or maybe everything in the documentation page... Renato 2011/12/21 Eric Noulard eric.noul...@gmail.com: 2011/12/21 Renato Utsch renatout...@gmail.com: I had the same problem a yesterday (or the day before) with the string( FIND ) command... I tried to find the cmake 2.8.4 docs but I couldn't. cmake command **itself** is able to spit out its documentation. So cmake --help-command string will give you the hopefully up to date doc of the currently used cmake. In the same way: cmake --help-full cmake --help-html will give you a doc similar to http://www.cmake.org/cmake/help/cmake-2-8-docs.html but for the currently used cmake. I think you should do it, or at least to issue a warning (in the documentation) in every command that wasn't introduced in CMake 2.8.0... You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. -- 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 -- 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] CMake add_subdirectory and recompiling
Here's my initial shot at it: http://stackoverflow.com/questions/8479929/cmake-add-subdirectory-and-recompiling/8593372#8593372 On Wed, Dec 21, 2011 at 11:25 AM, André Caron andre.l.ca...@gmail.com wrote: I've recently been surprised by the behavior of CMake when modifying CMakeLists.txt files pointed to by add_subdirectory() directives. I've asked the question on StackOverflow[1] and have gotten no clean answer. If anyone is interested, there is a small bounty (50 points) on the question expiring in a few hours. The question is tad bit lengthy, so I won't duplicate here. Any reply on either the mailing list or to the linked StackOverflow question is appreciated. Thanks! André [1]: http://stackoverflow.com/questions/8479929/cmake-add-subdirectory-and-recompiling -- 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] Target to build only unit tests?
On Wed, Dec 21, 2011 at 11:29 AM, Robert Dailey rcdai...@gmail.com wrote: Is there a target generated by CMake to build ONLY unit tests? I'm using Visual Studio 2008. No, there is not. If not, is there a way I can make one? Yes, of course. You can do anything you want with a combination of add_custom_command and add_custom_target. David - Robert Dailey -- 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] Target to build only unit tests?
On Wed, Dec 21, 2011 at 11:52 AM, David Cole david.c...@kitware.com wrote: On Wed, Dec 21, 2011 at 11:29 AM, Robert Dailey rcdai...@gmail.com wrote: Is there a target generated by CMake to build ONLY unit tests? I'm using Visual Studio 2008. No, there is not. If not, is there a way I can make one? Yes, of course. You can do anything you want with a combination of add_custom_command and add_custom_target. The easiest thing is simply: add_custom_target(unit_tests DEPENDS unit_test_target_1 unit_test_target_2) Then when you build the do-nothing unit_tests target, all of its DEPENDS targets will be built first. David - Robert Dailey -- 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] CMake add_subdirectory and recompiling
On 12/21/2011 05:25 PM, André Caron wrote: I've recently been surprised by the behavior of CMake when modifying CMakeLists.txt files pointed to by add_subdirectory() directives. I've asked the question on StackOverflow[1] and have gotten no clean answer. If anyone is interested, there is a small bounty (50 points) on the question expiring in a few hours. The question is tad bit lengthy, so I won't duplicate here. Any reply on either the mailing list or to the linked StackOverflow question is appreciated. Thanks! André [1]: http://stackoverflow.com/questions/8479929/cmake-add-subdirectory-and-recompiling Get rid of the file(GLOB ...). Never, ever use it unless you know exactly what you're doing. Using it usually breaks something. Also, you didn't say *what* changes you made that caused a full rebuild. If you change anything that will show up on the command line (e.g. change add_definitions(), include_directories(), etc.), this will of course cause a rebuild. 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
Re: [CMake] CMake add_subdirectory and recompiling
On Wed, Dec 21, 2011 at 11:56 AM, Michael Wild them...@gmail.com wrote: On 12/21/2011 05:25 PM, André Caron wrote: I've recently been surprised by the behavior of CMake when modifying CMakeLists.txt files pointed to by add_subdirectory() directives. I've asked the question on StackOverflow[1] and have gotten no clean answer. If anyone is interested, there is a small bounty (50 points) on the question expiring in a few hours. The question is tad bit lengthy, so I won't duplicate here. Any reply on either the mailing list or to the linked StackOverflow question is appreciated. Thanks! André [1]: http://stackoverflow.com/questions/8479929/cmake-add-subdirectory-and-recompiling Get rid of the file(GLOB ...). Never, ever use it unless you know exactly what you're doing. Using it usually breaks something. Also, you didn't say *what* changes you made that caused a full rebuild. If you change anything that will show up on the command line (e.g. change add_definitions(), include_directories(), etc.), this will of course cause a rebuild. 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 I agree with the advice to get rid of file(GLOB, but I also think it's irrelevant to the problem here. Using it should have no bearing on what rebuilds when CMake re-runs, assuming that the set of globbed files is the same from run to run. -- 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] CMake add_subdirectory and recompiling
On 12/21/2011 05:59 PM, David Cole wrote: On Wed, Dec 21, 2011 at 11:56 AM, Michael Wild them...@gmail.com wrote: On 12/21/2011 05:25 PM, André Caron wrote: I've recently been surprised by the behavior of CMake when modifying CMakeLists.txt files pointed to by add_subdirectory() directives. I've asked the question on StackOverflow[1] and have gotten no clean answer. If anyone is interested, there is a small bounty (50 points) on the question expiring in a few hours. The question is tad bit lengthy, so I won't duplicate here. Any reply on either the mailing list or to the linked StackOverflow question is appreciated. Thanks! André [1]: http://stackoverflow.com/questions/8479929/cmake-add-subdirectory-and-recompiling Get rid of the file(GLOB ...). Never, ever use it unless you know exactly what you're doing. Using it usually breaks something. Also, you didn't say *what* changes you made that caused a full rebuild. If you change anything that will show up on the command line (e.g. change add_definitions(), include_directories(), etc.), this will of course cause a rebuild. 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 I agree with the advice to get rid of file(GLOB, but I also think it's irrelevant to the problem here. Using it should have no bearing on what rebuilds when CMake re-runs, assuming that the set of globbed files is the same from run to run. That's why I was asking for the specifics of the modifications causing a rebuild. 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
[CMake] Upcoming What's New in CMake 2.8.7 webinar
The CMake team is hard at work on the 2.8.7 release - we announcedhttp://www.kitware.com/blog/home/post/208 CMake 2.8.7 rc1 on December 8th, and we expect to release the final version by the end of the year. Want to learn more? Then please join us on January 4th from 12:00-12:20 p.m. EST, when I will be presenting a free webinar highlighting what’s new in the CMake 2.8.7 release and giving a preview of what’s in the pipeline. You'll also get a chance to ask the CMake team any questions you may have on this release in particular or CMake in general. You can register for this event through GoToWebinarhttps://www3.gotomeeting.com/register/152723134 . https://www3.gotomeeting.com/register/152723134 Please note that you'll need to attend this webinar from a Windows or Mac computer - GoToWebinar does not yet support Linux. If you can't attend, we'll have the recorded session available within a few days after the webinar at www.cmake.org (under Resources - Webinars). See you online, 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
Re: [CMake] CMake add_subdirectory and recompiling
On 12/21/2011 11:56 AM, Michael Wild wrote: [1]: http://stackoverflow.com/questions/8479929/cmake-add-subdirectory-and-recompiling Get rid of the file(GLOB ...). Never, ever use it unless you know exactly what you're doing. Using it usually breaks something. Also, you didn't say *what* changes you made that caused a full rebuild. If you change anything that will show up on the command line (e.g. change add_definitions(), include_directories(), etc.), this will of course cause a rebuild. I made a comment on stackoverflow as well. -Bill -- 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] Documentation request
Yes, exactly, the way it is now is not obvious, but it should be. I indeed thought that CMake 2.8 documentation was for 2.8.*, but I discovered this week that it wasn't. And I'm sure that this happens with A LOT of people. Renato 2011/12/21 Tim Gallagher tim.gallag...@gatech.edu: I like the idea of putting new in #.#.# when features are added, that would at least be an easy reminder on the documentation page that some things are not universal to 2.8.*. I also agree that it's not super clear that back documentation is available on the wiki. If you look at the documentation page, it says things like Documentation for CMake 2.8, Documentation for CMake 2.6 and then at the bottom under Legacy Documentation for CMake there is a section for CMake 2.4. To me that implies that A) documentation holds for all versions of 2.8.* or 2.6.* or 2.4.*; B) there is only documentation for those versions and the wiki would hold other types of information (and if you just go to the main page of the wiki, there is no indication that old versions are documented, I had to search to find it). So, I understand all to well how time consuming writing documentation is. And if space is an issue, how about the following: A) Rename the links on the documentation page so that it says it is for the current version, so it would say Documentation for CMake 2.8.7 when the next is released. B) Under Legacy Documentation, put a link to the CMake_Released_Versions page on the wiki to point people to that documentation. Does that sounds like a reasonable compromise? We've run into this frequently enough that I thought I'd bring it up, but as I said before, if we're the only ones who keep making these mistakes, then we can deal with it internally. Tim - Original Message - From: Renato Utsch renatout...@gmail.com To: cmake@cmake.org Sent: Wednesday, December 21, 2011 8:38:27 AM Subject: Re: [CMake] Documentation request Yes, but is not so easy to find. It would be easier to have it in the documentation page (if the page hosts CMake 2.6 or CMake 2.4 documentations, why it doesn't host CMake 2.8.3 documentation? They should be on the wiki too!), easier to find. Renato 2011/12/21 Michael Wild them...@gmail.com: As I already said, all the old documentation (back to version 1.6, AFAIK) is available on the wiki. Michael On 12/21/2011 01:12 PM, Renato Utsch wrote: You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. Sorry, I am not that good with english, I meant as the CMake team with 'you'. But the 'CMake team' could do that with new releases, like, writing this warning with additions in the newer releases. Or, the easier way, to mantain different versions of the documentation at the site. This is not difficult, maybe put the latest doc in the Documentation page and down in the see also of the documentation a link to the older ones, or maybe everything in the documentation page... Renato 2011/12/21 Eric Noulard eric.noul...@gmail.com: 2011/12/21 Renato Utsch renatout...@gmail.com: I had the same problem a yesterday (or the day before) with the string( FIND ) command... I tried to find the cmake 2.8.4 docs but I couldn't. cmake command **itself** is able to spit out its documentation. So cmake --help-command string will give you the hopefully up to date doc of the currently used cmake. In the same way: cmake --help-full cmake --help-html will give you a doc similar to http://www.cmake.org/cmake/help/cmake-2-8-docs.html but for the currently used cmake. I think you should do it, or at least to issue a warning (in the documentation) in every command that wasn't introduced in CMake 2.8.0... You ? This represents a fair amount of work... I bet that if no-one did it it is because it's a hUGe task. -- 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 -- 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
Re: [CMake] Documentation request
On 21 December 2011 18:10, Renato Utsch renatout...@gmail.com wrote: Yes, exactly, the way it is now is not obvious, but it should be. I indeed thought that CMake 2.8 documentation was for 2.8.*, but I discovered this week that it wasn't. And I'm sure that this happens with A LOT of people. As a matter of fact, it happened to me several times until I've learned the lesson. Manual version vs CMake version http://www.cmake.org/pipermail/cmake/2010-February/035006.html IMHO, the choice is binary: either docs are versioned (see Python) or only docs for most recent release are displayed but titled with full version number X.Y.Z. Best regards -- Mateusz Loskot, http://mateusz.loskot.net -- 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] CMake add_subdirectory and recompiling
Bill, your suggestion lead me to find a problem in the way I was setting the compiler flags. It seems this had nothing to do with the add_subdirectory() command or my project structure. If you're interested in the answer, checkout it out: http://stackoverflow.com/q/8479929/313063 Thanks, André -Original Message- From: Bill Hoffman Sent: Wednesday, December 21, 2011 12:06 PM To: cmake@cmake.org Subject: Re: [CMake] CMake add_subdirectory and recompiling On 12/21/2011 11:56 AM, Michael Wild wrote: [1]: http://stackoverflow.com/questions/8479929/cmake-add-subdirectory-and-recompiling Get rid of the file(GLOB ...). Never, ever use it unless you know exactly what you're doing. Using it usually breaks something. Also, you didn't say *what* changes you made that caused a full rebuild. If you change anything that will show up on the command line (e.g. change add_definitions(), include_directories(), etc.), this will of course cause a rebuild. I made a comment on stackoverflow as well. -Bill -- 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] Target to build only unit tests?
Hi,
On Wed, Dec 21, 2011 at 11:59:13AM -0500, cmake-requ...@cmake.org wrote:
Date: Wed, 21 Dec 2011 11:52:27 -0500
From: David Cole david.c...@kitware.com
Subject: Re: [CMake] Target to build only unit tests?
To: Robert Dailey rcdai...@gmail.com
Cc: CMake ML cmake@cmake.org
Message-ID:
caadwe9xg5mooennxwsx0gylczwqc_7tuyby+8zo0w4tu+-c...@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Dec 21, 2011 at 11:29 AM, Robert Dailey rcdai...@gmail.com wrote:
Is there a target generated by CMake to build ONLY unit tests? I'm using
Visual Studio 2008.
No, there is not.
If not, is there a way I can make one?
Yes, of course. You can do anything you want with a combination of
add_custom_command and add_custom_target.
Something worthwhile might be (whipped up quickly, untested):
# Implement include guard (e.g. reduce cmake --trace clutter)
if(UNIT_TEST_HELPERS_DEFINED)
return()
endif(UNIT_TEST_HELPERS_DEFINED)
set(UNIT_TEST_HELPERS_DEFINED true)
if(NOT TARGET unit_tests_all)
add_custom_target(unit_tests_all ALL)
endif(NOT TARGET unit_tests_all)
# Properly very worthwhile to have a fixed convention for unit test
# targets. Or perhaps use unit_test_? (...too?)
set(unit_test_targets_common_name_prefix ut_)
function(unit_test_register_conditional _target)
if(_target MATCHES ^${unit_test_targets_common_name_prefix})
add_dependencies(unit_tests_all ${_target})
endif(_target MATCHES ^${unit_test_targets_common_name_prefix})
function(unit_test_register_conditional _target)
function(super_power_target_post_handling _target)
unit_test_register_conditional(${_target})
...something_else_that_might_be_useful...()
endfunction(super_power_target_post_handling _target)
Then push that code into a CMake Module file (to be added to
cmake/Modules/ in your source root or some such),
and do
include(ModuleName)
where needed, and call
super_power_target_post_handling(current_target)
for every target where common post-handling might be useful.
But obviously super_power_target_post_handling() shouldn't fetch
your morning cereals - it should still contain functionality
that's specific enough, to not end up with messy imprecise (unknown!) handling
that might change at any time.
And then, in case there's a build shell script, one could implement
poor man's unit test handling by doing something like:
[ ... run build stuff ... ]
pseudo_random=$(date +%s) # UNIX Epoch seconds (don't use %N nanoseconds since
it's not portable, plus it's overkill)
run_tests=$((${pseudo_random} % 42)) # modulo, obviously
if [ ${run_tests} -eq 0 ]; then
echo INFO: running unit tests...
[[[ result of grep CMAKE_BUILD_COMMAND CMakeCache.txt ]]] unit_tests_all
fi
Andreas Mohr
--
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] Target to build only unit tests?
I've managed to workaround this in Visual Studio by using a solution folder
for my unit tests. I can then right-click the solution folder and click
Build, and that will build all my tests.
I actually like the dependency idea, it is simple and straight forward. I
have common code that defines my tests, so I can easily accumulate a list
of those tests and at the end, define a custom target that depends on all
of them.
Would be nice to see CMake have builtin support for this, though. There
could be a BUILD_TESTS CMake predefined target in visual studio.
-
Robert Dailey
On Wed, Dec 21, 2011 at 1:12 PM, Andreas Mohr a...@lisas.de wrote:
Hi,
On Wed, Dec 21, 2011 at 11:59:13AM -0500, cmake-requ...@cmake.org wrote:
Date: Wed, 21 Dec 2011 11:52:27 -0500
From: David Cole david.c...@kitware.com
Subject: Re: [CMake] Target to build only unit tests?
To: Robert Dailey rcdai...@gmail.com
Cc: CMake ML cmake@cmake.org
Message-ID:
caadwe9xg5mooennxwsx0gylczwqc_7tuyby+8zo0w4tu+-c...@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Dec 21, 2011 at 11:29 AM, Robert Dailey rcdai...@gmail.com
wrote:
Is there a target generated by CMake to build ONLY unit tests? I'm
using
Visual Studio 2008.
No, there is not.
If not, is there a way I can make one?
Yes, of course. You can do anything you want with a combination of
add_custom_command and add_custom_target.
Something worthwhile might be (whipped up quickly, untested):
# Implement include guard (e.g. reduce cmake --trace clutter)
if(UNIT_TEST_HELPERS_DEFINED)
return()
endif(UNIT_TEST_HELPERS_DEFINED)
set(UNIT_TEST_HELPERS_DEFINED true)
if(NOT TARGET unit_tests_all)
add_custom_target(unit_tests_all ALL)
endif(NOT TARGET unit_tests_all)
# Properly very worthwhile to have a fixed convention for unit test
# targets. Or perhaps use unit_test_? (...too?)
set(unit_test_targets_common_name_prefix ut_)
function(unit_test_register_conditional _target)
if(_target MATCHES ^${unit_test_targets_common_name_prefix})
add_dependencies(unit_tests_all ${_target})
endif(_target MATCHES ^${unit_test_targets_common_name_prefix})
function(unit_test_register_conditional _target)
function(super_power_target_post_handling _target)
unit_test_register_conditional(${_target})
...something_else_that_might_be_useful...()
endfunction(super_power_target_post_handling _target)
Then push that code into a CMake Module file (to be added to
cmake/Modules/ in your source root or some such),
and do
include(ModuleName)
where needed, and call
super_power_target_post_handling(current_target)
for every target where common post-handling might be useful.
But obviously super_power_target_post_handling() shouldn't fetch
your morning cereals - it should still contain functionality
that's specific enough, to not end up with messy imprecise (unknown!)
handling
that might change at any time.
And then, in case there's a build shell script, one could implement
poor man's unit test handling by doing something like:
[ ... run build stuff ... ]
pseudo_random=$(date +%s) # UNIX Epoch seconds (don't use %N nanoseconds
since it's not portable, plus it's overkill)
run_tests=$((${pseudo_random} % 42)) # modulo, obviously
if [ ${run_tests} -eq 0 ]; then
echo INFO: running unit tests...
[[[ result of grep CMAKE_BUILD_COMMAND CMakeCache.txt ]]] unit_tests_all
fi
Andreas Mohr
--
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] Support for RVDS 4.1: ARM C/C++ and ASM compilers.
On Wednesday 21 December 2011, Abdelrazak Younes wrote: Hi Alexander, Just wanted to let you know that, thanks to your assistance, we did some more work on this. Please refer to the issue: http://public.kitware.com/Bug/view.php?id=12614 It would be nice if this work could be integrated in next release of CMake. I'll have a look. It would be 2.8.8, 2.8.7 is basically done now. Thanks Alex -- 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] Upcoming What's New in CMake 2.8.7 webinar
On Wednesday 21 December 2011, David Cole wrote: The CMake team is hard at work on the 2.8.7 release - we announcedhttp://www.kitware.com/blog/home/post/208 CMake 2.8.7 rc1 on December 8th, and we expect to release the final version by the end of the year. Want to learn more? Then please join us on January 4th from 12:00-12:20 p.m. EST, when I will be presenting a free webinar highlighting what’s new in the CMake 2.8.7 release and giving a preview of what’s in the pipeline. You'll also get a chance to ask the CMake team any questions you may have on this release in particular or CMake in general. You can register for this event through GoToWebinarhttps://www3.gotomeeting.com/register/152723134 . https://www3.gotomeeting.com/register/152723134 Please note that you'll need to attend this webinar from a Windows or Mac computer - GoToWebinar does not yet support Linux. Are there plans for GoToWebinar to support also Linux ? It's really a pity that also the other webinars by Kitware exclude Linux :-/ Alex -- 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] Upcoming What's New in CMake 2.8.7 webinar
On Wed, Dec 21, 2011 at 3:50 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: On Wednesday 21 December 2011, David Cole wrote: The CMake team is hard at work on the 2.8.7 release - we announcedhttp://www.kitware.com/blog/home/post/208 CMake 2.8.7 rc1 on December 8th, and we expect to release the final version by the end of the year. Want to learn more? Then please join us on January 4th from 12:00-12:20 p.m. EST, when I will be presenting a free webinar highlighting what’s new in the CMake 2.8.7 release and giving a preview of what’s in the pipeline. You'll also get a chance to ask the CMake team any questions you may have on this release in particular or CMake in general. You can register for this event through GoToWebinarhttps://www3.gotomeeting.com/register/152723134 . https://www3.gotomeeting.com/register/152723134 Please note that you'll need to attend this webinar from a Windows or Mac computer - GoToWebinar does not yet support Linux. Are there plans for GoToWebinar to support also Linux ? It's really a pity that also the other webinars by Kitware exclude Linux :-/ Agreed, I can't view them on my desktop. I have access to those other platforms on secondary machines at least, but it would be great to allow viewing of our webinars on the platforms we are targeting. Are there any good alternatives you know of Alex? Marcus -- 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] Upcoming What's New in CMake 2.8.7 webinar
On Wed, Dec 21, 2011 at 3:50 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: On Wednesday 21 December 2011, David Cole wrote: The CMake team is hard at work on the 2.8.7 release - we announcedhttp://www.kitware.com/blog/home/post/208 CMake 2.8.7 rc1 on December 8th, and we expect to release the final version by the end of the year. Want to learn more? Then please join us on January 4th from 12:00-12:20 p.m. EST, when I will be presenting a free webinar highlighting what’s new in the CMake 2.8.7 release and giving a preview of what’s in the pipeline. You'll also get a chance to ask the CMake team any questions you may have on this release in particular or CMake in general. You can register for this event through GoToWebinarhttps://www3.gotomeeting.com/register/152723134 . https://www3.gotomeeting.com/register/152723134 Please note that you'll need to attend this webinar from a Windows or Mac computer - GoToWebinar does not yet support Linux. Are there plans for GoToWebinar to support also Linux ? I do not know about GoToWebinar's future plans. I've asked our communications group whether they know or not -- I'll let you know if I find out anything new. It's really a pity that also the other webinars by Kitware exclude Linux :-/ We are not intentionally excluding Linux, believe me. We are striving to provide the best thing we can in a cost-effective manner in this case. We have certainly tried several different packages before settling on GoToMeeting. Each one out there has some silly limitation... Alex -- 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
[CMake] wrong line endings in cmake-2.8.7-rc1-1-src.tar.bz2 ?
http://www.cmake.org/files/v2.8/cmake-2.8.7-rc1-1-src.tar.bz2 seems to have DOS line endings, which leads the the following error when running configure on linux: /home/dank/Downloads/cmake-2.8.7/Bootstrap.cmk/cmConfigure.h:29: error: missing terminating character The command find . -type f -print0 | xargs -0 perl -p -i -e 'tr/\015//d' forcibly removes CR's from the whole tree and lets configure succeed, but presumably that shouldn't be needed. Hasn't anyone else run into this? -- 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] wrong line endings in cmake-2.8.7-rc1-1-src.tar.bz2 ?
That is the cygwin tar.bz2 file. If you want a Linux line endings source tarball, use: cmake-2.8.7-rc1.tar.gzhttp://cmake.org/files/v2.8/cmake-2.8.7-rc1.tar.gz Or wait a few minutes (hours) for rc2... :-) HTH, David On Wed, Dec 21, 2011 at 6:21 PM, Dan Kegel d...@kegel.com wrote: http://www.cmake.org/files/v2.8/cmake-2.8.7-rc1-1-src.tar.bz2 seems to have DOS line endings, which leads the the following error when running configure on linux: /home/dank/Downloads/cmake-2.8.7/Bootstrap.cmk/cmConfigure.h:29: error: missing terminating character The command find . -type f -print0 | xargs -0 perl -p -i -e 'tr/\015//d' forcibly removes CR's from the whole tree and lets configure succeed, but presumably that shouldn't be needed. Hasn't anyone else run into this? -- 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] wrong line endings in cmake-2.8.7-rc1-1-src.tar.bz2 ?
Aha, thanks for the explanation. -- 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
[CMake] CMake 2.8.7-rc2 ready for testing!
The CMake 2.8.7 release candidate stream continues! You can find the source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D This email is also available as a blog post: http://www.kitware.com/blog/home/post/216 Some of the notable changes in this release are: - improved Eclipse support - incremental improvements to the AUTOMOC feature added in the previous release - more cryptographic hash implementations (SHA1, SHA224, SHA256, SHA384, SHA512) - file(...) and string(...) command additions for computing hash values - added LINK_PUBLIC and LINK_PRIVATE options to target_link_libraries command - and, as always, various minor bug fixes Similar to the previous release, we do not have pre-built binaries for the SunOS anymore. However, now we have two sets of installers for the Mac. The Darwin versions are for Mac OSX 10.4 and later, and are ppc;i386 universal binaries. The Darwin64 versions are for 10.6 and later, and are x86_64;i386 universal binaries. Following is the complete list of changes in this release. Please try this version of CMake on your projects and report any issues to the list or the bug tracker. Happy building! -Dave Changes in CMake 2.8.7-rc2 (since 2.8.7-rc1) Alex Neundorf (5): automoc: default to strict mode, use CMAKE_AUTOMOC_RELAXED_MODE automoc: improved warning message in relaxed mode Remove trailing whitespace Add comment about one more problem of the C depency scanner. fix #12262: dependency scanning for ASM files Bill Hoffman (1): Fix the case where cmake --build failed with two project cmds in one file. Brad King (11): KWSys: Correctly handle empty environment variables FortranCInterface: Work around mingw32-make trouble with parens Xcode: Create separate rerun dependencies for subprojects (#12616) Fix Intel Fortran .vfproj files for VS 10 HP: Drive shared library linking with compiler front end Follow all dependencies of shared library private dependencies Do not link private dependent shared libraries on OS X 10.4 Avoid clobbering variable 'OUTPUT' in compiler tests (#12628) Fix and simplify Fortran test compiler compatibility check CTest: Recognize Intel errors without space before colon (#12627) Windows-GNU: Remove extra quotes in GNUtoMS rule variable David Cole (4): Release: Increase timeout for slow-testing cygwin build Modules: Use windres as rc compiler base name for cross-compiles (#12480) Tests: Only really run MFC test if we can build MFC apps (#11213) FindBoost: Quote possibly empty string argument (#12273) Eric NOULARD (1): CPackRPM fix #0012608 and unoticed related bug Johan Fänge (1): CMake: Fix progress reporting for custom targets (#12441) Mike McQuaid (2): Unset configurations variable when no build type. Improve component support and output indentation. Raphael Kubo da Costa (2): Remove the apparently outdated README in Source/QtDialog. QtDialog: Set Ctrl+Q as the shortcut for quitting the program. Tim Gallagher (2): FindLAPACK: Correct CMAKE_FIND_LIBRARY_SUFFIXES spelling (#12624) FindLAPACK: List thread libs to avoid link errors (#12625) Valat Sébastien (1): CTest: Do not get CDash version without drop site (#12618) -- 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] CMake 2.8.7-rc2 ready for testing!
The CMake 2.8.7 release candidate stream continues! You can find the source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D This will become the final build of CMake 2.8.7 next Wednesday unless somebody finds and reports a showstopping (crasher, serious behavioral regression) issue between now and then. This email is also available as a blog post: http://www.kitware.com/blog/home/post/216 Some of the notable changes in this release are: - improved Eclipse support - incremental improvements to the AUTOMOC feature added in the previous release - more cryptographic hash implementations (SHA1, SHA224, SHA256, SHA384, SHA512) - file(...) and string(...) command additions for computing hash values - added LINK_PUBLIC and LINK_PRIVATE options to target_link_libraries command - and, as always, various minor bug fixes Similar to the previous release, we do not have pre-built binaries for the SunOS anymore. However, now we have two sets of installers for the Mac. The Darwin versions are for Mac OSX 10.4 and later, and are ppc;i386 universal binaries. The Darwin64 versions are for 10.6 and later, and are x86_64;i386 universal binaries. Following is the list of changes in this rc since the previous one. Please try this version of CMake on your projects and report any issues to the list or the bug tracker. Happy building! -Dave Changes in CMake 2.8.7-rc2 (since 2.8.7-rc1) Alex Neundorf (5): automoc: default to strict mode, use CMAKE_AUTOMOC_RELAXED_MODE automoc: improved warning message in relaxed mode Remove trailing whitespace Add comment about one more problem of the C depency scanner. fix #12262: dependency scanning for ASM files Bill Hoffman (1): Fix the case where cmake --build failed with two project cmds in one file. Brad King (11): KWSys: Correctly handle empty environment variables FortranCInterface: Work around mingw32-make trouble with parens Xcode: Create separate rerun dependencies for subprojects (#12616) Fix Intel Fortran .vfproj files for VS 10 HP: Drive shared library linking with compiler front end Follow all dependencies of shared library private dependencies Do not link private dependent shared libraries on OS X 10.4 Avoid clobbering variable 'OUTPUT' in compiler tests (#12628) Fix and simplify Fortran test compiler compatibility check CTest: Recognize Intel errors without space before colon (#12627) Windows-GNU: Remove extra quotes in GNUtoMS rule variable David Cole (4): Release: Increase timeout for slow-testing cygwin build Modules: Use windres as rc compiler base name for cross-compiles (#12480) Tests: Only really run MFC test if we can build MFC apps (#11213) FindBoost: Quote possibly empty string argument (#12273) Eric NOULARD (1): CPackRPM fix #0012608 and unoticed related bug Johan Fänge (1): CMake: Fix progress reporting for custom targets (#12441) Mike McQuaid (2): Unset configurations variable when no build type. Improve component support and output indentation. Raphael Kubo da Costa (2): Remove the apparently outdated README in Source/QtDialog. QtDialog: Set Ctrl+Q as the shortcut for quitting the program. Tim Gallagher (2): FindLAPACK: Correct CMAKE_FIND_LIBRARY_SUFFIXES spelling (#12624) FindLAPACK: List thread libs to avoid link errors (#12625) Valat Sébastien (1): CTest: Do not get CDash version without drop site (#12618) -- 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
[Cmake-commits] CMake branch, next, updated. v2.8.6-2309-gd93673a
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via d93673a5d3e2a0b0d0a9ef3d8afe9ff55a77b353 (commit) via a542139c9314f096d86ddaccd5737585b0bf5650 (commit) from 9a47eba294aeb006f0d30b8ac2c5fbf739559cf7 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d93673a5d3e2a0b0d0a9ef3d8afe9ff55a77b353 commit d93673a5d3e2a0b0d0a9ef3d8afe9ff55a77b353 Merge: 9a47eba a542139 Author: Bill Hoffman bill.hoff...@kitware.com AuthorDate: Wed Dec 21 14:50:17 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Dec 21 14:50:17 2011 -0500 Merge topic 'cmake_add_fortran_subdirectory' into next a542139 Remove fio library and add m to fix link on Sun. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a542139c9314f096d86ddaccd5737585b0bf5650 commit a542139c9314f096d86ddaccd5737585b0bf5650 Author: Bill Hoffman bill.hoff...@kitware.com AuthorDate: Wed Dec 21 14:49:19 2011 -0500 Commit: Bill Hoffman bill.hoff...@kitware.com CommitDate: Wed Dec 21 14:49:19 2011 -0500 Remove fio library and add m to fix link on Sun. diff --git a/Tests/VSGNUFortran/fortran/CMakeLists.txt b/Tests/VSGNUFortran/fortran/CMakeLists.txt index f96ac80..1d4d7be 100644 --- a/Tests/VSGNUFortran/fortran/CMakeLists.txt +++ b/Tests/VSGNUFortran/fortran/CMakeLists.txt @@ -13,6 +13,6 @@ target_link_libraries(hello world) if(CMAKE_Fortran_COMPILER_ID MATCHES SunPro) target_link_libraries(hello fsu) if(CMAKE_Fortran_PLATFORM_ID MATCHES SunOS) -target_link_libraries(hello fio sunmath) +target_link_libraries(hello sunmath m) endif() endif() --- Summary of changes: Tests/VSGNUFortran/fortran/CMakeLists.txt |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, release, updated. v2.8.6-439-ga1c9de5
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, release has been updated via a1c9de5635313258272fa1579a4c4d5d779a9788 (commit) via 25b159cdbf90fb34cf162bcf4938a15b95b4ea6e (commit) via b4c2f40653332dfd1ea6abb81bfa5ab6a22acfe1 (commit) via 7f8cf4236d523483560c500335a8644b5f769089 (commit) via cc9319e71785d021985b81cdb15df53a1eb5a994 (commit) via 7ca69a08cba0a28791dbb98b68b11e89ba5cafa4 (commit) via 7868061a6ba5a29a937e120cc6f3fe526396c5d4 (commit) via c24bdb05d01ae72594e3a1afea5d9c12f1728309 (commit) via d6a33f6d38d8989345840ddc218518fc86f3846a (commit) via 16dacf3a6a85af2b0b07a4634c3b5dfbe6ece3ca (commit) via 5badf5f734119199fa42377b25d415532191a710 (commit) via 4e985000124931cb8219da35cc507b4ccf05d30f (commit) via cdf522436f6623d8a2ded55aa3192a7041c7773b (commit) via 4bb3edfcb49db58d4683b4c6757eb251fd778e6c (commit) via ea6883752b7ad65a91af71611955ccb7b7055d76 (commit) via 318b0cdf2306a9198baa837885d65423e5f7fc96 (commit) via 4bb08e0a9b2d4b652f9bdf06f24c5db57c249abb (commit) via 84094cd155d415930631636e6c4c4822a861fd21 (commit) via 61da11ecd74461da6edb551d87e29d653df147ad (commit) via 3aa5432315fed4cbf983747bda666c6aa7455d9f (commit) via 0e598b7bcd2da655b23e02bef4e56e620c6286c5 (commit) via f7be6d616f06c08e3b955df5ef2d8c4b18243334 (commit) via ef086b5e41ac01e04fe1d7e416131b0d5939825f (commit) via 1706a7ed5b43f39dd6a8ff2f7ed7552b88463268 (commit) via 52d5f67ec7ac1f8c97a0aa51750b7496a25dcfa8 (commit) via 44b6b0b5df98f0b0a9e2302abe41311379cb034c (commit) via 8f8ee53729f4f75f75eafc39e8a9b8b5a86af3a7 (commit) via 65db5b4a993937aca84d600d3370eb584a51354a (commit) via 2f82798ef88e8d03aa6457e57faebf4fc16d1660 (commit) via e44cdb04f1172f8cb516400e09d2ec0fc1379039 (commit) via be637d7a92ca20c18a66562d650b307e21eeffa4 (commit) via c6c82f9e3e921a3988a2e8b4012e3942fa22db40 (commit) via 037616f194f72b3563edd0c5b5c028694b2fcb50 (commit) via ac9453c371132d12d975385be8376af0f76d8078 (commit) via c68a780dece71b23664ea65c670a5771e638245a (commit) via e945df2a7ea0d0e0c9a498766bc44e6051a743b9 (commit) via 765e9d30ae970a9075c6dd463e881a3635d1fabc (commit) via f189c5d7d340eba74b0a812fb873695dba487316 (commit) via 7e6c8edb15e98bc932dabd7db051dc2d0bd8427f (commit) via 762930efe809edc203065efac380305fd83374a8 (commit) via b15071791c88bebfb8a157611684701313e6176d (commit) via c544545c6364ed7081d60772505278c9f199ecf8 (commit) via 56e04991048ff27e2af1fdcf98fc731ca59280a3 (commit) via 56f29f48c2f93251838519cade02ce57dd77510f (commit) via fcb2a27982bf8648c3aa3de58a4d54c7d700f580 (commit) via 470bcfad7ba51fd2a4bd04fe2a4aa68582a0b2a1 (commit) via 5f6985ac869150e468f8ad388bdbb8a39010cbb5 (commit) via 5d9934312d0b553eafb7c690487215cff7ddedb3 (commit) via 0a6543d957463f0a7f7a585cc43468174c1204a0 (commit) via e474dcb23197489640456b46862a5aa7019834a5 (commit) via 183b95098ea4102da5ca510e8c7a36106a5c257a (commit) via 5720e1f634b0253013b1887a924492f3dd29f012 (commit) via 4ed1769186f0622efced9d89e6593d136c920dd2 (commit) via 7ab1162eaa1490be745f2b2a24ba7b4a3ec69112 (commit) via 6ddb1e5b9a3eff941ad12d29609839871fe518ed (commit) via 6571f4655a4e86986ca30215f46e6867c0ff7b92 (commit) via b3c42cb0123c7d21b6a23b1b7517cbb27d55df76 (commit) via f603cf2d36bced4fbb191354980849f4c888fb8e (commit) via 96fc5d5d0701c98a5029469c8a9dcc6aa6576278 (commit) via 4e9274e95498e7bf30d912ca6f7fbbb6d6ab970b (commit) via 3c101429a4e563f4c711cae84317806284784eb6 (commit) via 121c29553fc66575f231bebda6682b21216c1e03 (commit) via 52f937aea81eaa531b46c0c8e791e1d1391c705d (commit) via 99771d55beee37d8e4a1cff19570c2847ce221cd (commit) via 53455f938be36872b3ed74bbb079c63de85aae67 (commit) via 85344d767bc8430ad4e844331461e66791477133 (commit) via e8b8f0eda8f5d757582310a9f5d58c90d7074e3f (commit) via 4cb73c43ac13a4b796c61da137a1576c8c6a4d23 (commit) via 61a7da279a71f251aa9ff9d5713838f0a20cbead (commit) via 33c24b210099c6cc9fc8f7b50621014ab6b3 (commit) via c213eb9cbf73c2d0ad723f1afb079508a731410f (commit) from 56b5a72ebd869d32ebb7bf349009e760c9bb3b8f (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a1c9de5635313258272fa1579a4c4d5d779a9788 commit
[Cmake-commits] CMake branch, master, updated. v2.8.6-437-gb81ef05
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via b81ef0533c19a979868040b9bbebd49209297bef (commit) from b4c2f40653332dfd1ea6abb81bfa5ab6a22acfe1 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b81ef0533c19a979868040b9bbebd49209297bef commit b81ef0533c19a979868040b9bbebd49209297bef Author: KWSys Robot kwro...@kitware.com AuthorDate: Thu Dec 22 00:05:19 2011 -0500 Commit: KWSys Robot kwro...@kitware.com CommitDate: Thu Dec 22 00:05:19 2011 -0500 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 018f815..3c2549c 100644 --- a/Source/kwsys/kwsysDateStamp.cmake +++ b/Source/kwsys/kwsysDateStamp.cmake @@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR 2011) SET(KWSYS_DATE_STAMP_MONTH 12) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 21) +SET(KWSYS_DATE_STAMP_DAY 22) --- Summary of changes: Source/kwsys/kwsysDateStamp.cmake |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
