> -Original Message-
> From: Ben Boeckel [mailto:ben.boec...@kitware.com]
> Sent: Friday, August 04, 2017 12:55 PM
> To: Puetz Kevin A <puetzkev...@johndeere.com>
> Cc: cmake@cmake.org; Robert Maynard <robert.mayn...@kitware.com>
> Subject: Re: CMake 3.9 ch
> -Original Message-
> From: Robert Maynard [mailto:robert.mayn...@kitware.com]
> Sent: Friday, August 04, 2017 1:03 PM
> To: Ben Boeckel <ben.boec...@kitware.com>
> Cc: Puetz Kevin A <puetzkev...@johndeere.com>; cmake@cmake.org
> Subject: Re: CMake 3.9 ch
Thanks for the reply, questions/clarifications below.
> -Original Message-
> From: Ben Boeckel [mailto:ben.boec...@kitware.com]
> Sent: Thursday, August 03, 2017 10:59 AM
> To: cmake@cmake.org
> Cc: Robert Maynard <robert.mayn...@kitware.com>; Puetz Kevin A
> &l
I saw the following in the CMake 3.9 release notes, but didn't immediately
realize all the implications. Sorry for not catching this during the -rc
phase...
. The Ninja generator has loosened the dependencies of object compilation.
Object compilation now depends only on custom targets and
I often hit this, particularly with header-only INTERFACE libraries where I
just want to pick up their defines/include paths, and then CMake ends up
treating the target_link_libraries(PRIVATE as public anyway). So it would
definitely be helpful to have a warning that this doesn’t do what you’d
