[Cmake-commits] CMake branch, master, updated. v3.9.2-789-gd6b49ee

[Kitware Robot]

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  d6b49ee6767e8b21eee08d218ca5f599ad8f978b (commit)
  from  dd67b65188a03be8b1c961d5cd932f654e2566ae (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d6b49ee6767e8b21eee08d218ca5f599ad8f978b
commit d6b49ee6767e8b21eee08d218ca5f599ad8f978b
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Thu Sep 14 00:01:05 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Thu Sep 14 00:01:05 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 9c1da41..49fe6f2 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 9)
-set(CMake_VERSION_PATCH 20170913)
+set(CMake_VERSION_PATCH 20170914)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.9.2-788-gdd67b65

[Kitware Robot]

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  dd67b65188a03be8b1c961d5cd932f654e2566ae (commit)
   via  7ed35aa331b58fce396e68d756f139b098acbac0 (commit)
  from  420874bfaa20772525c60b20d1ee5b6ef5ed9298 (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 -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dd67b65188a03be8b1c961d5cd932f654e2566ae
commit dd67b65188a03be8b1c961d5cd932f654e2566ae
Merge: 420874b 7ed35aa
Author: Craig Scott 
AuthorDate: Thu Sep 14 00:38:34 2017 +
Commit: Kitware Robot 
CommitDate: Wed Sep 13 20:38:40 2017 -0400

Merge topic 'improve-graphviz-doc'

7ed35aa3 Docs: Improve markup for graphviz related documentation

Acked-by: Kitware Robot 
Merge-request: !1236


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7ed35aa331b58fce396e68d756f139b098acbac0
commit 7ed35aa331b58fce396e68d756f139b098acbac0
Author: Jano Svitok 
AuthorDate: Tue Sep 5 18:34:44 2017 +0200
Commit: Jano Svitok 
CommitDate: Mon Sep 11 14:45:36 2017 +0200

Docs: Improve markup for graphviz related documentation

- add hyperlink to CMakeGraphVizOptions.cmake in cmake(1)
- improve markup in CMakeGraphVizOptions.cmake

diff --git a/Help/manual/cmake.1.rst b/Help/manual/cmake.1.rst
index 8aece23..6eef6c6 100644
--- a/Help/manual/cmake.1.rst
+++ b/Help/manual/cmake.1.rst
@@ -69,11 +69,11 @@ Options
  See `Find-Package Tool Mode`_.
 
 ``--graphviz=[file]``
- Generate graphviz of dependencies, see CMakeGraphVizOptions.cmake for more.
+ Generate graphviz of dependencies, see :module:`CMakeGraphVizOptions` for 
more.
 
  Generate a graphviz input file that will contain all the library and
  executable dependencies in the project.  See the documentation for
- CMakeGraphVizOptions.cmake for more details.
+ :module:`CMakeGraphVizOptions` for more details.
 
 ``--system-information [file]``
  Dump information about this system.
diff --git a/Modules/CMakeGraphVizOptions.cmake 
b/Modules/CMakeGraphVizOptions.cmake
index 420e3a9..3976581 100644
--- a/Modules/CMakeGraphVizOptions.cmake
+++ b/Modules/CMakeGraphVizOptions.cmake
@@ -11,19 +11,19 @@
 # ^^
 #
 # CMake
-# can generate graphviz files, showing the dependencies between the
+# can generate `graphviz `_ files, showing the 
dependencies between the
 # targets in a project and also external libraries which are linked
-# against.  When CMake is run with the --graphviz=foo.dot option, it will
+# against.  When CMake is run with the ``--graphviz=foo.dot`` option, it will
 # produce:
 #
-# * a foo.dot file showing all dependencies in the project
-# * a foo.dot. file for each target, file showing on which other 
targets the respective target depends
-# * a foo.dot..dependers file, showing which other targets depend on 
the respective target
+# * a ``foo.dot`` file showing all dependencies in the project
+# * a ``foo.dot.`` file for each target, file showing on which other 
targets the respective target depends
+# * a ``foo.dot..dependers`` file, showing which other targets depend 
on the respective target
 #
 # This can result in huge graphs.  Using the file
-# CMakeGraphVizOptions.cmake the look and content of the generated
+# ``CMakeGraphVizOptions.cmake`` the look and content of the generated
 # graphs can be influenced.  This file is searched first in
-# ${CMAKE_BINARY_DIR} and then in ${CMAKE_SOURCE_DIR}.  If found, it is
+# :variable:`CMAKE_BINARY_DIR` and then in :variable:`CMAKE_SOURCE_DIR`.  If 
found, it is
 # read and the variables set in it are used to adjust options for the
 # generated graphviz files.
 #

---

Summary of changes:
 Help/manual/cmake.1.rst|4 ++--
 Modules/CMakeGraphVizOptions.cmake |   14 +++---
 2 files changed, 9 insertions(+), 9 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [CMake] Adding compile and build type tests to CMake/CTest

[Nagy-Egri Máté Ferenc via CMake]

Indeed, such a feature would come in handy to test libraries for correctly 
failing on erronous user input.

What amazes me even more is that noone has stepped up yet to create CBench. A 
utility executable for measuring compilation times and capture output of some 
(micro)benchmark instrumentation, either one of its own or some external tool, 
like google/benchmark. Present output either as a table on the console, ASCII 
art or as .xls/.html… you get what I mean.

Has it never bothered anyone enough yet to create quantitative output of a 
build, other than the binary failed/passed kind tests?

Feladó: Robert Ramey
Elküldve: 2017. szeptember 12., kedd 19:12
Címzett: cmake@cmake.org
Tárgy: Re: [CMake] Adding compile and build type tests to CMake/CTest

On 9/4/17 6:40 AM, Edward Diener wrote:
> Boost Build has tests for running an application successfully or not, 
> for compiling one or more source files successfully or not, and for 
> building one or more source files into an exe or not. These tests in 
> Boost Build are the run/run-fail, compile/compile-fail, and 
> link/link-fail rules.
> 
> CMake/CTest has the exact equivalent to the run/run-fail rule in its 
> add_test framework, but there is not add_test equivalent to the other 
> two sets of rules. It sure would be nice, when Boost transitions to 
> using CMake/CTest instead of Boost Build, if CMake/CTest had the 
> equivalent of the other two sets of types of test in its add_test 
> framework.
> 
> Is there any consensus that these other two types of tests might be 
> valuable for CMake/CTest, or any way to make this happen ?
> 

I would like to second this suggestion.  The absence of this feature 
presents a huge obstacle to replicating the functionality of the boost 
build functionality with CMake.  It's amazing to me that after so many 
years CMake doesn't have this functionality already.  It certainly seems 
to me that this would be easy to implement.

I'm aware that suggestions using CMake macros have been proposed.  But 
to the inexperienced user they are not intuitive or easy to understand.

Could we get some response on Edward's suggestion here? It's a serious 
obstacle to implementing support of CMake in Boost libraries.

Robert Ramey

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CMakeLists.txt location

[Nils Gladitz]

On 13.09.2017 14:31, Alain Miniussi wrote:



On 13/09/2017 12:49, Nils Gladitz wrote:

 [...]
Do you have a minimal reproducible example for that behaviour?


e.g. given:

   cmake_minimum_required(VERSION 2.8.0)

project(Foo NONE)

file(WRITE foo/CMakeLists.txt "add_executable()")

add_subdirectory(foo)


I get:

CMake Error at foo/CMakeLists.txt:1 (add_executable):
  add_executable called with incorrect number of arguments


Even with the oldest CMake version currently available to me (2.8.0).

That test case works for me too. But my real case does not.
I think it would be tricky to minimized, what is failling is the 
second run of cmake, after a modification in the build system or in a 
configure_file source.



CMake Error at CMakeLists.txt:14 (add_executable):
  Target "cmTC_60ee6" links to item " -Xlinker --enable-new-dtags 
-Xlinker

  -rpath -Xlinker
/opt/software/common/intel/impi/2017.0.098/intel64/lib/release_mt 
-Xlinker

  -rpath -Xlinker /opt/software/common/intel/impi/2017.0.098/intel64/lib
  -Xlinker -rpath -Xlinker 
/opt/intel/mpi-rt/2017.0.0/intel64/lib/release_mt

  -Xlinker -rpath -Xlinker /opt/intel/mpi-rt/2017.0.0/intel64/lib
/opt/software/occigen/libraries/boost/1_63_0/intel/17.0/intelmpi/2017.0.098/lib/libboost_serialization.a" 

  which has leading or trailing whitespace.  This is now an error 
according

  to policy CMP0004.


CMake Error: Internal CMake error, TryCompile generation of cmake failed
INFO   Boost MPI not available or too old:


Now, maybe the problem is with a CMakeLists.tx generated by a 
try_compile.

Indicating that I would actually need the location of the try_compile.

Thanks

Alain 


Ok, I assume that means you are actually looking at CMakeError.log and 
not the output you get from CMake concerning your own project's 
configuration run.
try_compile() runs aren't necessarily meant to succeed but rather their 
outcome is used in conditionals which may or may not have fatal outcomes 
for your actual project.


If a fatal diagnostic is produced based on such a conditional it would 
be visible in CMake's direct output (with file and line information) not 
CMakeError.log.
You only need to look at CMakeError.log to understand why a 
try_compile() did not succeed even though you would have expected it to.


The CMakeLists.txt where the error comes from in your failing 
try_compile() is generated and temporary so you will not find it in your 
own sources.


Nils
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CMakeLists.txt location

[Alain Miniussi]

On 13/09/2017 12:49, Nils Gladitz wrote:

 [...]
Do you have a minimal reproducible example for that behaviour?


e.g. given:

   cmake_minimum_required(VERSION 2.8.0)

project(Foo NONE)

file(WRITE foo/CMakeLists.txt "add_executable()")

add_subdirectory(foo)


I get:

CMake Error at foo/CMakeLists.txt:1 (add_executable):
  add_executable called with incorrect number of arguments


Even with the oldest CMake version currently available to me (2.8.0).

That test case works for me too. But my real case does not.
I think it would be tricky to minimized, what is failling is the second 
run of cmake, after a modification in the build system or in a 
configure_file source.



CMake Error at CMakeLists.txt:14 (add_executable):
  Target "cmTC_60ee6" links to item " -Xlinker --enable-new-dtags -Xlinker
  -rpath -Xlinker
  /opt/software/common/intel/impi/2017.0.098/intel64/lib/release_mt 
-Xlinker

  -rpath -Xlinker /opt/software/common/intel/impi/2017.0.098/intel64/lib
  -Xlinker -rpath -Xlinker 
/opt/intel/mpi-rt/2017.0.0/intel64/lib/release_mt

  -Xlinker -rpath -Xlinker /opt/intel/mpi-rt/2017.0.0/intel64/lib
/opt/software/occigen/libraries/boost/1_63_0/intel/17.0/intelmpi/2017.0.098/lib/libboost_serialization.a"
  which has leading or trailing whitespace.  This is now an error according
  to policy CMP0004.


CMake Error: Internal CMake error, TryCompile generation of cmake failed
INFO   Boost MPI not available or too old:


Now, maybe the problem is with a CMakeLists.tx generated by a try_compile.
Indicating that I would actually need the location of the try_compile.

Thanks

Alain




Nils



--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CMakeLists.txt location

[Mateusz Loskot]

On 13 September 2017 at 12:49, Nils Gladitz  wrote:
> On 13.09.2017 12:22, Alain Miniussi wrote:
>> On 13/09/2017 11:16, Nils Gladitz wrote:
>>> On 13.09.2017 10:52, Alain Miniussi wrote:

 Is there a way, when printing CMake error, to get the exact location of
 the CMakeLists.txt ?

 For example, right now, when I have:

 CMake Error at CMakeLists.txt:14 (add_executable):

 I  need to scan all my CMakeLists.txt (~200) to check which one has
 add_executable at line 14.
>>>
>>>
>>> CMake includes the (relative to the root source directory) path for me
>>> e.g.:
>>> CMake Error at Source/CMakeLists.txt:4 (add_executable):
>>
>> Well, it never did for me:
>> $grep add_executable CMakeLists.txt
>> $
>
> Do you have a minimal reproducible example for that behaviour?
>
> e.g. given:
>
>cmake_minimum_required(VERSION 2.8.0)
> project(Foo NONE)
> file(WRITE foo/CMakeLists.txt "add_executable()")
> add_subdirectory(foo)
>
> I get:
>
> CMake Error at foo/CMakeLists.txt:1 (add_executable):
>   add_executable called with incorrect number of arguments

I can confirm this works with cmake version 3.9.0 on Windows 10

D:\tmp\cmake-location\build>cmake ..
-- Building for: Visual Studio 15 2017
CMake Error at foo/CMakeLists.txt:1 (add_executable):
  add_executable called with incorrect number of arguments

-- Configuring incomplete, errors occurred!
See also "D:/tmp/cmake-location/build/CMakeFiles/CMakeOutput.log".


Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CMakeLists.txt location

[Nils Gladitz]

On 13.09.2017 12:22, Alain Miniussi wrote:



On 13/09/2017 11:16, Nils Gladitz wrote:

On 13.09.2017 10:52, Alain Miniussi wrote:

Hi,

Is there a way, when printing CMake error, to get the exact location 
of the CMakeLists.txt ?


For example, right now, when I have:

CMake Error at CMakeLists.txt:14 (add_executable):

I  need to scan all my CMakeLists.txt (~200) to check which one has 
add_executable at line 14. 


CMake includes the (relative to the root source directory) path for 
me e.g.:

CMake Error at Source/CMakeLists.txt:4 (add_executable):

Well, it never did for me:
$grep add_executable CMakeLists.txt
$

Alain



Do you have a minimal reproducible example for that behaviour?


e.g. given:

   cmake_minimum_required(VERSION 2.8.0)

project(Foo NONE)

file(WRITE foo/CMakeLists.txt "add_executable()")

add_subdirectory(foo)


I get:

CMake Error at foo/CMakeLists.txt:1 (add_executable):
  add_executable called with incorrect number of arguments


Even with the oldest CMake version currently available to me (2.8.0).


Nils

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CMakeLists.txt location

[Alain Miniussi]

On 13/09/2017 11:16, Nils Gladitz wrote:

On 13.09.2017 10:52, Alain Miniussi wrote:

Hi,

Is there a way, when printing CMake error, to get the exact location 
of the CMakeLists.txt ?


For example, right now, when I have:

CMake Error at CMakeLists.txt:14 (add_executable):

I  need to scan all my CMakeLists.txt (~200) to check which one has 
add_executable at line 14. 


CMake includes the (relative to the root source directory) path for me 
e.g.:

CMake Error at Source/CMakeLists.txt:4 (add_executable):

Well, it never did for me:
$grep add_executable CMakeLists.txt
$

Alain
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] CMakeLists.txt location

[Nils Gladitz]

On 13.09.2017 10:52, Alain Miniussi wrote:

Hi,

Is there a way, when printing CMake error, to get the exact location 
of the CMakeLists.txt ?


For example, right now, when I have:

CMake Error at CMakeLists.txt:14 (add_executable):

I  need to scan all my CMakeLists.txt (~200) to check which one has 
add_executable at line 14. 


CMake includes the (relative to the root source directory) path for me e.g.:
CMake Error at Source/CMakeLists.txt:4 (add_executable):

Nils
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[CMake] CMakeLists.txt location

[Alain Miniussi]

Hi,

Is there a way, when printing CMake error, to get the exact location of 
the CMakeLists.txt ?


For example, right now, when I have:

CMake Error at CMakeLists.txt:14 (add_executable):

I  need to scan all my CMakeLists.txt (~200) to check which one has 
add_executable at line 14.


Thanks

Alain

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] debugging CMAKE_PREFIX_PATH

[Patrick Welche]

I think I am confused by the following:

1) CMAKE_PREFIX_PATH;

Problematic (scribus) CMakeLists.txt:   

   set(CMAKE_PREFIX_PATH "${QT_PREFIX}/lib/cmake")

CMakeCache.txt:

  //No help, variable specified on the command line.
  CMAKE_PREFIX_PATH:PATH=/usr/pkg/qt5

So the problem was that CMakeLists.txt overwrote the command line.
Removing the set() line made things work

2) CMAKE_MODULE_PATH

CMakeLists.txt (with extras to debug):

  set (CMAKE_MODULE_PATH 
"/usr/obj/pkgsrc/print/scribus5/work.x86_64/.buildlink/cmake-Modules" "one" 
"two" "/usr/obj/pkgsrc/print/scribus5/work.x86_64/.buildlink/cmake-Modules" 
"${CMAKE_SOURCE_DIR}/cmake/modules")
  set(testpath ${CMAKE_MODULE_PATH} CACHE PATH "testing path")

CMakeCache.txt:

  //No help, variable specified on the command line.
  
CMAKE_MODULE_PATH:PATH=/usr/obj/pkgsrc/print/scribus5/work.x86_64/.buildlink/cmake-Modules

  //testing path
  
testpath:PATH=/usr/obj/pkgsrc/print/scribus5/work.x86_64/.buildlink/cmake-Modules;one;two;/usr/obj/pkgsrc/print/scribus5/work.x86_64/.buildlink/cmake-Modules;/usr/obj/pkgsrc/print/scribus5/work.x86_64/scribus-1.5.3/cmake/modules

So here, it seems the command line overwrites CMakeLists.txt ?!

Cheers,

Patrick
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake