[Cmake-commits] CMake branch, master, updated. v3.13.3-891-g2033c1e

2019-01-14 Thread 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  2033c1e56fd3d9367fc4eb9a2595c3c592575d54 (commit)
  from  4541c914b587125048c8e82bc3cd687f573f753a (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=2033c1e56fd3d9367fc4eb9a2595c3c592575d54
commit 2033c1e56fd3d9367fc4eb9a2595c3c592575d54
Author: Kitware Robot 
AuthorDate: Tue Jan 15 00:01:05 2019 -0500
Commit: Kitware Robot 
CommitDate: Tue Jan 15 00:01:05 2019 -0500

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 4a4f63f..7ae4417 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 13)
-set(CMake_VERSION_PATCH 20190114)
+set(CMake_VERSION_PATCH 20190115)
 #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-developers] [ANNOUNCE] CMake 3.13.3 available for download

2019-01-14 Thread Robert Maynard via cmake-developers 
We are pleased to announce that CMake 3.13.3 is now available for download.

Please use the latest release from our download page:
  https://cmake.org/download/

Thanks for your support!

* The VS 2017 generator has been fixed to work when VS 2019 is installed.

-
Changes in 3.13.3 since 3.13.2:

Brad King (4):
  VS: Exclude VS 2019 instances when using VS 2017 generator
  Tests: Add cases for -{C,D,U} without a source tree
  Tests: Add case for warning when AUTOMOC/UIC/RCC gets disabled
  CMake 3.13.3

Craig Scott (2):
  cmake: Stop processing if -P option lacks file name
  cmake: Ensure source and binary dirs are set

Paul Seyfert (1):
  cmake: distinguish '-Cpath' from '-C path' in source dir parsing

Sebastian Holtermann (1):
  Autogen: Issue a warning when AUTOMOC/UIC/RCC gets disabled.

Tim Blechmann (1):
  BundleUtilities: Ensure target dir exists when creating symlinks
-- 

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

[CMake] [ANNOUNCE] CMake 3.13.3 available for download

2019-01-14 Thread Robert Maynard via CMake 
We are pleased to announce that CMake 3.13.3 is now available for download.

Please use the latest release from our download page:
  https://cmake.org/download/

Thanks for your support!

* The VS 2017 generator has been fixed to work when VS 2019 is installed.

-
Changes in 3.13.3 since 3.13.2:

Brad King (4):
  VS: Exclude VS 2019 instances when using VS 2017 generator
  Tests: Add cases for -{C,D,U} without a source tree
  Tests: Add case for warning when AUTOMOC/UIC/RCC gets disabled
  CMake 3.13.3

Craig Scott (2):
  cmake: Stop processing if -P option lacks file name
  cmake: Ensure source and binary dirs are set

Paul Seyfert (1):
  cmake: distinguish '-Cpath' from '-C path' in source dir parsing

Sebastian Holtermann (1):
  Autogen: Issue a warning when AUTOMOC/UIC/RCC gets disabled.

Tim Blechmann (1):
  BundleUtilities: Ensure target dir exists when creating symlinks
-- 

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] How to correctly default initialize CMAKE_BUILD_TYPE inside CMakeLists.txt

2019-01-14 Thread frodak17 
On Mon, Jan 14, 2019 at 1:09 PM Kim Walisch  wrote:

> Based on feedback from Craig Scott I now use the following code:
>
> if(CMAKE_VERSION VERSION_GREATER_EQUAL 3.9)
>  get_property(isMultiConfig GLOBAL PROPERTY
> GENERATOR_IS_MULTI_CONFIG)
> elseif(CMAKE_CONFIGURATION_TYPES)
>  set(isMultiConfig TRUE)
> endif()
>
> if(NOT isMultiConfig AND NOT CMAKE_BUILD_TYPE)
> set(CMAKE_BUILD_TYPE Release CACHE STRING
> "Choose the type of build, options are: None Debug Release
> RelWithDebInfo MinSizeRel." FORCE)
> endif()
>
> This code sets CMAKE_BUILD_TYPE only for single configuration generators
> (like GNU make or Ninja) because multi configuration generators (like Xcode
> or Visual Studio) generally ignore CMAKE_BUILD_TYPE. For an in depth
> explanation please refer to chapter 13 of Scott's excellent "Professional
> CMake" book (https://crascit.com/professional-cmake).
>
> Regards,
> Kim
>
>
There is nothing particularly wrong with setting CMAKE_BUILD_TYPE to
Release in a CMakeLists.txt except that then you can't use the default
settings of when it is not set.

In general a CMakeLists.txt that supports Multi-configuration generators
will use the generator expressions to determine the configuration type.  In
those cases CMAKE_BUILD_TYPE is not used and doesn't show up in any script.

Other scripts may check if CMAKE_BUILD_TYPE is set to enable additional
flags or add in special files and those scripts won't usually work as
expected with a multi-configuration generator because Debug / Release can
be chosen at build time.

If you have to work around something that is going to break because it
expects CMAKE_BUILD_TYPE to never be set then it won't work for single
configuration generators when the user sets CMAKE_BUILD_TYPE to Release.

Both types of generators are available for use when working with clang on
windows.

You never mentioned what part didn't work or what generator you are using,
but if only setting CMAKE_BUILD_TYPE when a single configuration generator
is used gets you past the problem then that works too.

Regards,
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] INVOICE P109342

2019-01-14 Thread Julien Jomier via CMake 
Hi,


Attached to this e-mail is your new invoice
Please make a Bank Transfer for $1,732.00 to:
Account Name: Julien Jomier
Account Number: 3624775
Sort Code: 55-790-49
Please note that as explained on our website no orders paid for by Bank 
Transfer can be dispatched until cleared funds have been received.

I have enclosed a copy of the invoice for your reference, you can download \/ 
view using this link:

   http://www.prom-engineering.com/Clients_information/01_19



Thank you for your valued custom.

-

Julien Jomier
Phone (Business): 
961 846-8847
Phone (FAX): 
961 846-8621
Email ID:julien.jom...@kitware.com



This email transmission is intended only for the use of the individual or 
entity named above and may contain information 
that is confidential, privileged, and exempt from disclosure under applicable 
law.
If you are not the intended recipient, you are hereby notified that any 
disclosure, copying, distribution, or use of any of the
information contained in this transmission is strictly prohibited. All email 
and attachments are scanned for viruses before
transmission. However, I recommend that you perform such scans as are necessary 
before opening any attachments, as we
accept no liability any loss or damage caused in the process of communication. 
All quotations and recommendations in any
proposal, report, e-mail or letter are made in good faith and on the basis of 
the information before us at the time.
In consequence, no statement in any proposal, report e-mail or letter is to be 
deemed in any circumstances a representation,
undertaking, warranty or contractual condition. If you have received this 
transmission in error, please notify me by email at 
the above address. Thank you.
-- 

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] How to correctly default initialize CMAKE_BUILD_TYPE inside CMakeLists.txt

2019-01-14 Thread frodak17 
On Mon, Jan 14, 2019 at 3:48 AM Kim Walisch  wrote:

> Hi,
>
> By default I would like to set CMAKE_BUILD_TYPE=Release (inside
> CMakeLists.txt) if the user has not defined CMAKE_BUILD_TYPE himself (e.g.
> as command-line option: cmake . -DCMAKE_BUILD_TYPE=Debug). Is there a best
> practice how to do this in CMake? I have been searching the web to see how
> other people achieved this and I found that many people use code like this:
>
> if(NOT CMAKE_BUILD_TYPE)
> set(CMAKE_BUILD_TYPE "Release" CACHE STRING
> "Choose the type of build, options are: None Debug Release
> RelWithDebInfo MinSizeRel."
> FORCE)
> endif()
>
> I used this code myself in one of my projects but I recently discovered
> that this code causes issues when compiling with clang-cl on Windows.
>
> Greetings,
> Kim
>
>
Which part of that causes the problem?  It sounds like there is an issue
with Release mode flags.
Wouldn't you just have the same problem if "cmake
-DCMAKE_BUILD_TYPE=Release" was used on the command line?
I guess maybe it could be a problem if it wasn't one of the first things
done and it changed mid-processing.
-- 

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.13.3-888-g9e03a63

2019-01-14 Thread 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  9e03a63ba8b6b01ffbf5c0ee207c8c0bf040f494 (commit)
   via  e91f1616d92120bd364437fc915634d48d653512 (commit)
   via  beb991110d84e9c0a6b1339e22fa98284b08bac9 (commit)
   via  c834c47dfc8006fbdf95a22ea4241b53d7235915 (commit)
  from  3e763d506cda64d76c40d327371925e9df7cbca8 (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=9e03a63ba8b6b01ffbf5c0ee207c8c0bf040f494
commit 9e03a63ba8b6b01ffbf5c0ee207c8c0bf040f494
Merge: e91f161 beb9911
Author: Brad King 
AuthorDate: Mon Jan 14 14:15:04 2019 +
Commit: Kitware Robot 
CommitDate: Mon Jan 14 09:15:10 2019 -0500

Merge topic 'drop-IRIX'

beb991110d Remove now-unused code once used on IRIX

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e91f1616d92120bd364437fc915634d48d653512
commit e91f1616d92120bd364437fc915634d48d653512
Merge: 3e763d5 c834c47
Author: Brad King 
AuthorDate: Mon Jan 14 14:14:09 2019 +
Commit: Kitware Robot 
CommitDate: Mon Jan 14 09:14:17 2019 -0500

Merge topic 'cpplint-no-output-no-warning'

c834c47dfc cpplint: only print diagnostics to console if there are errors

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=beb991110d84e9c0a6b1339e22fa98284b08bac9
commit beb991110d84e9c0a6b1339e22fa98284b08bac9
Author: Brad King 
AuthorDate: Fri Jan 11 13:50:46 2019 -0500
Commit: Brad King 
CommitDate: Fri Jan 11 13:50:46 2019 -0500

Remove now-unused code once used on IRIX

We dropped support for IRIX as a host platform long ago.
Remove some leftover code.

diff --git a/CompileFlags.cmake b/CompileFlags.cmake
index ec9b31b..5d0e144 100644
--- a/CompileFlags.cmake
+++ b/CompileFlags.cmake
@@ -28,13 +28,6 @@ if(CMAKE_SYSTEM_NAME MATCHES "AIX")
   endif()
 endif()
 
-if(CMAKE_SYSTEM_NAME MATCHES "IRIX")
-  if(NOT CMAKE_COMPILER_IS_GNUCXX)
-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wl,-woff84 -no_auto_include")
-set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -Wl,-woff15")
-  endif()
-endif()
-
 if(CMAKE_SYSTEM MATCHES "OSF1-V")
   if(NOT CMAKE_COMPILER_IS_GNUCXX)
 set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -timplicit_local 
-no_implicit_include ")
diff --git a/Modules/CMakeBackwardCompatibilityCXX.cmake 
b/Modules/CMakeBackwardCompatibilityCXX.cmake
index 628b541..02744a9 100644
--- a/Modules/CMakeBackwardCompatibilityCXX.cmake
+++ b/Modules/CMakeBackwardCompatibilityCXX.cmake
@@ -22,9 +22,6 @@ if(NOT CMAKE_SKIP_COMPATIBILITY_TESTS)
   if(NOT CMAKE_COMPILER_IS_GNUCXX)
 include(TestCXXAcceptsFlag)
 set(CMAKE_TRY_ANSI_CXX_FLAGS "")
-if(CMAKE_SYSTEM_NAME MATCHES "IRIX")
-  set(CMAKE_TRY_ANSI_CXX_FLAGS "-LANG:std")
-endif()
 if(CMAKE_SYSTEM_NAME MATCHES "OSF")
   set(CMAKE_TRY_ANSI_CXX_FLAGS "-std strict_ansi -nopure_cname")
 endif()
diff --git a/Modules/CMakeCompilerABI.h b/Modules/CMakeCompilerABI.h
index 6f36b03..45532af 100644
--- a/Modules/CMakeCompilerABI.h
+++ b/Modules/CMakeCompilerABI.h
@@ -10,16 +10,10 @@ const char info_sizeof_dptr[] = {
 };
 
 /* Application Binary Interface.  */
-#if defined(__sgi) && defined(_ABIO32)
-#  define ABI_ID "ELF O32"
-#elif defined(__sgi) && defined(_ABIN32)
-#  define ABI_ID "ELF N32"
-#elif defined(__sgi) && defined(_ABI64)
-#  define ABI_ID "ELF 64"
 
 /* Check for (some) ARM ABIs.
  * See e.g. http://wiki.debian.org/ArmEabiPort for some information on this. */
-#elif defined(__GNU__) && defined(__ELF__) && defined(__ARM_EABI__)
+#if defined(__GNU__) && defined(__ELF__) && defined(__ARM_EABI__)
 #  define ABI_ID "ELF ARMEABI"
 #elif defined(__GNU__) && defined(__ELF__) && defined(__ARMEB__)
 #  define ABI_ID "ELF ARM"
diff --git a/Modules/CMakeCompilerIdDetection.cmake 
b/Modules/CMakeCompilerIdDetection.cmake
index f2d43b6..9b2a91f 100644
--- a/Modules/CMakeCompilerIdDetection.cmake
+++ b/Modules/CMakeCompilerIdDetection.cmake
@@ -135,9 +135,6 @@ function(compiler_id_detection outvar lang)
 /* These compilers are either not known or too old to define an
   identification macro.  Try to identify the platform and guess that
   it is the native compiler.  */
-#elif defined(__sgi)
-# define ${CID_PREFIX}COMPILER_ID \"MIPSpro\"
-
 #elif defined(__hpux) || defined(__hpua)
 # define ${CID_PREFIX}COMPILER_ID \"HP\"
 
diff --git a/Modules/CMakeDetermineSystem.cmake 
b/Modules/CMakeDetermineSystem.cmake
index 600d558..dc208c6 100644
--- a/Modules/CMakeDetermineSystem.cmake
+++ b/Modules/CMakeDetermineSystem.cmake
@@ -13,7

[Cmake-commits] CMake annotated tag, v3.13.3, created. v3.13.3

2019-01-14 Thread 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 annotated tag, v3.13.3 has been created
at  085e1f6ac8e234c874c0e854945c5228d055638e (tag)
   tagging  8887ebc69b86606b388272d5c89ce11753bb4804 (commit)
  replaces  v3.13.2
 tagged by  Brad King
on  Mon Jan 14 09:07:45 2019 -0500

- Log -
CMake 3.13.3
-BEGIN PGP SIGNATURE-

iQJKBAABCgA0FiEExsJlMku+vcNQtRPQLSzvEDSSFoQFAlw8l7EWHGJyYWQua2lu
Z0BraXR3YXJlLmNvbQAKCRAtLO8QNJIWhOAMEACpNrxLFINl8nnXqS+bV7HN5v3E
ViCUrrCMd+FN2F7XwhlO/UfIGXq8YKq9dnVPBcLf9uaYPqDobBJvyFvxTM0D2Rrz
7knEMSJm/JFDAGat9V+eNYO6xMBmDhqWlujcD4dfF36CHiXr9GYTDHtK+6VPVrQp
S8wOkMgW81ogTT4Y4kM92xJag9Vp4FhwQs9k1OU2E+jvGMp65xBfLwx//BEgFLrR
kZNp4zpzY6Qa5olAonhBWQX7RTA90ec3znc0h6i58lBZ9PB2w35rAg1ZEVuYQT8+
/jy6ZSU9+mjiJ/5pDa0VopWhIpM99SAUIfFMaW1ucVdNZE+tvYUbYOu7uY3fh15Y
sFMbzhK0J8CCJje0vCL2sL5hjq0HALdqlpVvoJx9emo32egHudIJqDuSaBdyz1h+
w7TTp/u/8GuBIBLidr6NJ8qI2zTE70Z2YxmZfwfupfEUlpRawjsC5vvunNi6qp98
GNahzAi4ziCUfbMSI8FjxIwTDw1aW6rS91Y6wugzovBESIoh8yrEQOSe5z3J5WCZ
qEzQMquaoEXPBxlEYl+QxMTsrhY8N3YNW7w/8KW2sH6DtuQt2AATZ2GG5cZ7Hld7
DZSHU+wjUfphzz2DbIhuLui6s3xHew9xmylJEd17vGIxk66AJnBJ5/HfDqd030+6
SQRtJKK2HuK1k9LGpg==
=+nrX
-END PGP SIGNATURE-

Brad King (8):
  VS: Exclude VS 2019 instances when using VS 2017 generator
  Merge branch 'vs2017-skip-2019' into release-3.13
  Tests: Add cases for -{C,D,U} without a source tree
  Merge branch 'cmake-CDU-option-parsing' into release-3.13
  Tests: Add case for warning when AUTOMOC/UIC/RCC gets disabled
  Merge branch 'backport-autogen_noqt_warning' into release-3.13
  Merge branch 'cmake-option-parsing' into release-3.13
  CMake 3.13.3

Craig Scott (3):
  Merge branch 'feature/fix-link_resolved_item_into_bundle' into 
release-3.13
  cmake: Stop processing if -P option lacks file name
  cmake: Ensure source and binary dirs are set

Paul Seyfert (1):
  cmake: distinguish '-Cpath' from '-C path' in source dir parsing

Sebastian Holtermann (1):
  Autogen: Issue a warning when AUTOMOC/UIC/RCC gets disabled.

Tim Blechmann (1):
  BundleUtilities: Ensure target dir exists when creating symlinks

---


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.13.2-14-g8887ebc

2019-01-14 Thread 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  8887ebc69b86606b388272d5c89ce11753bb4804 (commit)
  from  c63a19e9201474750fea6adc11d75a9bb5a21e5b (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:
 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.13.2-898-g3e763d5

2019-01-14 Thread 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  3e763d506cda64d76c40d327371925e9df7cbca8 (commit)
   via  8887ebc69b86606b388272d5c89ce11753bb4804 (commit)
  from  848dc85187ec1e4b2364987d911ce7af93062b45 (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=3e763d506cda64d76c40d327371925e9df7cbca8
commit 3e763d506cda64d76c40d327371925e9df7cbca8
Merge: 848dc85 8887ebc
Author: Brad King 
AuthorDate: Mon Jan 14 09:02:41 2019 -0500
Commit: Brad King 
CommitDate: Mon Jan 14 09:02:41 2019 -0500

Merge branch 'release-3.13'


---

Summary of changes:


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.13.2-13-gc63a19e

2019-01-14 Thread 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  c63a19e9201474750fea6adc11d75a9bb5a21e5b (commit)
   via  27eb7c5bdb5bb8deefe1772675dc4819592bf036 (commit)
   via  a1adbc724336b0a4185e34b63e18de03a8b119cf (commit)
   via  ddb5b097cd29e2e7fcddcb79c4e3ae8c64b0a5b3 (commit)
   via  dd39da551883bca5f8ec1be376a77f6d5552 (commit)
   via  5ae69f591965886c5e6a1cde780a87ddc4c4722d (commit)
  from  91fa6a472cd262014a74d765b003bb1cc9d7ab8a (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:
 Source/cmGlobalGenerator.cxx   | 25 +++
 Source/cmake.cxx   | 25 ---
 Source/cmake.h |  3 +--
 Source/cmakemain.cxx   | 10 
 Tests/RunCMake/{Android => Autogen}/CMakeLists.txt |  2 +-
 Tests/RunCMake/Autogen/NoQt-stderr.txt |  8 ++
 Tests/RunCMake/Autogen/NoQt.cmake  |  6 +
 Tests/RunCMake/Autogen/RunCMakeTest.cmake  |  3 +++
 .../{include_directories => Autogen}/empty.cpp |  0
 Tests/RunCMake/CMakeLists.txt  |  1 +
 Tests/RunCMake/CommandLine/RunCMakeTest.cmake  | 29 +++---
 .../no-S-B-result.txt} |  0
 Tests/RunCMake/CommandLine/no-S-B-stderr.txt   |  1 +
 13 files changed, 82 insertions(+), 31 deletions(-)
 copy Tests/RunCMake/{Android => Autogen}/CMakeLists.txt (63%)
 create mode 100644 Tests/RunCMake/Autogen/NoQt-stderr.txt
 create mode 100644 Tests/RunCMake/Autogen/NoQt.cmake
 create mode 100644 Tests/RunCMake/Autogen/RunCMakeTest.cmake
 copy Tests/RunCMake/{include_directories => Autogen}/empty.cpp (100%)
 copy Tests/RunCMake/{while/MissingArgument-result.txt => 
CommandLine/no-S-B-result.txt} (100%)
 create mode 100644 Tests/RunCMake/CommandLine/no-S-B-stderr.txt


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.13.2-896-g848dc85

2019-01-14 Thread 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  848dc85187ec1e4b2364987d911ce7af93062b45 (commit)
   via  1f411b0cfaad12c87da02ffc2b20bb791b1f9024 (commit)
   via  c63a19e9201474750fea6adc11d75a9bb5a21e5b (commit)
   via  27eb7c5bdb5bb8deefe1772675dc4819592bf036 (commit)
   via  a1adbc724336b0a4185e34b63e18de03a8b119cf (commit)
   via  ddb5b097cd29e2e7fcddcb79c4e3ae8c64b0a5b3 (commit)
  from  6a23e16ec289ca737b7a4c1020e6b0c71c749672 (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=848dc85187ec1e4b2364987d911ce7af93062b45
commit 848dc85187ec1e4b2364987d911ce7af93062b45
Merge: 1f411b0 c63a19e
Author: Brad King 
AuthorDate: Mon Jan 14 07:26:12 2019 -0500
Commit: Brad King 
CommitDate: Mon Jan 14 07:26:12 2019 -0500

Merge branch 'release-3.13'


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1f411b0cfaad12c87da02ffc2b20bb791b1f9024
commit 1f411b0cfaad12c87da02ffc2b20bb791b1f9024
Merge: 6a23e16 27eb7c5
Author: Brad King 
AuthorDate: Mon Jan 14 12:25:39 2019 +
Commit: Kitware Robot 
CommitDate: Mon Jan 14 07:25:46 2019 -0500

Merge topic 'cmake-option-parsing'

27eb7c5bdb cmake: Ensure source and binary dirs are set
a1adbc7243 cmake: Stop processing if -P option lacks file name

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


---

Summary of changes:
 Source/cmake.cxx   | 25 ---
 Source/cmake.h |  3 +--
 Source/cmakemain.cxx   | 10 
 Tests/RunCMake/CommandLine/RunCMakeTest.cmake  | 29 +++---
 .../no-S-B-result.txt} |  0
 Tests/RunCMake/CommandLine/no-S-B-stderr.txt   |  1 +
 6 files changed, 38 insertions(+), 30 deletions(-)
 copy Tests/RunCMake/{while/MissingArgument-result.txt => 
CommandLine/no-S-B-result.txt} (100%)
 create mode 100644 Tests/RunCMake/CommandLine/no-S-B-stderr.txt


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.13.2-890-g6a23e16

2019-01-14 Thread 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  6a23e16ec289ca737b7a4c1020e6b0c71c749672 (commit)
   via  0377fe1e2b05b729b2baad6c78b922aa972b7c09 (commit)
   via  dd39da551883bca5f8ec1be376a77f6d5552 (commit)
   via  f44a0414aec38f6e70eb2c11c75c9f35bb526259 (commit)
   via  5ae69f591965886c5e6a1cde780a87ddc4c4722d (commit)
  from  dd90811bbf61fb9066f84463e9817b94324c105f (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=6a23e16ec289ca737b7a4c1020e6b0c71c749672
commit 6a23e16ec289ca737b7a4c1020e6b0c71c749672
Merge: dd90811 0377fe1
Author: Brad King 
AuthorDate: Mon Jan 14 11:51:32 2019 +
Commit: Kitware Robot 
CommitDate: Mon Jan 14 06:51:42 2019 -0500

Merge topic 'autogen_noqt_warning'

0377fe1e2b Merge branch 'backport-autogen_noqt_warning' into 
autogen_noqt_warning
dd39da5518 Tests: Add case for warning when AUTOMOC/UIC/RCC gets disabled
f44a0414ae Autogen: Issue a warning when AUTOMOC/UIC/RCC gets disabled.
5ae69f5919 Autogen: Issue a warning when AUTOMOC/UIC/RCC gets disabled.

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0377fe1e2b05b729b2baad6c78b922aa972b7c09
commit 0377fe1e2b05b729b2baad6c78b922aa972b7c09
Merge: f44a041 dd39da5
Author: Brad King 
AuthorDate: Fri Jan 11 08:41:51 2019 -0500
Commit: Brad King 
CommitDate: Fri Jan 11 08:41:51 2019 -0500

Merge branch 'backport-autogen_noqt_warning' into autogen_noqt_warning


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dd39da551883bca5f8ec1be376a77f6d5552
commit dd39da551883bca5f8ec1be376a77f6d5552
Author: Brad King 
AuthorDate: Fri Jan 11 08:27:14 2019 -0500
Commit: Brad King 
CommitDate: Fri Jan 11 08:28:42 2019 -0500

Tests: Add case for warning when AUTOMOC/UIC/RCC gets disabled

diff --git a/Tests/RunCMake/Autogen/CMakeLists.txt 
b/Tests/RunCMake/Autogen/CMakeLists.txt
new file mode 100644
index 000..9a66cde
--- /dev/null
+++ b/Tests/RunCMake/Autogen/CMakeLists.txt
@@ -0,0 +1,3 @@
+cmake_minimum_required(VERSION 3.13)
+project(${RunCMake_TEST} NONE)
+include(${RunCMake_TEST}.cmake)
diff --git a/Tests/RunCMake/Autogen/NoQt-stderr.txt 
b/Tests/RunCMake/Autogen/NoQt-stderr.txt
new file mode 100644
index 000..6b4a933
--- /dev/null
+++ b/Tests/RunCMake/Autogen/NoQt-stderr.txt
@@ -0,0 +1,8 @@
+^CMake Warning \(dev\) in CMakeLists.txt:
+  AUTOGEN: No valid Qt version found for target main.  AUTOMOC, AUTOUIC,
+  AUTORCC disabled.  Consider adding:
+
+find_package\(Qt5 COMPONENTS Widgets\)
+
+  to your CMakeLists.txt file.
+This warning is for project developers.  Use -Wno-dev to suppress it.
diff --git a/Tests/RunCMake/Autogen/NoQt.cmake 
b/Tests/RunCMake/Autogen/NoQt.cmake
new file mode 100644
index 000..b2d375a
--- /dev/null
+++ b/Tests/RunCMake/Autogen/NoQt.cmake
@@ -0,0 +1,6 @@
+enable_language(CXX)
+
+add_executable(main empty.cpp)
+set_property(TARGET main PROPERTY AUTOMOC 1)
+set_property(TARGET main PROPERTY AUTORCC 1)
+set_property(TARGET main PROPERTY AUTOUIC 1)
diff --git a/Tests/RunCMake/Autogen/RunCMakeTest.cmake 
b/Tests/RunCMake/Autogen/RunCMakeTest.cmake
new file mode 100644
index 000..e52f28d
--- /dev/null
+++ b/Tests/RunCMake/Autogen/RunCMakeTest.cmake
@@ -0,0 +1,3 @@
+include(RunCMake)
+
+run_cmake(NoQt)
diff --git a/Tests/RunCMake/Autogen/empty.cpp b/Tests/RunCMake/Autogen/empty.cpp
new file mode 100644
index 000..e69de29
diff --git a/Tests/RunCMake/CMakeLists.txt b/Tests/RunCMake/CMakeLists.txt
index 99f4ae7..89102dd 100644
--- a/Tests/RunCMake/CMakeLists.txt
+++ b/Tests/RunCMake/CMakeLists.txt
@@ -142,6 +142,7 @@ if(NOT CMake_TEST_EXTERNAL_CMAKE)
 endif()
 
 add_RunCMake_test(AndroidTestUtilities)
+add_RunCMake_test(Autogen)
 add_RunCMake_test(BuildDepends)
 if(UNIX AND "${CMAKE_GENERATOR}" MATCHES "Unix Makefiles|Ninja")
   add_RunCMake_test(Byproducts)

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f44a0414aec38f6e70eb2c11c75c9f35bb526259
commit f44a0414aec38f6e70eb2c11c75c9f35bb526259
Author: Sebastian Holtermann 
AuthorDate: Thu Jan 10 17:39:51 2019 +0100
Commit: Brad King 
CommitDate: Thu Jan 10 14:05:33 2019 -0500

Autogen: Issue a warning when AUTOMOC/UIC/RCC gets disabled.

We used to silently disable AUTOMOC/UIC/RCC when no valid Qt
version was found.  This patch introduces the generation of
a warning message in that case.

diff --git a/Source/cmQtAutoGenGlobalInitializer.cxx 
b/Source/cmQtAutoGenGlobalInitializer.cxx
index 678ff14..f4cf3e0 100644
--- a/Source/cmQtAutoGenGlobalInitializer.cxx
+++

Re: [cmake-developers] Support for list length expression in if()-command?

2019-01-14 Thread Brad King via cmake-developers 
On 1/14/19 4:21 AM, Torsten Robitzki wrote:
> if (LENGTH list GREATER 1)

An investigation will be needed to determine whether a policy
is needed to add this to the if() command to avoid possible
behavior changes for existing callers.

For reference, you asked this previously:

  https://cmake.org/pipermail/cmake-developers/2018-December/030941.html

I've almost never needed to test the length of a list in CMake
code.  It's not very common in my experience.  What is your
customer trying to do?

-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

[cmake-developers] Support for list length expression in if()-command?

2019-01-14 Thread Torsten Robitzki 
Hi,
I have a customer that requires quite often to check, whether a list contains 
at least a given number of elements. As we do not have functions with return 
values, this requires him to inquire the length of a list before taking special 
actions.

To simplify that task (and without larger changes in CMake [like introducing 
*real* functions]), he came up with the idea to extend the if()-command with a 
LENGTH operator:

set(list)

…

if (LENGTH list GREATER 1)
…
endif()

Would such an extension be accepted as pull request, if we would provide it?

regards,

Torsten



signature.asc
Description: Message signed with OpenPGP
-- 

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

[CMake] How to correctly default initialize CMAKE_BUILD_TYPE inside CMakeLists.txt

2019-01-14 Thread Kim Walisch 
Hi,

By default I would like to set CMAKE_BUILD_TYPE=Release (inside
CMakeLists.txt) if the user has not defined CMAKE_BUILD_TYPE himself (e.g.
as command-line option: cmake . -DCMAKE_BUILD_TYPE=Debug). Is there a best
practice how to do this in CMake? I have been searching the web to see how
other people achieved this and I found that many people use code like this:

if(NOT CMAKE_BUILD_TYPE)
set(CMAKE_BUILD_TYPE "Release" CACHE STRING
"Choose the type of build, options are: None Debug Release
RelWithDebInfo MinSizeRel."
FORCE)
endif()

I used this code myself in one of my projects but I recently discovered
that this code causes issues when compiling with clang-cl on Windows.

Greetings,
Kim
-- 

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] How to specify gfortran in an MSVC project

2019-01-14 Thread Stephen Morris 
Thank you KT; let's see what they say.

Like in your case, I have a project structure where my Fortran library depends 
on various C libraries, and my C++ application depends on those same C 
libraries both indirectly (through the Fortran library) and directly. I'd like 
to be able to use the MSVC versions of those C libraries (and as the interfaces 
are C, not C++, this ought to be straightforward). Currently, however, the only 
way I can get my Fortran code to compile is if I call it from the command line 
with the "MinGW Makefiles" generator, in which case it uses MinGW versions for 
all the other libraries as well.

Warm regards,
Stephen.

From: Thompson, KT 
Sent: 14 January 2019 04:06
To: Stephen Morris ; cmake@cmake.org
Subject: Re: How to specify gfortran in an MSVC project


Hi Stephen,



I am also interested in Kitware's response to your question.  I don't use Qt 
Creator, but I help maintain several projects that use Visual Studio and MinGW 
gfortran via the CMakeAddFortranSubdirectory feature.  This feature is somewhat 
limited and not really maintained (in my experience).



Background: In my case, I use a heavily modified version of 
CMakeAddFortranSubdirectory  that supports Xcode builds in addition to MSVC.  I 
also have dependencies of the form mycpp.exe -> myf90.lib -> mycpp.lib -> 
msmpi.lib that standard CMakeAddFortranSubdirectory doesn't know how to deal 
with.



When I run the 'build' target via Visual Studio, the Fortran compiler is 
discovered by CMakeAddFortranSubdirectory only if gfortran.exe is in %PATH% 
(via find_program -- I believe that the default code only supports the name 
'gfortran.exe'.)  You might need to add C:/Qt/Tools/mingw730_64/bin/ to your 
local path before running cmake for the project.  I have found that 
CMakeAddFortranSubdirectory isn't flexible.  You may need modify it for your 
own needs.



-kt


From: CMake mailto:cmake-boun...@cmake.org>> on behalf 
of Stephen Morris mailto:s-mor...@n-eos.com>>
Sent: Sunday, January 13, 2019 6:14:33 PM
To: cmake@cmake.org
Subject: [CMake] How to specify gfortran in an MSVC project

I would like to try to use 64-bit gfortran to compile a project in which the 
rest of the code is compiled with Visual C++ 2017. I've read the netlib article 
(http://www.netlib.org/lapack/lawnspdf/lawn270.pdf) but it doesn't address my 
problem, which is how to help CMake select the right Fortran compiler. The 
CMakeLists.txt file is launched from within Qt Creator.

My CMakeLists.txt file (which I've tested thoroughly using gfortran in Linux 
and MinGW gfortran on Windows) begins:

cmake_minimum_required(VERSION 3.12)
project(myProj LANGUAGES Fortran)

...and if I set Qt Creator to parse it with the MSVC compiler option selected, 
the output is:

Starting to parse CMake project, using: 
"-DCMAKE_CXX_COMPILER:STRING=C:/Program Files (x86)/Microsoft Visual 
Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/HostX86/x64/cl.exe", 
"-DCMAKE_C_COMPILER:STRING=C:/Program Files (x86)/Microsoft Visual 
Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/HostX86/x64/cl.exe", 
"-DCMAKE_PREFIX_PATH:STRING=C:/Qt/5.9.7/msvc2017_64", 
"-DQT_QMAKE_EXECUTABLE:STRING=C:/Qt/5.9.7/msvc2017_64/bin/qmake.exe".
The Fortran compiler identification is unknown
CMake Error at CMakeLists.txt:2 (project):
  No CMAKE_Fortran_COMPILER could be found.

  Tell CMake where to find the compiler by setting either the environment
  variable "FC" or the CMake cache entry CMAKE_Fortran_COMPILER to the full
  path to the compiler, or to the compiler name if it is in the PATH.

Fair enough; here's my second attempt:

cmake_minimum_required(VERSION 3.12)
set(CMAKE_Fortran_COMPILER "C:/Qt/Tools/mingw730_64/bin/gfortran.exe")
project(myProj LANGUAGES Fortran)

...and this gives me:

Starting to parse CMake project, using: 
"-DCMAKE_CXX_COMPILER:STRING=C:/Program Files (x86)/Microsoft Visual 
Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/HostX86/x64/cl.exe", 
"-DCMAKE_C_COMPILER:STRING=C:/Program Files (x86)/Microsoft Visual 
Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/HostX86/x64/cl.exe", 
"-DCMAKE_PREFIX_PATH:STRING=C:/Qt/5.9.7/msvc2017_64", 
"-DQT_QMAKE_EXECUTABLE:STRING=C:/Qt/5.9.7/msvc2017_64/bin/qmake.exe".
The Fortran compiler identification is unknown
Check for working Fortran compiler: C:/Qt/Tools/mingw730_64/bin/gfortran.exe
CMake Error: Error required internal CMake variable not set, cmake may not 
be built correctly.
Missing variable is:
CMAKE_Fortran_PREPROCESS_SOURCE
CMake Error at C:/Program 
Files/CMake/share/cmake-3.12/Modules/CMakeTestFortranCompiler.cmake:30 
(try_compile):
  Failed to generate test project build system.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)

In place of the "set(CMAKE_Fortran_COMPILER..." line I've also tried

set($ENV{FC}