Re: [cmake-developers] Introductions and questions

2014-01-28 Thread David Cole
Awesome, welcome! Seconded! Thirded! -- 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

Re: [cmake-developers] RFC: add version to project() call

2014-01-28 Thread Brad King
On 01/23/2014 04:08 PM, Alexander Neundorf wrote: Any more comments left ? Moving the discussion from http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/9156/focus=9158 back to the thread where it belongs: On 01/27/2014 04:58 PM, Stephen Kelly wrote: Though I still don't like

Re: [cmake-developers] Avoid installing Sphinx html build files (was: Preparing for CMake 3.0.0-rc1)

2014-01-28 Thread Brad King
On 01/27/2014 05:13 PM, Stephen Kelly wrote: Some new files are installed with the new docs system which maybe should not be installed. doc/cmake-2.8.12/html/.buildinfo doc/cmake-2.8.12/html/objects.inv Good catch, thanks: Help: Do not install Sphinx html build info files

Re: [cmake-developers] RFC: add version to project() call

2014-01-28 Thread Jean-Christophe Fillion-Robin
I would vote for (2), that way people using the latest and greatest of CMake won't have to enable any variable and it will work out of the box. Jc On Tue, Jan 28, 2014 at 9:10 AM, Brad King brad.k...@kitware.com wrote: On 01/23/2014 04:08 PM, Alexander Neundorf wrote: Any more comments left

Re: [cmake-developers] RFC: add version to project() call

2014-01-28 Thread Brad King
On 01/28/2014 11:16 AM, Jean-Christophe Fillion-Robin wrote: I would vote for (2), that way people using the latest and greatest of CMake won't have to enable any variable and it will work out of the box. No one has to set a magic variable in Alex's current design either. The

Re: [cmake-developers] Avoid installing Sphinx html build files (was: Preparing for CMake 3.0.0-rc1)

2014-01-28 Thread Stephen Kelly
Brad King wrote: /home/stephen/dev/prefix/qtbase/kde/doc/cmake-2.8.12/html/_sources/* Those are for the Show Source links on each page. I don't think that's valuable. I'd just remove the link. Alternatively, consider something like the no-duplicate-install-doc-src topic in my clone

Re: [cmake-developers] Review Request for ExternalProjects: Only update certain git submodules

2014-01-28 Thread Gereon Kremer
Hi, Any success with this patch? I was hoping to get this done soon :-) Cheers, Gereon On 01/15/2014 04:21 PM, Jean-Christophe Fillion-Robin wrote: Hi Folks, That would be a great contribution. I will give a try to the patch by the beginning of next week. This is something that would be

Re: [cmake-developers] Avoid installing Sphinx html build files

2014-01-28 Thread Brad King
On 01/28/2014 11:43 AM, Stephen Kelly wrote: Brad King wrote: /home/stephen/dev/prefix/qtbase/kde/doc/cmake-2.8.12/html/_sources/* Those are for the Show Source links on each page. I don't think that's valuable. I'd just remove the link. It's also for the search page:

Re: [cmake-developers] RFC: add version to project() call

2014-01-28 Thread Matthew Woehlke
On 2014-01-28 11:16, Jean-Christophe Fillion-Robin wrote: On Tue, Jan 28, 2014 at 9:10 AM, Brad King wrote: So our options are (1) Design new behavior in a way that requires a change to the project to activate. (2) Add a policy. The policy should only trigger when the project()

Re: [cmake-developers] Avoid installing Sphinx html build files

2014-01-28 Thread Stephen Kelly
Brad King wrote: Alternatively, consider something like the no-duplicate-install-doc-src topic in my clone instead. We can't reference the source tree for redistributable docs. Oh, I didn't intend for that. What about using a relative path? Thanks, Steve. -- Powered by www.kitware.com

Re: [cmake-developers] Avoid installing Sphinx html build files

2014-01-28 Thread Brad King
On 01/28/2014 12:35 PM, Stephen Kelly wrote: Brad King wrote: Alternatively, consider something like the no-duplicate-install-doc-src topic in my clone instead. We can't reference the source tree for redistributable docs. Oh, I didn't intend for that. What about using a relative path?

Re: [cmake-developers] Review Request for ExternalProjects: Only update certain git submodules

2014-01-28 Thread Brad King
On 01/28/2014 11:55 AM, Gereon Kremer wrote: Any success with this patch? I think others have had long enough to provide pre-integration feedback. I was hoping to get this done soon :-) I've put the changes in 'next' for testing: ExternalProject: Add option GIT_SUBMODULES

Re: [cmake-developers] Avoid installing Sphinx html build files

2014-01-28 Thread Stephen Kelly
Brad King wrote: On 01/28/2014 12:35 PM, Stephen Kelly wrote: Brad King wrote: Alternatively, consider something like the no-duplicate-install-doc-src topic in my clone instead. We can't reference the source tree for redistributable docs. Oh, I didn't intend for that. What about using

[cmake-developers] CMake 2.8.12.2 available for download

2014-01-28 Thread Robert Maynard
Some problems were reported with the 2.8.12 release. Thanks to the work of Brad King, Robert Maynard, Rolf Eike Beer, Ruslan Baratov, and Ted Kremenek those problems have been fixed. We've prepared a 2.8.12.2 bug fix release to address those issues. Some of the notable changes in this patch

Re: [cmake-developers] RFC: add version to project() call

2014-01-28 Thread Alexander Neundorf
On Tuesday 28 January 2014, Brad King wrote: On 01/23/2014 04:08 PM, Alexander Neundorf wrote: Any more comments left ? Moving the discussion from http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/9156/focu s=9158 back to the thread where it belongs: On 01/27/2014

Re: [CMake] Announcing CMake BASIS, a set of CMake based project interoperability and automation tools

2014-01-28 Thread Matthew Woehlke
On 2014-01-28 01:11, Andrew Hundt wrote: On Mon, Jan 27, 2014 at 3:30 PM, Matthew Woehlke wrote: I didn't look at it yet, but to be optimally useful I would hope that an implementation of generating doxygen documentation would: What we have won't be optimally useful, but it is very useful. I

Re: [CMake] Linking intel (icpc/icc) compiled libraries with gnu (g++/gcc/ar) compiled targets

2014-01-28 Thread Pettey . Lucas
Do you have a line similar to target_link_libraries(foo.exe ${IntelCompilerLibrary_LIBRARIES})? Also check to see if IntelCompilerLibrary_LIBRARIES is being set correctly by having it print out in a message. I have had times where the entire SET needs the quotes:

Re: [CMake] Does a ctested build work with make -j

2014-01-28 Thread Bill Hoffman
On 1/27/2014 6:05 PM, Matthew Woehlke wrote: What would be the difference in this context between MAKECOMMAND and CMAKE_MAKE_PROGRAM? I was just reading somewhere¹ that prefers the latter... (¹ https://github.com/Slicer/Slicer/commit/38905c9) MAKECOMMAND is set by CTest.cmake and gets put in

Re: [CMake] Does a ctested build work with make -j

2014-01-28 Thread Bill Hoffman
On 1/28/2014 10:46 AM, Bill Hoffman wrote: MAKECOMMAND is set by CTest.cmake and gets put in the file that CTest reads to get the build command. If you set that make Experimental will work. If you note the change in the Sliicer github link you sent, you can see it sets

[CMake] problem with mac linker flags

2014-01-28 Thread Alexander von Below
Hello, I'm the new guy :D So I inherited a project which uses CMake as part of it's build process. It is generating Xcode project files (for an iOS static library), and I am stumbling across an old error: http://www.cmake.org/pipermail/cmake/2010-December/041518.html The problem, again, is

[CMake] CMake 2.8.12.2 available for download

2014-01-28 Thread Robert Maynard
Some problems were reported with the 2.8.12 release. Thanks to the work of Brad King, Robert Maynard, Rolf Eike Beer, Ruslan Baratov, and Ted Kremenek those problems have been fixed. We've prepared a 2.8.12.2 bug fix release to address those issues. Some of the notable changes in this patch

[CMake] Unable to include a custom (i.e., non-Apple) framework in a CMake iOS project

2014-01-28 Thread David Hirvonen
I've been using the following macro: macro(ADD_FRAMEWORK fwname appname) find_library(FRAMEWORK_${fwname} NAMES ${fwname} PATHS ${CMAKE_OSX_SYSROOT}/System/Library PATH_SUFFIXES Frameworks NO_DEFAULT_PATH) if( ${FRAMEWORK_${fwname}} STREQUAL FRAMEWORK_${fwname}-NOTFOUND)

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-7302-g29c4543

2014-01-28 Thread Brad King
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 29c45433c4ce11f6b1ddb561001b00598f1be6d0 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-7307-gb70bfe6

2014-01-28 Thread Brad King
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 b70bfe6d97d3756f58fba12534888286958fe454 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-7311-g6ed015f

2014-01-28 Thread Brad King
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 6ed015f4ef359a22629abc32dd4bef5e82176db7 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-7313-ge27be1b

2014-01-28 Thread Brad King
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 e27be1b5ee8d53089418b770ad7f1d4b56c7172d (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-7316-g0cfd274

2014-01-28 Thread Brad King
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 0cfd274e41883024b48911789dacaa3c9d49850b (commit) via

[Cmake-commits] CMake branch, maint, updated. v2.8.12.2

2014-01-28 Thread Brad King
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, maint has been updated via 0b3781e4c497566acaa504d4106d11c02a642501 (commit) via

[Cmake-commits] CMake branch, release, updated. v2.8.12.2

2014-01-28 Thread Brad King
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 0b3781e4c497566acaa504d4106d11c02a642501 (commit) via

[Cmake-commits] CMake annotated tag, v2.8.12.2, created. v2.8.12.2

2014-01-28 Thread Brad King
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 annotated tag, v2.8.12.2 has been created at dcf19b00ded0151666cc8c8dae08ac01df64deb9 (tag) tagging

[Cmake-commits] CMake branch, next, updated. v2.8.12.2-7304-g59b1c93

2014-01-28 Thread Brad King
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 59b1c93d3ec2f38d3901376b72011e158869 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.2-1270-g8157f58

2014-01-28 Thread Brad King
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 8157f58d024547aef221259b65ce2c502ee514d4 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.2-7306-g35560f8

2014-01-28 Thread Brad King
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 35560f8e806a0d6c55832de452726e0b1c9bcd97 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.2-7316-g7ffd00b

2014-01-28 Thread Stephen Kelly
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 7ffd00b648548ab9f5286b5e8427a650fde57b04 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.2-7318-gf481c00

2014-01-28 Thread Brad King
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 f481c002b0a6527555004f547b62491cc3dcc0bd (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.2-1271-g5d08ba9

2014-01-28 Thread Kitware Robot
Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 1267363..4bbc4e7 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -2,5 +2,5 @@ set(CMake_VERSION_MAJOR 2) set(CMake_VERSION_MINOR 8) set(CMake_VERSION_PATCH 12) -set(CMake_VERSION_TWEAK 20140128