[Cmake-commits] CMake branch, master, updated. v3.10.2-1042-g5656ebc

2018-02-06 Thread 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  5656ebc87cab02762d242326c6e5397393e671d7 (commit)
  from  f7c08c333b3ccd86134f73a8a3df5bf59c53bdd8 (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=5656ebc87cab02762d242326c6e5397393e671d7
commit 5656ebc87cab02762d242326c6e5397393e671d7
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Wed Feb 7 00:01:05 2018 -0500
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Wed Feb 7 00:01:05 2018 -0500

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 6c2abb5..1aa1ccc 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 11)
-set(CMake_VERSION_PATCH 20180206)
+set(CMake_VERSION_PATCH 20180207)
 #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
https://cmake.org/mailman/listinfo/cmake-commits

[CMake] Free CMake course at Kitware Headquarters March 13-15, 2018 at Kitware's Clifton Park, NY, USA

2018-02-06 Thread Bill Hoffman 
Kitware is offering a free course on VTK/ParaView/CMake March 13-15, 
2018 at Kitware's Clifton Park, NY, USA.  The signup can be found here:


https://docs.google.com/forms/d/e/1FAIpQLSeee7oTBzapITmark0dIX0E86zEyyPmh-LEbecz2zm_822WFw/viewform

Hope to meet some of you in person.

-Bill
--

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-developers] Free CMake course at Kitware Headquarters March 13-15, 2018 at Kitware's Clifton Park, NY, USA

2018-02-06 Thread Bill Hoffman 
Kitware is offering a free course on VTK/ParaView/CMake March 13-15, 
2018 at Kitware's Clifton Park, NY, USA.  The signup can be found here:


https://docs.google.com/forms/d/e/1FAIpQLSeee7oTBzapITmark0dIX0E86zEyyPmh-LEbecz2zm_822WFw/viewform

Hope to meet some of you in person.

-Bill
--

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-developers

Re: [cmake-developers] why includes the Ninja decency contents sytemheader too?

2018-02-06 Thread Brad King 
On 02/06/2018 10:03 AM, Claus Klein wrote:
> why different default behaviors in Nina and Makefile generators?

The Makefile dependency generation works totally differently and
can't do system headers well at all.  One day perhaps they should
be ported to use a depfile approach too and then a similar switch
could be added.  However, it must continue to support compilers
that don't have any depfile flags.

-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-developers

Re: [cmake-developers] why includes the Ninja decency contents sytemheader too?

2018-02-06 Thread Claus Klein 
Yes, it should be configurable via one option flag.

The cmake user can control it but it is not well documented and different to 
configure depending on compiler and generator used:

#for ninja generator:
set(CMAKE_DEPFILE_FLAGS_CXX "-MMD -MT  -MF " CACHE STRING 
"dependency flag" FORCE)

# for makefile generator:
option(CMAKE_DEPENDS_IN_PROJECT_ONLY „do NOT use system header dependencies“ ON)

###

But I am still wondering why different default behaviors in Nina and Makefile 
generators?

Claus

> Am 06.02.2018 um 13:22 schrieb Brad King :
> 
> Some people want system headers checked for $reasons, and others
> don't want them checked for $other_reasons.  The only way to satisfy
> both groups is to make it an option.
> 
> The internal `CMAKE_DEPFILE_FLAGS_${lang}` table of flags used for this
> would need to be extended with `CMAKE_DEPFILE_NOSYSTEM_FLAGS_${lang}`
> alternatives.  Some option would need to be introduced to choose.
> 
> -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-developers

Re: [cmake-developers] why includes the Ninja decency contents sytemheader too?

2018-02-06 Thread Brad King 
On 02/06/2018 03:19 AM, Claus Klein wrote:
> IMHO: This make ninja slower without much user benefit!

For reference, the change was made for CMake 3.6 here:

  
https://gitlab.kitware.com/cmake/cmake/commit/6d74e7870b8804a5af0bc395a9fbb45c1b3d26a4

The benefit is that sources recompile when system headers change
after an update to system packages.  During discussion of the
change from -MMD to -MD, it was claimed that the performance
impact was minimal:

  https://cmake.org/Bug/view.php?id=14914#c40684

Maybe that's true in some environments but not others.

> On Thu, Nov 30, 2017 at 12:09:55 -0800, Evan Martin wrote:
>> That CMake change is interesting.  While it's true that it is more correct
>> to check the state of the system headers, it's also true that to be fully
>> correct here you need a completely hermetic build.  If CMake doesn't also
>> check the compiler binary as well as any shared libraries that the compiler
>> binary uses, then I think using this extra flag only serves to make ninja
>> slower without much user benefit.

Robustness to some system updates is still valuable even without
being robust to all system updates.

Some people want system headers checked for $reasons, and others
don't want them checked for $other_reasons.  The only way to satisfy
both groups is to make it an option.

The internal `CMAKE_DEPFILE_FLAGS_${lang}` table of flags used for this
would need to be extended with `CMAKE_DEPFILE_NOSYSTEM_FLAGS_${lang}`
alternatives.  Some option would need to be introduced to choose.

-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-developers

Re: [CMake] Removing Transitively Inherited Properties

2018-02-06 Thread Sergei Nikulov 
2018-02-06 13:15 GMT+03:00 Geogin Varghese :
> What is the recommended way of removing transitively inherited
> attributes for a target.
>
> Example:
> target_link_libraries(A PRIVATE B)
> target_compile_options(B PUBLIC -Werror)
>

Shouldn't it be PRIVATE for B?
E.g.  target_compile_options(B PRIVATE -Werror)

https://cmake.org/cmake/help/v3.0/manual/cmake-buildsystem.7.html#build-specification-and-usage-requirements

"
Each of the commands has a PRIVATE, PUBLIC and INTERFACE mode. The
PRIVATE mode populates only the non-INTERFACE_ variant of the target
property and the INTERFACE mode populates only the INTERFACE_
variants. The PUBLIC mode populates both variants of the respective
target property.
"


> How should the -Werror option be removed from target A.
> --
>
> 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



-- 
Best Regards,
Sergei Nikulov
-- 

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] Removing Transitively Inherited Properties

2018-02-06 Thread Jean-Michaël Celerier 
For stuff like this one you could add -Wno-error afterwards to A's
compile_options.



---
Jean-Michaël Celerier
http://www.jcelerier.name

On Tue, Feb 6, 2018 at 11:15 AM, Geogin Varghese  wrote:

> What is the recommended way of removing transitively inherited
> attributes for a target.
>
> Example:
> target_link_libraries(A PRIVATE B)
> target_compile_options(B PUBLIC -Werror)
>
> How should the -Werror option be removed from target A.
> --
>
> 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

[CMake] Removing Transitively Inherited Properties

2018-02-06 Thread Geogin Varghese 
What is the recommended way of removing transitively inherited
attributes for a target.

Example:
target_link_libraries(A PRIVATE B)
target_compile_options(B PUBLIC -Werror)

How should the -Werror option be removed from target A.
-- 

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-developers] why includes the Ninja decency contents sytemheader too?

2018-02-06 Thread Claus Klein 
I’m wondering about the different dependency strategies between ‚Unix Makefiles’ and Nina generator.IMHO: This make ninja slower without much user benefit!-Clausfind . -name depend.make | xargs cat# CMAKE generated file: DO NOT EDIT!# Generated by "Unix Makefiles" Generator, CMake Version 3.10CMakeFiles/BindToDevice.dir/BindToDevice.c.o: ../BindToDevice.c# CMAKE generated file: DO NOT EDIT!# Generated by "Unix Makefiles" Generator, CMake Version 3.10CMakeFiles/InnerClassIdiom.dir/InnerClassIdiom.cpp.o: ../InnerClassIdiom.cpp# CMAKE generated file: DO NOT EDIT!# Generated by "Unix Makefiles" Generator, CMake Version 3.10CMakeFiles/testFileAppend.dir/tests/testFileAppend.c.o: ../tests/testFileAppend.c#Claus-MBP:build clausklein$ ninja -t depsCMakeFiles/testFileAppend.dir/tests/testFileAppend.c.o: #deps 98, deps mtime 1517904010 (VALID)    ../tests/testFileAppend.c    /usr/include/sys/stat.h    /usr/include/sys/_types.h    /usr/include/sys/cdefs.h    /usr/include/sys/_symbol_aliasing.h    /usr/include/sys/_posix_availability.h    /usr/include/machine/_types.h    /usr/include/i386/_types.h    /usr/include/sys/_pthread/_pthread_types.h    /usr/include/Availability.h    /usr/include/AvailabilityInternal.h# ….quote from ninja list:On Thu, Nov 30, 2017 at 12:09:55 -0800, Evan Martin wrote:That CMake change is interesting.  While it's true that it is more correctto check the state of the system headers, it's also true that to be fullycorrect here you need a completely hermetic build.  If CMake doesn't alsocheck the compiler binary as well as any shared libraries that the compilerbinary uses, then I think using this extra flag only serves to make ninjaslower without much user benefit.The mentioned issue is here:   https://cmake.org/Bug/view.php?id=14914It was done for feature parity with the Makefiles generators. They useCMake's scanning logic rather than exact dependencies like Ninja (forvarious reasons).--Ben

dependencies.log
Description: Binary data

-- 

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-developers