[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-36-ga8d42ec

[Kitware Robot via Cmake-commits]

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  a8d42ecb8dddc615e93559889994390bd10daf88 (commit)
  from  fe9a903d8ee70b62a9d598dcfebeab0ded0b2e05 (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=a8d42ecb8dddc615e93559889994390bd10daf88
commit a8d42ecb8dddc615e93559889994390bd10daf88
Author: Kitware Robot 
AuthorDate: Sat Oct 12 00:01:14 2019 -0400
Commit: Kitware Robot 
CommitDate: Sat Oct 12 00:01:14 2019 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index f7646c9..5670622 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,7 +1,7 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 16)
-set(CMake_VERSION_PATCH 20191011)
+set(CMake_VERSION_PATCH 20191012)
 #set(CMake_VERSION_RC 0)
 set(CMake_VERSION_IS_DIRTY 0)
 

---

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
https://cmake.org/mailman/listinfo/cmake-commits

Re: [CMake] target_sources vs. PUBLIC_HEADER for libraries

[Innokentiy Alaytsev]

Hello!

After some look into target installation, I've devised  the following
abomination

 
. It is ugly and not the way it should be done, but it works and only
requires some discipline at copying and pasting header files listing code.
The function expects the files that are to be installed to be listed with
BUILD_INTERFACE and INSTALL_INTERFACE generator expressions. 

I only use it for headers because I don't know how to separate file lists
into components (i.e. Dev for headers and Runtime for resource files
required at runtime). I use the following code for listing target header
files:

set (HEADERS
  # List of files here
  )

file(RELATIVE_PATH PREFIX
  ${PROJECT_SOURCE_DIR}
  ${CMAKE_CURRENT_LIST_DIR})


foreach (HEADER IN LISTS HEADERS)
  target_sources (my_target(s)
PRIVATE
$
$)
endforeach (HEADER IN HEADERS)

Hope that will somewhat help and won't hurt anyone's fillings and mind.

Best regards,
Innokentiy Alaytsev




--
Sent from: http://cmake.3232098.n2.nabble.com/
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] target_sources vs. PUBLIC_HEADER for libraries

[Alex Turbov]

Hi,

On Fri, Oct 11, 2019 at 9:33 PM Michael Ellery  wrote:

> I’d like to make sure I understand two different aspects of header files
> management for libraries:
>
> (1) typically you can add header files to target_sources, but it’s only
> helpful for IDEs..so that the IDE will show the header files in its sources
> list, correct?. In theory, cmake does not actually need header files
> explicitly specified for dependency tracking, although I guess listing them
> makes it explicit.
>

yep, correct


> (2) setting the PUBLIC_HEADER property for a target then makes header
> files available for installation via the PUBLIC_HEADER destination. Is this
> the preferred way to install the library interface/public headers? How do
> you handle a header directory hierarchy — for example maybe you have detail
> and impl subdirectories if you are following boost/stdlib conventions.
>
>
Nowadays this feature useless if you have a directory hierarchy %( So
pity...


> I found Craig’s article about target_sources very helpful (
> https://crascit.com/2016/01/31/enhanced-source-file-handling-with-target_sources/),
> but I don’t think it addresses the PUBLIC_HEADER installation use case.
>

Yep, it describes a trivial ("Hello World" level) projects.

Some time ago I've started a discussion about improvements to
`target_sources` addressed to resolve directory hierarchy install problem,
but it ends w/ no outcome... %(


> Thanks,
> Mike Ellery
> --
>
> 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:
> https://cmake.org/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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] target_sources vs. PUBLIC_HEADER for libraries

[Fred Baksik]

On Fri, Oct 11, 2019, at 3:33 PM, Michael Ellery wrote:
> I’d like to make sure I understand two different aspects of header files 
> management for libraries:
> 
> (1) typically you can add header files to target_sources, but it’s only 
> helpful for IDEs..so that the IDE will show the header files in its sources 
> list, correct?. In theory, cmake does not actually need header files 
> explicitly specified for dependency tracking, although I guess listing them 
> makes it explicit.
My experience has been that adding a header file makes sure it’s listed in the 
IDE along with the other sources. Some IDEs will determine other non-listed 
headers and list them under a different folder. But I’ve never seen listing an 
unused header file getting added as a dependency so that changing it causes the 
target to get rebuilt. I’ve always had to make sure that the header is included 
in something that gets compiled. 

—
F-- 

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] target_sources vs. PUBLIC_HEADER for libraries

[Michael Ellery]

I’d like to make sure I understand two different aspects of header files 
management for libraries:

(1) typically you can add header files to target_sources, but it’s only helpful 
for IDEs..so that the IDE will show the header files in its sources list, 
correct?. In theory, cmake does not actually need header files explicitly 
specified for dependency tracking, although I guess listing them makes it 
explicit.

(2) setting the PUBLIC_HEADER property for a target then makes header files 
available for installation via the PUBLIC_HEADER destination. Is this the 
preferred way to install the library interface/public headers? How do you 
handle a header directory hierarchy — for example maybe you have detail and 
impl subdirectories if you are following boost/stdlib conventions.

I found Craig’s article about target_sources very helpful 
(https://crascit.com/2016/01/31/enhanced-source-file-handling-with-target_sources/),
 but I don’t think it addresses the PUBLIC_HEADER installation use case.

Thanks,
Mike Ellery
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

[Kyle Edwards via CMake]

On Fri, Oct 11, 2019 at 1:36 AM Alan W. Irwin
 wrote:
> The source files that have COMPILE_OPTIONS, COMPILE_DEFINITIONS, 
> COMPILE_FLAGS, or INCLUDE_DIRECTORIES will also be skipped."

This is by far the most likely reason. We added this restriction
because we don't want files that have different COMPILE_FLAGS etc. to
be lumped together in a unity file. We decided that this was good
enough as a first past, but the way forward is to intelligently group
together files that have the same COMPILE_OPTIONS,
COMPILE_DEFINITIONS, COMPILE_FLAGS, and INCLUDE_DIRECTORIES.

Kyle
-- 

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] Error because of MSVC_RUNTIME_LIBRARY value

[Денис Смирнов]

*Here is my root CMakeLists.txt file:*
cmake_minimum_required(VERSION 3.15)

cmake_policy(SET CMP0091 NEW)
project(test_masm)

set(CMAKE_MSVC_RUNTIME_LIBRARY "MultiThreaded$<$:Debug>")

add_subdirectory(src)

*Here is the src/CMakeLists.txt file:*
enable_language(ASM_MASM)
add_executable(test_executable main.asm)

*src/main.asm is empty.*

After run cmake.exe I get error "*MSVC_RUNTIME_LIBRARY value
'MultiThreadedDebug' not known for this ASM_MASM compiler*".

*Here is the full listing:*
cmake.exe -G "Visual Studio 16 2019" -A x64 ..
-- The C compiler identification is MSVC 19.22.27905.0
-- The CXX compiler identification is MSVC 19.22.27905.0
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
Studio/2019/Community/VC/Tools/MSVC/14.22.27905/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
Studio/2019/Community/VC/Tools/MSVC/14.22.27905/bin/Hostx64/x64/cl.exe --
works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
Studio/2019/Community/VC/Tools/MSVC/14.22.27905/bin/Hostx64/x64/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
Studio/2019/Community/VC/Tools/MSVC/14.22.27905/bin/Hostx64/x64/cl.exe --
works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- The ASM_MASM compiler identification is MSVC
-- Found assembler: C:/Program Files (x86)/Microsoft Visual
Studio/2019/Community/VC/Tools/MSVC/14.22.27905/bin/Hostx64/x64/ml64.exe
-- Configuring done
CMake Error in src/CMakeLists.txt:
  MSVC_RUNTIME_LIBRARY value 'MultiThreadedDebug' not known for this
ASM_MASM
  compiler.
-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.

Can someone please tell me if I am doing something wrong or it's a bug?
-- 

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:
https://cmake.org/mailman/listinfo/cmake

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-35-gfe9a903

[Kitware Robot via Cmake-commits]

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  fe9a903d8ee70b62a9d598dcfebeab0ded0b2e05 (commit)
   via  90bb63a5ef9805519c12cc693a7c3d23b990a42c (commit)
   via  ae24597202bbcc51ebcc9e32ae1b3ee8a8a99336 (commit)
   via  ef5875b5593833ba99bc7a8afd23a1c9cd80cd3e (commit)
   via  b7509dd674d9e0a1e428c5f4ceff7b78b47ac296 (commit)
   via  3fb146cb1149ecb90404a5276c8db3cb46e00889 (commit)
   via  847e8bc98c68cdf5bc0b7935c68764c0a6d5658e (commit)
  from  696b2d40d4bdf5a8094f7d7c3e9ac66b039f34bf (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=fe9a903d8ee70b62a9d598dcfebeab0ded0b2e05
commit fe9a903d8ee70b62a9d598dcfebeab0ded0b2e05
Merge: 90bb63a b7509dd
Author: Brad King 
AuthorDate: Fri Oct 11 12:36:49 2019 +
Commit: Kitware Robot 
CommitDate: Fri Oct 11 08:36:57 2019 -0400

Merge topic 'cmake-bin-link-job-pool'

b7509dd674 Add option to configure Ninja link job pool for CMake's own 
binaries

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=90bb63a5ef9805519c12cc693a7c3d23b990a42c
commit 90bb63a5ef9805519c12cc693a7c3d23b990a42c
Merge: ae24597 ef5875b
Author: Brad King 
AuthorDate: Fri Oct 11 08:35:02 2019 -0400
Commit: Brad King 
CommitDate: Fri Oct 11 08:35:02 2019 -0400

Merge branch 'release-3.16'


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ae24597202bbcc51ebcc9e32ae1b3ee8a8a99336
commit ae24597202bbcc51ebcc9e32ae1b3ee8a8a99336
Merge: 696b2d4 3fb146c
Author: Brad King 
AuthorDate: Fri Oct 11 12:34:08 2019 +
Commit: Kitware Robot 
CommitDate: Fri Oct 11 08:34:16 2019 -0400

Merge topic 'intel-19-compile-features'

3fb146cb11 Tests: Update CompileFeatures test for Intel 19 with VS 2015
847e8bc98c Intel: Fix default C++ dialect detection on Windows

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b7509dd674d9e0a1e428c5f4ceff7b78b47ac296
commit b7509dd674d9e0a1e428c5f4ceff7b78b47ac296
Author: Brad King 
AuthorDate: Thu Oct 10 13:28:08 2019 -0400
Commit: Brad King 
CommitDate: Thu Oct 10 13:28:45 2019 -0400

Add option to configure Ninja link job pool for CMake's own binaries

Create an undocumented `CMake_JOB_POOL_LINK_BIN` option that builders
can set to avoid linking too many of our binaries at once.

diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt
index 63e08de..d89a69d 100644
--- a/Source/CMakeLists.txt
+++ b/Source/CMakeLists.txt
@@ -1193,6 +1193,11 @@ if(WIN32)
   endforeach()
 endif()
 
+if(CMake_JOB_POOL_LINK_BIN)
+  set_property(TARGET ${_tools} PROPERTY JOB_POOL_LINK "link-bin")
+  set_property(GLOBAL APPEND PROPERTY JOB_POOLS 
"link-bin=${CMake_JOB_POOL_LINK_BIN}")
+endif()
+
 # Install tools
 
 foreach(_tool ${_tools})
diff --git a/Source/CursesDialog/CMakeLists.txt 
b/Source/CursesDialog/CMakeLists.txt
index 7009717..a9e46fd 100644
--- a/Source/CursesDialog/CMakeLists.txt
+++ b/Source/CursesDialog/CMakeLists.txt
@@ -34,5 +34,9 @@ else()
   target_link_libraries(ccmake cmForm)
 endif()
 
+if(CMake_JOB_POOL_LINK_BIN)
+  set_property(TARGET ccmake PROPERTY JOB_POOL_LINK "link-bin")
+endif()
+
 CMake_OPTIONAL_COMPONENT(ccmake)
 install(TARGETS ccmake DESTINATION ${CMAKE_BIN_DIR} ${COMPONENT})
diff --git a/Source/QtDialog/CMakeLists.txt b/Source/QtDialog/CMakeLists.txt
index cb89d19..98dd0e2 100644
--- a/Source/QtDialog/CMakeLists.txt
+++ b/Source/QtDialog/CMakeLists.txt
@@ -178,6 +178,10 @@ if(WIN32)
   target_sources(cmake-gui PRIVATE $)
 endif()
 
+if(CMake_JOB_POOL_LINK_BIN)
+  set_property(TARGET cmake-gui PROPERTY JOB_POOL_LINK "link-bin")
+endif()
+
 # cmake-gui has not been updated for `include-what-you-use`.
 # Block the tool until this is done.
 set_target_properties(cmake-gui PROPERTIES

---

Summary of changes:
 Modules/CMakeCXXCompilerId.cpp.in | 16 +---
 Source/CMakeLists.txt |  5 +
 Source/CursesDialog/CMakeLists.txt|  4 
 Source/QtDialog/CMakeLists.txt|  4 
 Tests/CompileFeatures/CMakeLists.txt  |  6 ++
 Tests/CompileFeatures/default_dialect.cpp | 12 +++-
 6 files changed, 43 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-3-gef5875b

[Kitware Robot via Cmake-commits]

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  ef5875b5593833ba99bc7a8afd23a1c9cd80cd3e (commit)
   via  3fb146cb1149ecb90404a5276c8db3cb46e00889 (commit)
   via  847e8bc98c68cdf5bc0b7935c68764c0a6d5658e (commit)
  from  9150c818b7d2afb868575fcb2e0c9ba62b9d7f85 (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 -
---

Summary of changes:
 Modules/CMakeCXXCompilerId.cpp.in | 16 +---
 Tests/CompileFeatures/CMakeLists.txt  |  6 ++
 Tests/CompileFeatures/default_dialect.cpp | 12 +++-
 3 files changed, 30 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

Re: [CMake] Unity builds vs. compile_commands.json

[Brad King via CMake]

On 10/10/19 6:53 PM, Paul Smith wrote:
> Is there an intent to address this before the 3.16 release?  
> 
> Or is this a known limitation, which may or may not be addressed in
> some future version of CMake?
> 
> If the latter it should probably be added to the release notes and/or
> documentation for unity builds.

I've opened an issue for it:

* https://gitlab.kitware.com/cmake/cmake/issues/19826

This won't block the release so I've updated the documentation to
mention this limitation.

-Brad
-- 

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:
https://cmake.org/mailman/listinfo/cmake

[CMake] Linking twice for CRC32

[Vincent van Beveren]

Hello  everyone,

For integrating the CRC to an ELF I believe I will need to link twice. 
First to create a binary on which to caclulate the CRC, and using a 
second pass to actually put the CRC into a the symbol at the last part 
of the RAM. Using the pointers by Eric  Noulard I have constructed the 
following CMake code, which links the file, exports a binary BIN file 
(the actual ROM image, and then calculates the CRC into a file called 
$.crc32.


# Exprimental CRC32 support
add_library(clb_v2_dom.objs OBJECT ${F_GEN} ${F__DOM})
target_compile_definitions(clb_v2_dom.objs PUBLIC -DDOM -DCLBV2 )
add_executable(clb_v2_dom.elf $)
add_custom_command(TARGET clb_v2_dom.elf POST_BUILD
    COMMAND ${CMAKE_OBJCOPY} $ ${SECTIONS} 
-O binary $.bin
    COMMAND ${Python_EXECUTABLE} ${CMAKE_SOURCE_DIR}/tools/crc32.py 
$.bin > $.crc32

)

with linker flags defined as

# Bring up the linker
add_link_options(
    -nostartfiles
    -nodefaultlibs
    -Wl,--gc-sections
    -nostdlib
    -T ${CMAKE_SOURCE_DIR}/${P_SRC}/romram.ld
    -Wl,--defsym=CRC_VALUE=0
    -Wl,--defsym=_start=0
    )

However, the last part is to link the file again with *exactly* the same 
invocation as the original linking, except for the 
'-Wl,--defsym=CRC_VALUE=<>' instead of 0.


Can anyone give me points on how to achieve this goal?

Kind regards,
Vincent

--
National Institute for Subatomic Physics Nikhef
Department of Computer Technology
Science Park 105
1098 XG AMSTERDAM

tel.  : +31 (0)20 592 2032
e-mail: v.van.beve...@nikhef.nl
site  : http://www.nikhef.nl/~vincentb

--

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:
https://cmake.org/mailman/listinfo/cmake