[CMake] Development Workflow with CMake and VS2017

[R0b0t1]

Hello list,

I apologize if this is slightly offtopic, but I have not yet found a
good way to manage dependencies on Windows. On Linux the dependencies
can be installed system wide, but on Windows this is typically not the
case.

I did see some CMake scripts that would download and install things
recursively, but I am not sure (badly) recreating a package manager is
a good idea. But is it the best way for now? What alternatives are
there?

As a usecase, imagine I just want to make a simple program that uses
e.g. FreeType2. I would also like to know of options where there is
either not a CMake build script, or when the library must be compiled
with MinGW.

It seems to me I should just stick to Cygwin or MSYS2.

Cheers,
R0b0t1
-- 

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] Development Workflow with CMake and VS2017

[Innokentiy Alaytsev]

Hello!

I usually just download prebuild binaries if they are available or build the
required dependency from sources. There are some libraries (and other
software) that are not Windows-friendly (These products are still considered
cross-platform and usually are free in the way fanatics from FSF understand
freedom, i.e. freedom is the thing that should be enforced). In the case
where it is impossible or hard to build something on Windows with MSVC, I
try to find some alternative.

The reason for trying to build everything with MSVC is simple -
unfortunately, it is the official compiler for the platform and some things
can only be built with it for Windows.

Sticking to Cygwin or MSYS2 may be fine unless you need some things like Qt
with WebEngine support or, probably, CUDA (I am not sure if it officially
works with anything else but MSVC).



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

[CMake] Boost + CMake + Windows + Sanity -> Possible?

[Wheeler, Gavin]

Hello! First the short version...

Can anyone give me a set of instructions to download, build and setup the 
latest Boost (currently 1.67) on Windows 10 for VS 2017 64bit such that the 
following will work...

find_package(Boost REQUIRED COMPONENTS system filesystem thread date_time 
iostreams)
include_directories(${Boost_INCLUDE_DIRS})
link_directories(${Boost_LIBRARY_DIRS})

Including...

- Steps to follow when building and installing Boost
- What environment variables to set and what to set them to, e.g. boost, boost 
library, boost include directories
- What to set in the CMake file so that Boost will be correctly included

I ask about building Boost as well as CMake because it seems to me that unless 
Boost is built in a way that matches CMake expectations it just won't work.

Some background...

I've inherited a project with the above in, along with depndencies on ITK, VTK 
and zlib - all of which I have set up in CMake OK. However, Boost appears to be 
immune to working with CMake. There are various suggestions on the web, but 
nothing consistent, and nothing I've found whcih will work.

I've spent 2 days building Boost (this isn't solely due to CMake, the Boost 
build instructions are all over the place and their latest installer contains a 
trojan according to Windows defender) and configuring CMake in various ways, 
getting frustrated setting various environmental variables, and the nebulous 
target that is a Boost source install.

I can fix this by manually setting all of the library paths and doing some 
fixing up in the resultant project files, but I shouldn't really have to.

Surely it shouldn't be this difficult! Hopefully if there is a clear set of 
instructions from start to finish it will save others future anguish.

For building Boost I ended up using b2 and the following steps install (based 
on https://www.boost.org/doc/libs/1_67_0/more/getting_started/windows.html) and 
having tried following the instructions to the letter I ended up with...

- Download Boost, e.g. from 
https://dl.bintray.com/boostorg/release/1.67.0/source/boost_1_67_0.7z
- Extract to e.g. C:\thirdparty\boost\boost_1_67_0
- Build the bootstrapper, as per section 5.2.1 in 
https://www.boost.org/doc/libs/1_67_0/more/getting_started/windows.html
- Build the binaries, simlar to section 5.2.2 in the above, but using
- b2 --build-dir=C:\thirdparty\boost-install\boost_1_67_0 toolset=msvc 
--build-type=complete install
- Why the change?
- Building the Boost build tools didn't seem to affect the building of the 
install
- The inital install command in their instructions didn't seem to actually 
install the headers and libs
- Using stage only seems to collect the lib files together, not the headers
- So I end up with a libs folder and an include folder

I then try to set the following environment variables (as system ones, rather 
than as user ones)

- BOOST_ROOT - to the boost folder of the downloaded and extracted boost
- BOOST_INCLUDEDIR - to the include folder of the installed boost
- BOOST_LIBRARYDIR - the the lib folder of the installed boost

As well as lots of other directories which seemed like they might work.

Then in the CMake (based upon suggestions from the web) I've tried things 
like...

set(Boost_USE_STATIC_LIBSON)
set(Boost_USE_MULTITHREADED  ON)
set(Boost_USE_STATIC_RUNTIMEOFF)

...and...

SET(Boost_ADDITIONAL_VERSIONS "1.67" "1.67.0")

...and...

set (Boost_DETAILED_FAILURE_MSG ON)
set (BOOST_DEBUG ON)

... to no avail






-- 

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] Concurrency issues with copy_if_different

[Robert Maynard]

Personally would go with option number 2

On Thu, Jul 12, 2018 at 1:58 AM Olivier Croquette 
wrote:

> Hello,
>
> in one of our projects, we use copy_if_different to copy some DLLs
> required by the runtime. It's called as post-build action. The problem
> is that several targets want to copy the same DLLs, and when using
> parallelized builds, the different "cmake -E copy_if_different" can
> conflict, leading the whole build to fail.
>
> I see two options to fix this:
>
> 1. don't use copy_if_different, but a custom tool that can deal with the
> concurrency
>
> 2. instead of adding post-build actions to different targets, fill up a
> list containing all the files required, and add a single post-build
> action to a single target that copies all the required files in one go
>
> What do you think?
>
> Cheers
> Olivier
>
>
> --
>
> 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] Concurrency issues with copy_if_different

[J. Caleb Wherry]

Had the same problem and went with #2

-Caleb

On Thu, Jul 12, 2018 at 1:58 AM Olivier Croquette 
wrote:

> Hello,
>
> in one of our projects, we use copy_if_different to copy some DLLs
> required by the runtime. It's called as post-build action. The problem
> is that several targets want to copy the same DLLs, and when using
> parallelized builds, the different "cmake -E copy_if_different" can
> conflict, leading the whole build to fail.
>
> I see two options to fix this:
>
> 1. don't use copy_if_different, but a custom tool that can deal with the
> concurrency
>
> 2. instead of adding post-build actions to different targets, fill up a
> list containing all the files required, and add a single post-build
> action to a single target that copies all the required files in one go
>
> What do you think?
>
> Cheers
> Olivier
>
>
> --
>
> 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
>
-- 
Sent from my iPhone 4s
-- 

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] FindMPI and version

[Clune, Thomas L. (GSFC-6101)]

It appears that MPI__VERSION is returning the version of the MPI 
_standard_ that is supported by the chosen MPI.   While I am sure this is 
useful in some contexts, it’s actually not what I want/need for my project and 
it is quite inconsistent with analogous versions such as 
CMAKE__COMPILER_VERSION.   E.g., CMAKE_Fortran_COMPILER_VERSION returns 
something like 18.0.3.x for my current Intel compiler whereas the Fortran 
language standard that it nominally supports is 2008.

Our project has dependencies on external libraries that in turn have 
dependencies on MPI.   We would like to ensure that we choose the external 
library that was compiled with  the same vendor version of MPI used in our 
project.In theory such information can be derived from 
MPI__LIBRARY_VERSION,   but it is nontrivial and some conventions need to 
be established.The proper home for such logic is FindMPI.cmake.

I would not think that we are the only project facing this frustration, but 
given that MPI__LIBRARY_VERSION is only in the very latest release of 
cmake, others must have found other means to compensate for this?





-- 

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] Boost + CMake + Windows + Sanity -> Possible?

[Innokentiy Alaytsev]

Hello!

First of all, I suggest you use Boost imported targets instead of
Boost_INCLUDE_DIRS and Boost_LIBRARY_DIRS and the
target_include_directories() and target_link_libraries() functions. Al this
is to better support exporting CMake package if you need it. If you do not
produce CMake package for use in some other projects, then just ignore this
advice.

Second, just use  pre-built Boost binaries
  . They are just
fine. If your Windows Defender finds something in them then it's the problem
in Windows Defender.

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

[Cmake-commits] CMake branch, master, updated. v3.12.0-rc3-203-g4d9d674

[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  4d9d674cf26be9a8bbfa59927f8540b88607bb91 (commit)
  from  bfb025f04b3522ff0fee650e7c4c4fe808d739b3 (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=4d9d674cf26be9a8bbfa59927f8540b88607bb91
commit 4d9d674cf26be9a8bbfa59927f8540b88607bb91
Author: Kitware Robot 
AuthorDate: Fri Jul 13 00:01:06 2018 -0400
Commit: Kitware Robot 
CommitDate: Fri Jul 13 00:01:06 2018 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 9086fb2..9eb3ade 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 12)
-set(CMake_VERSION_PATCH 20180712)
+set(CMake_VERSION_PATCH 20180713)
 #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-commits] CMake branch, master, updated. v3.12.0-rc3-190-g7b04ad6

[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  7b04ad61cf925161c8b7f9abf6ef3db047118807 (commit)
   via  f8a7cf85ad7ff9ed01987d5845dad46c395ac4fa (commit)
  from  05cd8311ab52cf1e1ca40701c092602fe51cfbe4 (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=7b04ad61cf925161c8b7f9abf6ef3db047118807
commit 7b04ad61cf925161c8b7f9abf6ef3db047118807
Merge: 05cd831 f8a7cf8
Author: Brad King 
AuthorDate: Thu Jul 12 13:12:15 2018 +
Commit: Kitware Robot 
CommitDate: Thu Jul 12 09:12:26 2018 -0400

Merge topic 'option_respects_existing_stack_variable'

f8a7cf85ad option: No CMP077 warnings when both cache and local variable 
exists

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f8a7cf85ad7ff9ed01987d5845dad46c395ac4fa
commit f8a7cf85ad7ff9ed01987d5845dad46c395ac4fa
Author: Robert Maynard 
AuthorDate: Tue Jul 10 13:56:15 2018 -0400
Commit: Robert Maynard 
CommitDate: Tue Jul 10 13:56:15 2018 -0400

option: No CMP077 warnings when both cache and local variable exists

Previously we would warn when the local and cache version of a variable
exists, but this use case doesn't need a warning as it maintains backwards
compatibility.

diff --git a/Source/cmOptionCommand.cxx b/Source/cmOptionCommand.cxx
index 4ab0e96..239cd00 100644
--- a/Source/cmOptionCommand.cxx
+++ b/Source/cmOptionCommand.cxx
@@ -28,32 +28,28 @@ bool cmOptionCommand::InitialPass(std::vector 
const& args,
   }
 
   // Determine the state of the option policy
-  auto status = this->Makefile->GetPolicyStatus(cmPolicies::CMP0077);
-  const char* exists =
-this->Makefile->GetStateSnapshot().GetDefinition(args[0]);
-  switch (status) {
-case cmPolicies::WARN:
-  if (exists) {
-std::ostringstream w;
-w << cmPolicies::GetPolicyWarning(cmPolicies::CMP0077)
-  << "\n"
- "For compatibility with older versions of CMake, option "
- "is clearing the normal variable '"
-  << args[0] << "'.";
-this->Makefile->IssueMessage(cmake::AUTHOR_WARNING, w.str());
-  }
-case cmPolicies::OLD:
-  // OLD behavior does not warn.
-  break;
-case cmPolicies::REQUIRED_ALWAYS:
-case cmPolicies::REQUIRED_IF_USED:
-case cmPolicies::NEW: {
-  // See if a local variable with this name already exists.
-  // If so we ignore the option command.
-  if (exists) {
-return true;
-  }
-} break;
+  bool checkAndWarn = false;
+  {
+auto status = this->Makefile->GetPolicyStatus(cmPolicies::CMP0077);
+const char* existsBeforeSet =
+  this->Makefile->GetStateSnapshot().GetDefinition(args[0]);
+switch (status) {
+  case cmPolicies::WARN:
+checkAndWarn = (existsBeforeSet != nullptr);
+break;
+  case cmPolicies::OLD:
+// OLD behavior does not warn.
+break;
+  case cmPolicies::REQUIRED_ALWAYS:
+  case cmPolicies::REQUIRED_IF_USED:
+  case cmPolicies::NEW: {
+// See if a local variable with this name already exists.
+// If so we ignore the option command.
+if (existsBeforeSet) {
+  return true;
+}
+  } break;
+}
   }
 
   // See if a cache variable with this name already exists
@@ -74,5 +70,19 @@ bool cmOptionCommand::InitialPass(std::vector 
const& args,
   bool init = cmSystemTools::IsOn(initialValue.c_str());
   this->Makefile->AddCacheDefinition(args[0], init ? "ON" : "OFF",
  args[1].c_str(), cmStateEnums::BOOL);
+
+  if (checkAndWarn) {
+const char* existsAfterSet =
+  this->Makefile->GetStateSnapshot().GetDefinition(args[0]);
+if (!existsAfterSet) {
+  std::ostringstream w;
+  w << cmPolicies::GetPolicyWarning(cmPolicies::CMP0077)
+<< "\n"
+   "For compatibility with older versions of CMake, option "
+   "is clearing the normal variable '"
+<< args[0] << "'.";
+  this->Makefile->IssueMessage(cmake::AUTHOR_WARNING, w.str());
+}
+  }
   return true;
 }
diff --git a/Tests/RunCMake/option/CMP0077-SECOND-PASS.cmake 
b/Tests/RunCMake/option/CMP0077-SECOND-PASS.cmake
new file mode 100644
index 000..f62a853
--- /dev/null
+++ b/Tests/RunCMake/option/CMP0077-SECOND-PASS.cmake
@@ -0,0 +1,14 @@
+
+#Verify that when both a cache and local version of a value exist that CMake
+#doesn't produce a CMP0077 warning and that we get the expected values.
+option(OPT_LOCAL_VAR "TEST_VAR" ON)
+set(OPT_LOCAL_VAR FALSE)
+option(OPT_LOCAL_VAR "TEST_VAR" ON)

[Cmake-commits] CMake branch, master, updated. v3.12.0-rc3-200-gf7f2b80

[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  f7f2b8078e6181f0f3c476c55d7cab3d86ffdaae (commit)
   via  f6f5f9f75f809a077ac3f451745904d9f3faaa85 (commit)
   via  e014df762b41e61b423e56637667a050be3a78e7 (commit)
   via  ce4f20ba62a3c7e0dd78cffc1669a400311f057e (commit)
   via  281c601024e7a82f85ef02ce00a0fc5686c5412d (commit)
   via  01c98c65a4d5c9faaf524da92590492e9976 (commit)
   via  bb77dc0cee95b2606ab6715aa9babc89c09d176f (commit)
   via  f80692cf600675bae4d12810c8119a62e76aa701 (commit)
   via  a37a4a00c8b8982c89ffc99505de097d3b2d7300 (commit)
   via  5d40d2b44fe93e223bd7802797b4cd430656790e (commit)
  from  7b04ad61cf925161c8b7f9abf6ef3db047118807 (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=f7f2b8078e6181f0f3c476c55d7cab3d86ffdaae
commit f7f2b8078e6181f0f3c476c55d7cab3d86ffdaae
Merge: f6f5f9f e014df7
Author: Brad King 
AuthorDate: Thu Jul 12 13:15:15 2018 +
Commit: Kitware Robot 
CommitDate: Thu Jul 12 09:15:58 2018 -0400

Merge topic 'qnx_fix'

e014df762b QNX: Fix autogen compiler predefines detection

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f6f5f9f75f809a077ac3f451745904d9f3faaa85
commit f6f5f9f75f809a077ac3f451745904d9f3faaa85
Merge: 7b04ad6 ce4f20b
Author: Brad King 
AuthorDate: Thu Jul 12 13:14:58 2018 +
Commit: Kitware Robot 
CommitDate: Thu Jul 12 09:15:18 2018 -0400

Merge topic 'ghs'

ce4f20ba62 GHS: Add release notes
281c601024 GHS: Update default BSP name
01c98c6ccc GHS: Update setting default OS location for Integrity platforms
bb77dc0cee GHS: Set primary target using arch/platform values (or user 
specified value)
f80692cf60 GHS: Add platform selection support
a37a4a00c8 GHS: Add toolset selection support
5d40d2b44f GHS: Support ARM, PPC, 86 architectures

Acked-by: Kitware Robot 
Acked-by: Matt Soucy 
Merge-request: !798


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e014df762b41e61b423e56637667a050be3a78e7
commit e014df762b41e61b423e56637667a050be3a78e7
Author: Cristian Adam 
AuthorDate: Wed Jul 11 15:45:40 2018 +0200
Commit: Brad King 
CommitDate: Wed Jul 11 09:54:49 2018 -0400

QNX: Fix autogen compiler predefines detection

In commit v3.12.0-rc1~20^2 (Move GNU COMPILER_PREDEFINES_COMMAND from
Platform to Compiler, 2018-06-01), `Compiler/GNU.cmake` introduced the
`-dM` flag, which requires `-Wp` prefix for the QNX compiler wrapper.

diff --git a/Modules/Compiler/QCC.cmake b/Modules/Compiler/QCC.cmake
index 0da7050..a5e2b0b 100644
--- a/Modules/Compiler/QCC.cmake
+++ b/Modules/Compiler/QCC.cmake
@@ -16,6 +16,8 @@ macro(__compiler_qcc lang)
   set(_CMAKE_${lang}_IPO_SUPPORTED_BY_CMAKE NO)
   set(_CMAKE_${lang}_IPO_MAY_BE_SUPPORTED_BY_COMPILER NO)
 
+  set(CMAKE_${lang}_COMPILER_PREDEFINES_COMMAND "${CMAKE_${lang}_COMPILER}" 
"-Wp,-dM" "-E" "-c" "${CMAKE_ROOT}/Modules/CMakeCXXCompilerABI.cpp")
+
   unset(CMAKE_${lang}_COMPILE_OPTIONS_IPO)
   unset(CMAKE_${lang}_ARCHIVE_CREATE_IPO)
   unset(CMAKE_${lang}_ARCHIVE_APPEND_IPO)

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ce4f20ba62a3c7e0dd78cffc1669a400311f057e
commit ce4f20ba62a3c7e0dd78cffc1669a400311f057e
Author: Fred Baksik 
AuthorDate: Sat Jul 7 07:27:22 2018 -0400
Commit: Fred Baksik 
CommitDate: Wed Jul 11 08:48:25 2018 -0400

GHS: Add release notes

diff --git a/Help/release/dev/ghs.rst b/Help/release/dev/ghs.rst
new file mode 100644
index 000..d3bec95
--- /dev/null
+++ b/Help/release/dev/ghs.rst
@@ -0,0 +1,20 @@
+ghs
+---
+
+* The :generator:`Green Hills MULTI` generator is updated:
+
+  - Added support for architecture selection through
+:variable:`CMAKE_GENERATOR_PLATFORM`:
+e.g. ``arm``, ``ppc``, and ``86``.
+
+  - Added support for toolset selection through
+:variable:`CMAKE_GENERATOR_TOOLSET`,
+e.g. ``comp_201205``, ``comp_201510``, ``comp_201722_beta``.
+
+  - Added support for platform selection through ``GHS_TARGET_PLATFORM``,
+e.g. ``integrity``, ``linux``, ``standalone``, etc.
+
+  - No longer checks that ``arm`` based compilers are installed but ensures
+that the correct ``gbuild.exe`` exists.
+
+  - No longer hard-codes ARM files, BSP, toolset, or OS locations.

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=281c601024e7a82f85ef02ce00a0fc5686c5412d
commit 281c601024e7a82f85ef02ce00a0fc5686c5412d
Author: Fred Baksik 
AuthorDate: Sat Jul 7 07:27:22 2018 -0400
Commit: Fred Baksik 
CommitDate: Wed Jul 11 08:48:23 2018 

[Cmake-commits] CMake branch, release, updated. v3.12.0-rc3-4-g730c8b8

[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, release has been updated
   via  730c8b87275ca9a95f90cea745532f49d6fdd05d (commit)
   via  e014df762b41e61b423e56637667a050be3a78e7 (commit)
  from  f974000d93798af1e3bd183985ec6f5159664f76 (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/Compiler/QCC.cmake | 2 ++
 1 file changed, 2 insertions(+)


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

[Cmake-commits] CMake branch, master, updated. v3.12.0-rc3-202-gbfb025f

[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  bfb025f04b3522ff0fee650e7c4c4fe808d739b3 (commit)
   via  730c8b87275ca9a95f90cea745532f49d6fdd05d (commit)
  from  f7f2b8078e6181f0f3c476c55d7cab3d86ffdaae (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=bfb025f04b3522ff0fee650e7c4c4fe808d739b3
commit bfb025f04b3522ff0fee650e7c4c4fe808d739b3
Merge: f7f2b80 730c8b8
Author: Brad King 
AuthorDate: Thu Jul 12 09:37:36 2018 -0400
Commit: Brad King 
CommitDate: Thu Jul 12 09:37:36 2018 -0400

Merge branch 'release-3.12'


---

Summary of changes:


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