[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-276-ge46350f

[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  e46350ffd98c39cb788aa2fdfbef9753d6089af6 (commit)
  from  188c762f8a5f690708109a3cb8d44693e599adb1 (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=e46350ffd98c39cb788aa2fdfbef9753d6089af6
commit e46350ffd98c39cb788aa2fdfbef9753d6089af6
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Tue Oct 18 00:01:03 2016 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Tue Oct 18 00:01:03 2016 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 3640ea8..e311274 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 7)
-set(CMake_VERSION_PATCH 20161017)
+set(CMake_VERSION_PATCH 20161018)
 #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
http://public.kitware.com/mailman/listinfo/cmake-commits

[CMake] cmake doesn't find QtCore

[Spencer Parkin]

Hi,

I'm trying to install PySide.  With "pip install PySide", I get the
warning...

CMake Warning at c:/Program Files
(x86)/Cmake/share/cmake-3.7/Modules/FindQt4.cmake:618 (message):
C:/Qt/4.8.5/bin/qmake.exe reported QT_INSTALL_LIBS as "C:/Qt/4.8.5/lib" but
QtCore could not be found there.  Qt is NOT installed correctly for the
target build environment.

...I, however, believe that Qt IS installed correctly.  I find QtCore4.lib
in the said directory.  I tried to decipher the code found in
FindQt4.cmake, but I don't know the cmake language.  "qmake -query
QT_INSTALL_LIBS" does indeed report the directory named above, and it's
full of Qt-licious libraries.

Later on I see...

Qt QTGUI library not found.
Qt QTXML library not found.
Qt QTCORE library not found.

...and the ultimate wammy...

CMake Error at ApiExtractor/CmakeLists.txt:82 (qt4_add_resources): Unknown
CMake command "qt4_add_resources".

So "shiboken" fails to configure.  But I'm hoping that the latter errors
are just a symptom of the initial warning above indicating that, oddly,
cmake can't locate my Qt libraries.

I'm at a complete loss.  I've wasted an entire day here at work on this one
issue.  Any help would be greatly appreciated.

--Sp
-- 

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:
http://public.kitware.com/mailman/listinfo/cmake

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-576-g237866b

[Brad King]

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, next has been updated
   via  237866b8bdb6d39992e3f77cd56e82e4181d5947 (commit)
   via  4bc17345c01ea467099e28c7df30c23ace9e7811 (commit)
  from  f923940b7c9c93179b7ea6356c32c8a7beedebe2 (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=237866b8bdb6d39992e3f77cd56e82e4181d5947
commit 237866b8bdb6d39992e3f77cd56e82e4181d5947
Merge: f923940 4bc1734
Author: Brad King 
AuthorDate: Mon Oct 17 14:56:31 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 14:56:31 2016 -0400

Merge topic 'CheckFunctionExists-prototype' into next

4bc17345 CheckFunctionExists.c: avoid gcc warnings with -Wstrict-prototypes


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4bc17345c01ea467099e28c7df30c23ace9e7811
commit 4bc17345c01ea467099e28c7df30c23ace9e7811
Author: Andre McCurdy 
AuthorDate: Fri Oct 14 16:26:58 2016 -0700
Commit: Andre McCurdy 
CommitDate: Fri Oct 14 16:26:58 2016 -0700

CheckFunctionExists.c: avoid gcc warnings with -Wstrict-prototypes

Avoid warnings (and therefore build failures etc) if a user happens
to add -Wstrict-prototypes to CFLAGS.

 | $ gcc --version
 | gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
 |
 | $ gcc -Wstrict-prototypes -Werror -DCHECK_FUNCTION_EXISTS=pthread_create 
-o foo.o -c Modules/CheckFunctionExists.c
 | Modules/CheckFunctionExists.c:7:3: error: function declaration isn't a 
prototype [-Werror=strict-prototypes]
 |CHECK_FUNCTION_EXISTS();
 |^
 | cc1: all warnings being treated as errors
 |

Signed-off-by: Andre McCurdy 

diff --git a/Modules/CheckFunctionExists.c b/Modules/CheckFunctionExists.c
index 2304000..224e340 100644
--- a/Modules/CheckFunctionExists.c
+++ b/Modules/CheckFunctionExists.c
@@ -4,7 +4,7 @@
 extern "C"
 #endif
   char
-  CHECK_FUNCTION_EXISTS();
+  CHECK_FUNCTION_EXISTS(void);
 #ifdef __CLASSIC_C__
 int main()
 {

---

Summary of changes:
 Modules/CheckFunctionExists.c |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-574-gf923940

[Brad King]

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, next has been updated
   via  f923940b7c9c93179b7ea6356c32c8a7beedebe2 (commit)
   via  909842fff98983bff8b61c37b11a99d89dcc4d36 (commit)
  from  2f779b24d65321dc05974c46a69cc3150f3d09cd (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=f923940b7c9c93179b7ea6356c32c8a7beedebe2
commit f923940b7c9c93179b7ea6356c32c8a7beedebe2
Merge: 2f779b2 909842f
Author: Brad King 
AuthorDate: Mon Oct 17 14:47:27 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 14:47:27 2016 -0400

Merge topic 'timeout_after_match_testtime' into next

909842ff CTest: report time spent after matching output


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=909842fff98983bff8b61c37b11a99d89dcc4d36
commit 909842fff98983bff8b61c37b11a99d89dcc4d36
Author: Zack Galbreath 
AuthorDate: Mon Oct 17 11:24:01 2016 -0400
Commit: Zack Galbreath 
CommitDate: Mon Oct 17 11:24:32 2016 -0400

CTest: report time spent after matching output

When using the TIMEOUT_AFTER_MATCH test property, only report the
time spent by the test after the matching output was found.

diff --git a/Help/prop_test/TIMEOUT_AFTER_MATCH.rst 
b/Help/prop_test/TIMEOUT_AFTER_MATCH.rst
index a191a9c..d607992 100644
--- a/Help/prop_test/TIMEOUT_AFTER_MATCH.rst
+++ b/Help/prop_test/TIMEOUT_AFTER_MATCH.rst
@@ -22,7 +22,9 @@ When the test outputs a line that matches ``regex`` its start 
time is
 reset to the current time and its timeout duration is changed to
 ``seconds``.  Prior to this, the timeout duration is determined by the
 :prop_test:`TIMEOUT` property or the :variable:`CTEST_TEST_TIMEOUT`
-variable if either of these are set.
+variable if either of these are set.  Because the test's start time is
+reset, its execution time will not include any time that was spent
+waiting for the matching output.
 
 :prop_test:`TIMEOUT_AFTER_MATCH` is useful for avoiding spurious
 timeouts when your test must wait for some system resource to become
diff --git a/Source/CTest/cmProcess.cxx b/Source/CTest/cmProcess.cxx
index cf3c7ac..a24fe21 100644
--- a/Source/CTest/cmProcess.cxx
+++ b/Source/CTest/cmProcess.cxx
@@ -225,6 +225,7 @@ void cmProcess::ChangeTimeout(double t)
 void cmProcess::ResetStartTime()
 {
   cmsysProcess_ResetStartTime(this->Process);
+  this->StartTime = cmSystemTools::GetTime();
 }
 
 int cmProcess::GetExitException()

---

Summary of changes:
 Help/prop_test/TIMEOUT_AFTER_MATCH.rst |4 +++-
 Source/CTest/cmProcess.cxx |1 +
 2 files changed, 4 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [CMake] Single Letter Omissions From File Path In Linker

[Max Smolens]

Hi Randy,

The missing character issue is likely due to some stage of your build
process hitting a command line length limit on Windows. Similar problems
have been described in 3D Slicer builds [1] [2], although in that case the
problems were related to (a) many include directories and (b) explicitly
passing a long command line to add_custom_command().

Your project may be different, because the error occurs while linking, but
hopefully these references help.

Thanks,
Max

[1] http://slicer-devel.65872.n3.nabble.com/VS2008-build-
td4032311.html#a4032337
[2] https://www.na-mic.org/Bug/view.php?id=3157


On Mon, Oct 17, 2016 at 10:59 AM, Randy Turner 
wrote:

> Thanks, Andrew, Bill, and Zan! I'm not completely certain that
> reinstalling Windows is the only or even the best solution, but once we all
> moved our repositories into our root directories I have not found another
> solution, even temporary. Of our six dev machines, it is a recurring
> problem on two and has occurred once on a third. The other three have never
> seen this problem.
>
> I did some digging on Friday and found that the problem seems to be
> connected to this call below to add all of our code files to a library to
> be used an item in the add_executable() command for each of our targets.
>
> foreach (code ${code_files})
> get_filename_component (codeName ${code} NAME_WE)
> add_library (${codeName} OBJECT
>  ${code}
>   )
>   list(APPEND codelib $)
> endforeach()
>
> If I remove that loop and add code_files instead of codelib to the
> executables then the problem disappears, but this breaks most of the
> functionality of my implementation of CMake, so this isn't a long-term
> solution. Using the library call above I followed the file paths around the
> script and printed them out at every step through the makefile generation
> and never saw any incorrect paths, but then I called the compiler and saw
> it error out.
>
> The project uses "Unix Makefiles" to run on TI's gmake compiler 7.4.14.
> I'm have been using CMake 3.5.2. I upgraded to 3.6.2 and continue to see
> the same problem. I will move forward with looking into this library issue
> but I'm sure what I expect to find.
>
> On Fri, Oct 14, 2016 at 10:16 AM, Andrew Bell 
> wrote:
>
>> On Fri, Oct 14, 2016 at 9:04 AM, Randy Turner > > wrote:
>>
>>> Hello! I've been running into a frustrating issue on and off for the
>>> past year. The project will build the source files correctly but when it
>>> comes to linking the executables, I always get the same error. The specific
>>> file varies, but the failure mode is always the same. For example:
>>>
>>> 
>>> "C:\\Users\\User\\AppData\\Local\\Temp\\", line
>>> xxx: error #10008-D: cannot find file
>>> "C:/Repos/operatingsystem/CMakeFiles/nvm_validate_ierator.di
>>> r/os/nvm/nvm_validate_iterator.c.obj"
>>>
>>> As you can see, the file path is missing a "t" in the first occurrence
>>> of the word "iterator" and so that file definitely does not exist. A file
>>> exists in the location with correct spelling, but somehow that hardcoded
>>> path in that temporary file has dropped a letter. The specific letter that
>>> gets dropped varies along with which file is allegedly missing. We noticed
>>> that requiring people to store the repository in their root directory
>>> greatly cut down on the occurrence of this issue but it is returning with
>>> more frequency as of late. Once it occurs once, CMake builds are never
>>> successful again and the only way that I have been able to completely clear
>>> the problem has been to reinstall Windows and set up the build environment
>>> again.
>>>
>>
>> This seems really, really strange.  Have to reinstall Windows?  What
>> about just using another build directory?  It sure *seems* like there's
>> some problem in your CMakeFiles.txt where the way the filepath is being
>> constructed is incorrect.  But I don't think you've really provided enough
>> information to determine the problem.  Where does the name of the object
>> file come from?
>>
>> --
>> Andrew Bell
>> andrew.bell...@gmail.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:
> http://public.kitware.com/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 

Re: [CMake] Single Letter Omissions From File Path In Linker

[Bill Hoffman]

Can you create a small example that shows the problem?  Even a small 
full example with the code you have below so I can better understand it.


-Bill


On 10/17/2016 10:59 AM, Randy Turner wrote:

Thanks, Andrew, Bill, and Zan! I'm not completely certain that
reinstalling Windows is the only or even the best solution, but once we
all moved our repositories into our root directories I have not found
another solution, even temporary. Of our six dev machines, it is a
recurring problem on two and has occurred once on a third. The other
three have never seen this problem.

I did some digging on Friday and found that the problem seems to be
connected to this call below to add all of our code files to a library
to be used an item in the add_executable() command for each of our targets.

foreach (code ${code_files})
get_filename_component (codeName ${code} NAME_WE)
add_library (${codeName} OBJECT
 ${code}
  )
  list(APPEND codelib $)
endforeach()

If I remove that loop and add code_files instead of codelib to the
executables then the problem disappears, but this breaks most of the
functionality of my implementation of CMake, so this isn't a long-term
solution. Using the library call above I followed the file paths around
the script and printed them out at every step through the makefile
generation and never saw any incorrect paths, but then I called the
compiler and saw it error out.

The project uses "Unix Makefiles" to run on TI's gmake compiler 7.4.14.
I'm have been using CMake 3.5.2. I upgraded to 3.6.2 and continue to see
the same problem. I will move forward with looking into this library
issue but I'm sure what I expect to find.

On Fri, Oct 14, 2016 at 10:16 AM, Andrew Bell > wrote:

On Fri, Oct 14, 2016 at 9:04 AM, Randy Turner
> wrote:

Hello! I've been running into a frustrating issue on and off for
the past year. The project will build the source files correctly
but when it comes to linking the executables, I always get the
same error. The specific file varies, but the failure mode is
always the same. For example:


"C:\\Users\\User\\AppData\\Local\\Temp\\",
line xxx: error #10008-D: cannot find file

"C:/Repos/operatingsystem/CMakeFiles/nvm_validate_ierator.dir/os/nvm/nvm_validate_iterator.c.obj"

As you can see, the file path is missing a "t" in the first
occurrence of the word "iterator" and so that file definitely
does not exist. A file exists in the location with correct
spelling, but somehow that hardcoded path in that temporary file
has dropped a letter. The specific letter that gets dropped
varies along with which file is allegedly missing. We noticed
that requiring people to store the repository in their root
directory greatly cut down on the occurrence of this issue but
it is returning with more frequency as of late. Once it occurs
once, CMake builds are never successful again and the only way
that I have been able to completely clear the problem has been
to reinstall Windows and set up the build environment again.


This seems really, really strange.  Have to reinstall Windows?  What
about just using another build directory?  It sure *seems* like
there's some problem in your CMakeFiles.txt where the way the
filepath is being constructed is incorrect.  But I don't think
you've really provided enough information to determine the problem.
Where does the name of the object file come from?

--
Andrew Bell
andrew.bell...@gmail.com 







--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
--

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:
http://public.kitware.com/mailman/listinfo/cmake

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-572-g2f779b2

[Brad King]

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, next has been updated
   via  2f779b24d65321dc05974c46a69cc3150f3d09cd (commit)
   via  19beee46cc6e9b7a05694b29420ad49487648501 (commit)
  from  6b400f503118e894685bb88f7b18ade37bca5dfe (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=2f779b24d65321dc05974c46a69cc3150f3d09cd
commit 2f779b24d65321dc05974c46a69cc3150f3d09cd
Merge: 6b400f5 19beee4
Author: Brad King 
AuthorDate: Mon Oct 17 11:20:24 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 11:20:24 2016 -0400

Merge topic 'propagate_ctest_use_launchers' into next

19beee46 ctest_configure: Propagate CTEST_USE_LAUNCHERS from caller to 
project


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=19beee46cc6e9b7a05694b29420ad49487648501
commit 19beee46cc6e9b7a05694b29420ad49487648501
Author: Bill Hoffman 
AuthorDate: Fri Oct 14 14:01:50 2016 -0400
Commit: Brad King 
CommitDate: Mon Oct 17 11:15:36 2016 -0400

ctest_configure: Propagate CTEST_USE_LAUNCHERS from caller to project

If `CTEST_USE_LAUNCHERS` is `TRUE` in a CTest script then the
`ctest_configure` command will add `-DCTEST_USE_LAUNCHERS:BOOL=TRUE` to
the cmake command used to configure the project.  This allows a project
to only set `CTEST_USE_LAUNCHERS` in a ctest script and have launchers
work.

diff --git a/Modules/CTestUseLaunchers.cmake b/Modules/CTestUseLaunchers.cmake
index 1cf20eb..dc90513 100644
--- a/Modules/CTestUseLaunchers.cmake
+++ b/Modules/CTestUseLaunchers.cmake
@@ -24,7 +24,9 @@
 # include(CTestUseLaunchers), it will use the value of the ENV variable
 # to initialize a CTEST_USE_LAUNCHERS cache variable.  This cache
 # variable initialization only occurs if CTEST_USE_LAUNCHERS is not
-# already defined.
+# already defined. If CTEST_USE_LAUNCHERS is on in a ctest -S script
+# the ctest_configure command will add -DCTEST_USE_LAUNCHERS:BOOL=TRUE
+# to the cmake command used to configure the project.
 
 if(NOT DEFINED CTEST_USE_LAUNCHERS AND DEFINED 
ENV{CTEST_USE_LAUNCHERS_DEFAULT})
   set(CTEST_USE_LAUNCHERS "$ENV{CTEST_USE_LAUNCHERS_DEFAULT}"
diff --git a/Source/CTest/cmCTestConfigureCommand.cxx 
b/Source/CTest/cmCTestConfigureCommand.cxx
index 62802ef..73e893d 100644
--- a/Source/CTest/cmCTestConfigureCommand.cxx
+++ b/Source/CTest/cmCTestConfigureCommand.cxx
@@ -102,6 +102,10 @@ cmCTestGenericHandler* 
cmCTestConfigureCommand::InitializeHandler()
 cmakeConfigureCommand += "\"";
   }
 
+  if (this->Makefile->IsOn("CTEST_USE_LAUNCHERS")) {
+cmakeConfigureCommand += " \"-DCTEST_USE_LAUNCHERS:BOOL=TRUE\"";
+  }
+
   cmakeConfigureCommand += " \"-G";
   cmakeConfigureCommand += cmakeGeneratorName;
   cmakeConfigureCommand += "\"";
diff --git a/Tests/RunCMake/ctest_build/CMakeLists.txt.in 
b/Tests/RunCMake/ctest_build/CMakeLists.txt.in
index 82cb7c4..133ae36 100644
--- a/Tests/RunCMake/ctest_build/CMakeLists.txt.in
+++ b/Tests/RunCMake/ctest_build/CMakeLists.txt.in
@@ -1,4 +1,5 @@
 cmake_minimum_required(VERSION 3.1)
+@CASE_CMAKELISTS_PREFIX_CODE@
 project(CTestBuild@CASE_NAME@ NONE)
 include(CTest)
 add_test(NAME RunCMakeVersion COMMAND "${CMAKE_COMMAND}" --version)
diff --git a/Tests/RunCMake/ctest_build/RunCMakeTest.cmake 
b/Tests/RunCMake/ctest_build/RunCMakeTest.cmake
index 324f25c..1092d2a 100644
--- a/Tests/RunCMake/ctest_build/RunCMakeTest.cmake
+++ b/Tests/RunCMake/ctest_build/RunCMakeTest.cmake
@@ -13,6 +13,11 @@ function(run_BuildFailure)
   set(CASE_CMAKELISTS_SUFFIX_CODE [[
 add_custom_target(BuildFailure ALL COMMAND command-does-not-exist)
 ]])
+  set(CASE_CMAKELISTS_PREFIX_CODE [[
+if(NOT CTEST_USE_LAUNCHERS)
+  message(FATAL_ERROR "CTEST_USE_LAUNCHERS not set")
+endif()
+]])
   set(CASE_TEST_PREFIX_CODE [[
 cmake_policy(SET CMP0061 NEW)
 ]])
diff --git a/Tests/RunCMake/ctest_build/test.cmake.in 
b/Tests/RunCMake/ctest_build/test.cmake.in
index 768f1c6..6f15ec9 100644
--- a/Tests/RunCMake/ctest_build/test.cmake.in
+++ b/Tests/RunCMake/ctest_build/test.cmake.in
@@ -9,6 +9,7 @@ set(CTEST_CMAKE_GENERATOR   "@RunCMake_GENERATOR@")
 set(CTEST_CMAKE_GENERATOR_PLATFORM  "@RunCMake_GENERATOR_PLATFORM@")
 set(CTEST_CMAKE_GENERATOR_TOOLSET   "@RunCMake_GENERATOR_TOOLSET@")
 set(CTEST_BUILD_CONFIGURATION   "$ENV{CMAKE_CONFIG_TYPE}")
+set(CTEST_USE_LAUNCHERS TRUE)
 
 set(ctest_build_args "@CASE_CTEST_BUILD_ARGS@")
 ctest_start(Experimental)

---

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-570-g6b400f5

[Brad King]

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, next has been updated
   via  6b400f503118e894685bb88f7b18ade37bca5dfe (commit)
   via  52e8fa2312c73338c7fac38e7c2b30f136f4d247 (commit)
  from  a9540002c5101e533e1896a4150462f20ceac68f (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=6b400f503118e894685bb88f7b18ade37bca5dfe
commit 6b400f503118e894685bb88f7b18ade37bca5dfe
Merge: a954000 52e8fa2
Author: Brad King 
AuthorDate: Mon Oct 17 11:07:48 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 11:07:48 2016 -0400

Merge topic 'FindwxWidgets-unversioned-library-path' into next

52e8fa23 FindwxWidgets: Fix finding unversioned VS-built directory prefixes


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=52e8fa2312c73338c7fac38e7c2b30f136f4d247
commit 52e8fa2312c73338c7fac38e7c2b30f136f4d247
Author: Brad King 
AuthorDate: Mon Oct 17 10:39:36 2016 -0400
Commit: Brad King 
CommitDate: Mon Oct 17 11:06:00 2016 -0400

FindwxWidgets: Fix finding unversioned VS-built directory prefixes

The change in commit v3.7.0-rc1~217^2 (FindwxWidgets: Add VS-versioned
library directory prefixes, 2016-08-24) works only for official
wxWidgets builds that add the VS-versioned directory prefixes.  Local
wxWidgets builds still have an unversioned prefix.  Search them.

Closes: #16366

diff --git a/Modules/FindwxWidgets.cmake b/Modules/FindwxWidgets.cmake
index eee47db..77091f4 100644
--- a/Modules/FindwxWidgets.cmake
+++ b/Modules/FindwxWidgets.cmake
@@ -491,23 +491,26 @@ if(wxWidgets_FIND_STYLE STREQUAL "win32")
 # Select one default tree inside the already determined wx tree.
 # Prefer static/shared order usually consistent with build
 # settings.
+set(_WX_TOOL "")
+set(_WX_TOOLVER "")
+set(_WX_ARCH "")
 if(MINGW)
-  set(WX_LIB_DIR_PREFIX gcc)
+  set(_WX_TOOL gcc)
 elseif(MSVC)
-  set(WX_LIB_DIR_PREFIX vc)
+  set(_WX_TOOL vc)
   if(MSVC14)
-set(WX_LIB_DIR_PREFIX ${WX_LIB_DIR_PREFIX}140)
+set(_WX_TOOLVER 140)
   elseif(MSVC12)
-set(WX_LIB_DIR_PREFIX ${WX_LIB_DIR_PREFIX}120)
+set(_WX_TOOLVER 120)
   elseif(MSVC11)
-set(WX_LIB_DIR_PREFIX ${WX_LIB_DIR_PREFIX}110)
+set(_WX_TOOLVER 110)
   elseif(MSVC10)
-set(WX_LIB_DIR_PREFIX ${WX_LIB_DIR_PREFIX}100)
+set(_WX_TOOLVER 100)
   elseif(MSVC90)
-set(WX_LIB_DIR_PREFIX ${WX_LIB_DIR_PREFIX}90)
+set(_WX_TOOLVER 90)
   endif()
   if(CMAKE_SIZEOF_VOID_P EQUAL 8)
-set(WX_LIB_DIR_PREFIX ${WX_LIB_DIR_PREFIX}_x64)
+set(_WX_ARCH _x64)
   endif()
 endif()
 if(BUILD_SHARED_LIBS)
@@ -522,8 +525,10 @@ if(wxWidgets_FIND_STYLE STREQUAL "win32")
   mswunivu/wx/setup.h
   mswunivud/wx/setup.h
 PATHS
-${WX_ROOT_DIR}/lib/${WX_LIB_DIR_PREFIX}_dll   # prefer shared
-${WX_ROOT_DIR}/lib/${WX_LIB_DIR_PREFIX}_lib
+${WX_ROOT_DIR}/lib/${_WX_TOOL}${_WX_TOOLVER}${_WX_ARCH}_dll   # prefer 
shared
+${WX_ROOT_DIR}/lib/${_WX_TOOL}${_WX_ARCH}_dll # prefer 
shared
+${WX_ROOT_DIR}/lib/${_WX_TOOL}${_WX_TOOLVER}${_WX_ARCH}_lib
+${WX_ROOT_DIR}/lib/${_WX_TOOL}${_WX_ARCH}_lib
 DOC "Path to wxWidgets libraries"
 NO_DEFAULT_PATH
 )
@@ -539,12 +544,17 @@ if(wxWidgets_FIND_STYLE STREQUAL "win32")
   mswunivu/wx/setup.h
   mswunivud/wx/setup.h
 PATHS
-${WX_ROOT_DIR}/lib/${WX_LIB_DIR_PREFIX}_lib   # prefer static
-${WX_ROOT_DIR}/lib/${WX_LIB_DIR_PREFIX}_dll
+${WX_ROOT_DIR}/lib/${_WX_TOOL}${_WX_TOOLVER}${_WX_ARCH}_lib   # prefer 
static
+${WX_ROOT_DIR}/lib/${_WX_TOOL}${_WX_ARCH}_lib # prefer 
static
+${WX_ROOT_DIR}/lib/${_WX_TOOL}${_WX_TOOLVER}${_WX_ARCH}_dll
+${WX_ROOT_DIR}/lib/${_WX_TOOL}${_WX_ARCH}_dll
 DOC "Path to wxWidgets libraries"
 NO_DEFAULT_PATH
 )
 endif()
+unset(_WX_TOOL)
+unset(_WX_TOOLVER)
+unset(_WX_ARCH)
 
 # If wxWidgets_LIB_DIR changed, clear all libraries.
 if(NOT WX_LIB_DIR STREQUAL wxWidgets_LIB_DIR)

---

Summary of changes:
 Modules/FindwxWidgets.cmake |   34 ++
 1 file changed, 22 insertions(+), 12 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org

Re: [CMake] Single Letter Omissions From File Path In Linker

[Randy Turner]

Thanks, Andrew, Bill, and Zan! I'm not completely certain that reinstalling
Windows is the only or even the best solution, but once we all moved our
repositories into our root directories I have not found another solution,
even temporary. Of our six dev machines, it is a recurring problem on two
and has occurred once on a third. The other three have never seen this
problem.

I did some digging on Friday and found that the problem seems to be
connected to this call below to add all of our code files to a library to
be used an item in the add_executable() command for each of our targets.

foreach (code ${code_files})
get_filename_component (codeName ${code} NAME_WE)
add_library (${codeName} OBJECT
 ${code}
  )
  list(APPEND codelib $)
endforeach()

If I remove that loop and add code_files instead of codelib to the
executables then the problem disappears, but this breaks most of the
functionality of my implementation of CMake, so this isn't a long-term
solution. Using the library call above I followed the file paths around the
script and printed them out at every step through the makefile generation
and never saw any incorrect paths, but then I called the compiler and saw
it error out.

The project uses "Unix Makefiles" to run on TI's gmake compiler 7.4.14. I'm
have been using CMake 3.5.2. I upgraded to 3.6.2 and continue to see the
same problem. I will move forward with looking into this library issue but
I'm sure what I expect to find.

On Fri, Oct 14, 2016 at 10:16 AM, Andrew Bell 
wrote:

> On Fri, Oct 14, 2016 at 9:04 AM, Randy Turner 
> wrote:
>
>> Hello! I've been running into a frustrating issue on and off for the past
>> year. The project will build the source files correctly but when it comes
>> to linking the executables, I always get the same error. The specific file
>> varies, but the failure mode is always the same. For example:
>>
>> 
>> "C:\\Users\\User\\AppData\\Local\\Temp\\", line
>> xxx: error #10008-D: cannot find file
>> "C:/Repos/operatingsystem/CMakeFiles/nvm_validate_ierator.di
>> r/os/nvm/nvm_validate_iterator.c.obj"
>>
>> As you can see, the file path is missing a "t" in the first occurrence of
>> the word "iterator" and so that file definitely does not exist. A file
>> exists in the location with correct spelling, but somehow that hardcoded
>> path in that temporary file has dropped a letter. The specific letter that
>> gets dropped varies along with which file is allegedly missing. We noticed
>> that requiring people to store the repository in their root directory
>> greatly cut down on the occurrence of this issue but it is returning with
>> more frequency as of late. Once it occurs once, CMake builds are never
>> successful again and the only way that I have been able to completely clear
>> the problem has been to reinstall Windows and set up the build environment
>> again.
>>
>
> This seems really, really strange.  Have to reinstall Windows?  What about
> just using another build directory?  It sure *seems* like there's some
> problem in your CMakeFiles.txt where the way the filepath is being
> constructed is incorrect.  But I don't think you've really provided enough
> information to determine the problem.  Where does the name of the object
> file come from?
>
> --
> Andrew Bell
> andrew.bell...@gmail.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:
http://public.kitware.com/mailman/listinfo/cmake

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-238-g248527e

[Brad King]

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  248527ed930ea69f9d6953a47b708044c48d5921 (commit)
   via  3b6f1587bed536e3d31e6665aff35aa27f5e79bc (commit)
  from  274ff520925deea9bf9532673c15b96616521615 (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=248527ed930ea69f9d6953a47b708044c48d5921
commit 248527ed930ea69f9d6953a47b708044c48d5921
Merge: 274ff52 3b6f158
Author: Brad King 
AuthorDate: Mon Oct 17 10:15:15 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:15:15 2016 -0400

Merge topic 'refactor-folder-name-retrieval'

3b6f1587 Factor IDE folder name retrieval out into helper method


---

Summary of changes:
 Source/cmGeneratorTarget.cxx  |   16 
 Source/cmGeneratorTarget.h|3 +++
 Source/cmGhsMultiTargetGenerator.cxx  |4 +---
 Source/cmGlobalGenerator.cxx  |2 +-
 Source/cmGlobalGenerator.h|3 ++-
 Source/cmGlobalGhsMultiGenerator.cxx  |6 +-
 Source/cmGlobalVisualStudio7Generator.cxx |4 ++--
 Source/cmGlobalXCodeGenerator.cxx |4 ++--
 8 files changed, 28 insertions(+), 14 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-564-gc7f69a3

[Brad King]

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, next has been updated
   via  c7f69a3ee6d693e6fb6d563d7914afb12abdca82 (commit)
   via  188c762f8a5f690708109a3cb8d44693e599adb1 (commit)
   via  9a2048f1ea6687530e209992c3f5eafcbc02b2a9 (commit)
   via  248527ed930ea69f9d6953a47b708044c48d5921 (commit)
   via  274ff520925deea9bf9532673c15b96616521615 (commit)
   via  69be82394dcd9044c9aa392e0aa078a6e09ec460 (commit)
   via  5fdee6d402798545280f8dc2955b21d4fe61605c (commit)
   via  6f7c02ab0ac83fcb23f147a41902d5ac97d4a299 (commit)
   via  0cbe2edb23d581233c518beafe92a2c9d4f529ac (commit)
  from  b09b42069ca7cfe9510fafbf8e5282a49bb45e93 (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=c7f69a3ee6d693e6fb6d563d7914afb12abdca82
commit c7f69a3ee6d693e6fb6d563d7914afb12abdca82
Merge: b09b420 188c762
Author: Brad King 
AuthorDate: Mon Oct 17 10:15:33 2016 -0400
Commit: Brad King 
CommitDate: Mon Oct 17 10:15:33 2016 -0400

Merge branch 'master' into next


---

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
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-255-g9a2048f

[Brad King]

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  9a2048f1ea6687530e209992c3f5eafcbc02b2a9 (commit)
   via  b59b6dd9d27de7839c7b23a3094db33298038896 (commit)
   via  b4234e977f65ee7df8adcd3888706dfd0dda (commit)
   via  f796e1b6f6984b200453a13e6b8640353ff9488b (commit)
   via  c75a9d660169ddd1e7be57486d3813ca73886b55 (commit)
   via  46ad0d2183230d1af93242efbdcce20d55514efb (commit)
   via  2628dec12cb22546d2a21032f53fb0ef096faec8 (commit)
   via  315b9a31895ca6bb26eba12bff3a0fe9cd37568a (commit)
   via  d5feb5b34cd9f595bf42aa934738b918785e3e87 (commit)
   via  efba22e1deebcfc3924d5f14c026104eb4b62d28 (commit)
   via  b29425f7aafe07eff526f3c7defb317856b72984 (commit)
   via  f009d8f5e2e4007b93494c5d22ba25b41a4872a1 (commit)
   via  6cd27a853a1c77e5da0a9a14140284a7674cf18c (commit)
   via  8b0e4795687a2ea289d1313db24d75bcf3cd13bc (commit)
   via  88016e2e9f13d60c4a0b88fb64ffd802a2d9e534 (commit)
   via  be87cb0c444595fa1970e257031252669c201d3e (commit)
   via  425cd1670fdd40b752af71e5f28952ae4fcec4ac (commit)
  from  248527ed930ea69f9d6953a47b708044c48d5921 (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=9a2048f1ea6687530e209992c3f5eafcbc02b2a9
commit 9a2048f1ea6687530e209992c3f5eafcbc02b2a9
Merge: 248527e b59b6dd
Author: Brad King 
AuthorDate: Mon Oct 17 10:15:17 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:15:17 2016 -0400

Merge topic 'extract-cmRulePlaceholderExpander'

b59b6dd9 cmRulePlaceholderExpander: Port clients to direct-use
b423 cmRulePlaceholderExpander: Extract from cmLocalGenerator
f796e1b6 cmLocalGenerator: Move memset to cxx file
c75a9d66 cmLocalGenerator: Use strings instead of a Target in rule 
replacement
46ad0d21 cmLocalGenerator: Use a converter in rule replacement API
2628dec1 cmLocalGenerator: Store variable replacements as state
315b9a31 cmLocalGenerator: Merge loops which populate mapping
d5feb5b3 cmLocalGenerator: Populate variable mapping for all replacements
efba22e1 cmLocalGenerator: Extract compiler option replacement from loop
b29425f7 cmLocalGenerator: Populate a container of mappings for replacements
f009d8f5 cmLocalGenerator: Move compiler option handling to be more direct
6cd27a85 cmLocalGenerator: Move variable to where it can be used easily
8b0e4795 cmLocalGenerator: Use the language from the compiler container
88016e2e cmLocalGenerator: Introduce a container of compiler names
be87cb0c cmLocalGenerator: Simplify loop with range algorithm
425cd167 cmLocalGenerator: Remove the launcher from RuleVariables


---

Summary of changes:
 Source/CMakeLists.txt  |2 +
 Source/cmLocalGenerator.cxx|  412 +---
 Source/cmLocalGenerator.h  |   63 +---
 Source/cmLocalNinjaGenerator.cxx   |   28 +-
 Source/cmLocalNinjaGenerator.h |8 +-
 Source/cmLocalUnixMakefileGenerator3.cxx   |   17 +-
 Source/cmMakefileExecutableTargetGenerator.cxx |   27 +-
 Source/cmMakefileLibraryTargetGenerator.cxx|   40 ++-
 Source/cmMakefileTargetGenerator.cxx   |   23 +-
 Source/cmNinjaNormalTargetGenerator.cxx|   24 +-
 Source/cmNinjaTargetGenerator.cxx  |   41 ++-
 Source/cmRulePlaceholderExpander.cxx   |  304 +
 Source/cmRulePlaceholderExpander.h |   83 +
 bootstrap  |1 +
 14 files changed, 634 insertions(+), 439 deletions(-)
 create mode 100644 Source/cmRulePlaceholderExpander.cxx
 create mode 100644 Source/cmRulePlaceholderExpander.h


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-551-gf014b34

[Brad King]

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, next has been updated
   via  f014b3408a942ed1be8e0bbe7767ec8e6f092f5f (commit)
   via  e8bafb6fcbb46bad4dfcb8dab1347c8e5f9a8090 (commit)
  from  a23f4f0666fdbfb7ab75635f62e216b5d5d158d0 (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=f014b3408a942ed1be8e0bbe7767ec8e6f092f5f
commit f014b3408a942ed1be8e0bbe7767ec8e6f092f5f
Merge: a23f4f0 e8bafb6
Author: Brad King 
AuthorDate: Mon Oct 17 10:05:06 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:05:06 2016 -0400

Merge topic 'osx-no-deployment-target-on-cross-compile' into next

e8bafb6f OS X: Do not try to set deployment target when cross-compiling


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e8bafb6fcbb46bad4dfcb8dab1347c8e5f9a8090
commit e8bafb6fcbb46bad4dfcb8dab1347c8e5f9a8090
Author: Gregor Jasny 
AuthorDate: Sun Oct 16 20:56:36 2016 +0200
Commit: Brad King 
CommitDate: Mon Oct 17 10:02:17 2016 -0400

OS X: Do not try to set deployment target when cross-compiling

The change in commit v3.4.0-rc2~6^2 (Xcode: Adjust deployment target SDK
version to host version, 2015-10-11) does not make sense when
cross-compiling.  Make it conditional to fix this regression in some
cross-compiling cases.

Closes: #16355

diff --git a/Modules/Platform/Darwin-Initialize.cmake 
b/Modules/Platform/Darwin-Initialize.cmake
index 427909d..39374e1 100644
--- a/Modules/Platform/Darwin-Initialize.cmake
+++ b/Modules/Platform/Darwin-Initialize.cmake
@@ -90,7 +90,7 @@ elseif("${CMAKE_GENERATOR}" MATCHES Xcode
   endif()
 endforeach()
 
-if(NOT CMAKE_OSX_DEPLOYMENT_TARGET AND _CURRENT_OSX_VERSION VERSION_LESS 
_CMAKE_OSX_DEPLOYMENT_TARGET)
+if(NOT CMAKE_CROSSCOMPILING AND NOT CMAKE_OSX_DEPLOYMENT_TARGET AND 
_CURRENT_OSX_VERSION VERSION_LESS _CMAKE_OSX_DEPLOYMENT_TARGET)
   set(CMAKE_OSX_DEPLOYMENT_TARGET ${_CURRENT_OSX_VERSION} CACHE STRING
 "Minimum OS X version to target for deployment (at runtime); newer 
APIs weak linked. Set to empty string for default value." FORCE)
 endif()

---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-232-g69be823

[Brad King]

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  69be82394dcd9044c9aa392e0aa078a6e09ec460 (commit)
   via  e8bafb6fcbb46bad4dfcb8dab1347c8e5f9a8090 (commit)
  from  5fdee6d402798545280f8dc2955b21d4fe61605c (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=69be82394dcd9044c9aa392e0aa078a6e09ec460
commit 69be82394dcd9044c9aa392e0aa078a6e09ec460
Merge: 5fdee6d e8bafb6
Author: Brad King 
AuthorDate: Mon Oct 17 10:15:02 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:15:02 2016 -0400

Merge topic 'osx-no-deployment-target-on-cross-compile'

e8bafb6f OS X: Do not try to set deployment target when cross-compiling


---

Summary of changes:
 Modules/Platform/Darwin-Initialize.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-228-g6f7c02a

[Brad King]

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  6f7c02ab0ac83fcb23f147a41902d5ac97d4a299 (commit)
   via  78b00f1d10f5bb0a152d7825ef554836b52f7977 (commit)
  from  0cbe2edb23d581233c518beafe92a2c9d4f529ac (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=6f7c02ab0ac83fcb23f147a41902d5ac97d4a299
commit 6f7c02ab0ac83fcb23f147a41902d5ac97d4a299
Merge: 0cbe2ed 78b00f1
Author: Brad King 
AuthorDate: Mon Oct 17 10:14:55 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:14:55 2016 -0400

Merge topic 'doc-clarify-ctest-APPEND'

78b00f1d Help: Clarify `ctest_*` APPEND option behavior


---

Summary of changes:
 Help/command/ctest_build.rst |4 +++-
 Help/command/ctest_configure.rst |4 +++-
 Help/command/ctest_coverage.rst  |4 +++-
 Help/command/ctest_test.rst  |4 +++-
 4 files changed, 12 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-236-g274ff52

[Brad King]

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  274ff520925deea9bf9532673c15b96616521615 (commit)
   via  70e268da3e5f8e00bdf065786cd685a9660fe1c4 (commit)
   via  47092d3e809be971264a8d5416ff3cb9255f6565 (commit)
   via  7db671a14374fdbfb8ae87ab9618bca111f4e8a5 (commit)
  from  69be82394dcd9044c9aa392e0aa078a6e09ec460 (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=274ff520925deea9bf9532673c15b96616521615
commit 274ff520925deea9bf9532673c15b96616521615
Merge: 69be823 70e268d
Author: Brad King 
AuthorDate: Mon Oct 17 10:15:12 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:15:12 2016 -0400

Merge topic 'cmcldeps-more-safety'

70e268da cmcldeps: prefer the /TC flag
47092d3e cmcldeps: append strings as strings
7db671a1 cmcldeps: search for single-byte strings as characters


---

Summary of changes:
 Source/cmcldeps.cxx |   11 +++
 1 file changed, 3 insertions(+), 8 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-275-g188c762

[Brad King]

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  188c762f8a5f690708109a3cb8d44693e599adb1 (commit)
   via  cef59bb8bac6b6d38025cc492235953c5ff7654b (commit)
   via  0d57b07ad99cefc5df9e65d6c14aeaddf5d64b88 (commit)
   via  c3fb0d95ad114c9f9680e885c4c2263b43c437dc (commit)
   via  fa9dbc56a15aec71ac2eda7890efd0116797f373 (commit)
   via  848ae2a663ef83e059561d94b33d551154642231 (commit)
   via  a0a720e6a70133e361762101ce69a0b3f1ab244d (commit)
   via  637e3f3ee131cf30f7337db06314f4a1af22c245 (commit)
   via  05251e6d80b03ae14d6a89765f14c2eb10979bd4 (commit)
   via  fbf1721c94b40ea86eeb183a1916f2066eb64bdc (commit)
   via  390a7d8647c13570dc6416fceb884dc51c8ef6f9 (commit)
   via  e32a6bdd990571bafb8537110128d28a593150b7 (commit)
   via  7863fba1f6f37db2f75834d0d6a3fbbc680e731c (commit)
   via  8096682e4edb542a48bbf66c085911db5f00be02 (commit)
   via  7d57c1a2c926011bc2e4c7a65b802763ec4efbcb (commit)
   via  a55cac4ba475ff61da4146272246512a52247323 (commit)
   via  705fcf522be16eee03b1757274b23ada6547e6bd (commit)
   via  1fb6f672bd2bd041edb772b0627278383a00fb62 (commit)
   via  60b3f216c18aa317656433bcc0b724e6abd8d02f (commit)
   via  aaa5dbbf64392dad518668ac1d046d624dac41f3 (commit)
  from  9a2048f1ea6687530e209992c3f5eafcbc02b2a9 (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=188c762f8a5f690708109a3cb8d44693e599adb1
commit 188c762f8a5f690708109a3cb8d44693e599adb1
Merge: 9a2048f cef59bb
Author: Brad King 
AuthorDate: Mon Oct 17 10:15:21 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:15:21 2016 -0400

Merge topic 'extract-computed-target-properties'

cef59bb8 cmTarget: Implement GetProperty in terms of cmState::Snapshot
0d57b07a cmTarget: Group code for checking written properties together
c3fb0d95 cmTarget: Move sanity checks and computed property access to 
callers
fa9dbc56 cmGeneratorTarget: Implement cmTargetPropertyComputer interface
848ae2a6 cmTargetPropertyComputer: Template some methods on the Target
a0a720e6 cm{,Generator}Target: Add global generator accessors
637e3f3e cmTargetPropertyComputer: Unify whitelist handling from cmTarget
05251e6d cmTargetPropertyComputer: Move whitelist check from cmTarget
fbf1721c cmTargetPropertyComputer: Extract into new files
390a7d86 cmTargetPropertyComputer: Implement GetProperty without cmMakefile
e32a6bdd cmListFileBacktrace: Add a method to retrieve the Bottom of a 
snapshot
7863fba1 cmTarget: Extract GetLocation method
8096682e cmTarget: Extract GetSources method
7d57c1a2 cmTarget: Extract location computation methods
a55cac4b cmTarget: Split property computation into separate class
705fcf52 cmTarget: Move IMPORTED check to callers
...


---

Summary of changes:
 Source/CMakeLists.txt  |2 +
 Source/cmGeneratorTarget.cxx   |   57 ++-
 Source/cmGeneratorTarget.h |4 +
 Source/cmGetPropertyCommand.cxx|   15 +-
 Source/cmGetTargetPropertyCommand.cxx  |   13 +-
 Source/cmListFileCache.h   |2 +
 Source/cmTarget.cxx|  458 
 Source/cmTarget.h  |   19 +-
 Source/cmTargetPropertyComputer.cxx|   99 +
 Source/cmTargetPropertyComputer.h  |  110 +
 .../TARGET_PROPERTY-LOCATION-stderr.txt|4 +-
 bootstrap  |1 +
 12 files changed, 493 insertions(+), 291 deletions(-)
 create mode 100644 Source/cmTargetPropertyComputer.cxx
 create mode 100644 Source/cmTargetPropertyComputer.h


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-230-g5fdee6d

[Brad King]

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  5fdee6d402798545280f8dc2955b21d4fe61605c (commit)
   via  c05d9b0569a2a2c43db6f09a53fed7b54ae97d32 (commit)
  from  6f7c02ab0ac83fcb23f147a41902d5ac97d4a299 (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=5fdee6d402798545280f8dc2955b21d4fe61605c
commit 5fdee6d402798545280f8dc2955b21d4fe61605c
Merge: 6f7c02a c05d9b0
Author: Brad King 
AuthorDate: Mon Oct 17 10:14:59 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:14:59 2016 -0400

Merge topic 'doc-math-EXPR'

c05d9b05 Help: Fix math(EXPR) documentation formatting


---

Summary of changes:
 Help/command/math.rst |9 +
 1 file changed, 5 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-568-ga954000

[Brad King]

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, next has been updated
   via  a9540002c5101e533e1896a4150462f20ceac68f (commit)
   via  2810e561829b0db36961442f0332939e1b74ccdf (commit)
   via  834f52a6f41ec5ae8429afa2d374f96458963cf3 (commit)
   via  7aaed265ade4c3b38967e83095497280a7a55153 (commit)
  from  c7f69a3ee6d693e6fb6d563d7914afb12abdca82 (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=a9540002c5101e533e1896a4150462f20ceac68f
commit a9540002c5101e533e1896a4150462f20ceac68f
Merge: c7f69a3 2810e56
Author: Brad King 
AuthorDate: Mon Oct 17 10:18:59 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:18:59 2016 -0400

Merge topic 'math-EXPR-unary' into next

2810e561 math(EXPR): Add support for unary `+` and `-` expressions
834f52a6 cmExprParser: Revise indentation style to match rest of CMake
7aaed265 cmExprParser: Port to bison 3


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2810e561829b0db36961442f0332939e1b74ccdf
commit 2810e561829b0db36961442f0332939e1b74ccdf
Author: Brad King 
AuthorDate: Fri Oct 14 15:28:51 2016 -0400
Commit: Brad King 
CommitDate: Fri Oct 14 15:35:15 2016 -0400

math(EXPR): Add support for unary `+` and `-` expressions

Closes: #8996

diff --git a/Help/release/dev/math-EXPR-unary.rst 
b/Help/release/dev/math-EXPR-unary.rst
new file mode 100644
index 000..d4af15b0
--- /dev/null
+++ b/Help/release/dev/math-EXPR-unary.rst
@@ -0,0 +1,5 @@
+math-EXPR-unary
+---
+
+* The :command:`math(EXPR)` command gained support for unary
+  ``+`` and ``-`` expressions.
diff --git a/Source/cmExprParser.cxx b/Source/cmExprParser.cxx
index 6eef2db..d11d0b6 100644
--- a/Source/cmExprParser.cxx
+++ b/Source/cmExprParser.cxx
@@ -422,18 +422,18 @@ union yyalloc
 #endif /* !YYCOPY_NEEDED */
 
 /* YYFINAL -- State number of the termination state.  */
-#define YYFINAL  12
+#define YYFINAL  17
 /* YYLAST -- Last index in YYTABLE.  */
-#define YYLAST   25
+#define YYLAST   30
 
 /* YYNTOKENS -- Number of terminals.  */
 #define YYNTOKENS  17
 /* YYNNTS -- Number of nonterminals.  */
-#define YYNNTS  9
+#define YYNNTS  10
 /* YYNRULES -- Number of rules.  */
-#define YYNRULES  20
+#define YYNRULES  23
 /* YYNSTATES -- Number of states.  */
-#define YYNSTATES  34
+#define YYNSTATES  39
 
 /* YYTRANSLATE[YYX] -- Symbol number corresponding to YYX as returned
by yylex, with out-of-bounds checking.  */
@@ -483,7 +483,7 @@ static const yytype_uint8 yyrline[] =
 {
0,70,70,75,78,83,86,91,94,99,
  102,   105,   110,   113,   116,   121,   124,   127,   130,   135,
- 138
+ 138,   141,   146,   149
 };
 #endif
 
@@ -496,7 +496,7 @@ static const char *const yytname[] =
   "exp_DIVIDE", "exp_MOD", "exp_SHIFTLEFT", "exp_SHIFTRIGHT",
   "exp_OPENPARENT", "exp_CLOSEPARENT", "exp_OR", "exp_AND", "exp_XOR",
   "exp_NOT", "exp_NUMBER", "$accept", "start", "exp", "bitwiseor",
-  "bitwisexor", "bitwiseand", "shift", "term", "factor", YY_NULLPTR
+  "bitwisexor", "bitwiseand", "shift", "term", "unary", "factor", YY_NULLPTR
 };
 #endif
 
@@ -510,10 +510,10 @@ static const yytype_uint16 yytoknum[] =
 };
 # endif
 
-#define YYPACT_NINF -14
+#define YYPACT_NINF -8
 
 #define yypact_value_is_default(Yystate) \
-  (!!((Yystate) == (-14)))
+  (!!((Yystate) == (-8)))
 
 #define YYTABLE_NINF -1
 
@@ -524,10 +524,10 @@ static const yytype_uint16 yytoknum[] =
  STATE-NUM.  */
 static const yytype_int8 yypact[] =
 {
- -10,   -10,   -14,18, 7, 6, 8, 2, 1,-4,
- -14, 3,   -14,   -10,   -10,   -10,   -10,   -10,   -10,   -10,
- -10,   -10,   -10,   -14, 6, 8, 2, 1, 1,-4,
-  -4,   -14,   -14,   -14
+   0, 0, 0, 0,-8, 2,-7,-5, 8, 3,
+  10, 1,-8,-8,-8,-8, 6,-8, 0, 0,
+   0, 0, 0, 0, 0, 0, 0, 0,-8,-5,
+   8, 3,10,10, 1, 1,-8,-8,-8
 };
 
   /* YYDEFACT[STATE-NUM] -- Default reduction number in state STATE-NUM.
@@ -535,22 +535,22 @@ static const yytype_int8 yypact[] =
  means the default is an error.  */
 static const yytype_uint8 yydefact[] =
 {
-   0, 0,19, 0, 2, 3, 5, 7, 9,12,
-  15, 0, 1, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,20, 4, 6, 8,10,11,13,
-  14,16,17,18
+   

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-555-gb09b420

[Brad King]

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, next has been updated
   via  b09b42069ca7cfe9510fafbf8e5282a49bb45e93 (commit)
   via  3b6f1587bed536e3d31e6665aff35aa27f5e79bc (commit)
  from  fddd06191565ba067f82b0baa6f33beabe78ccab (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=b09b42069ca7cfe9510fafbf8e5282a49bb45e93
commit b09b42069ca7cfe9510fafbf8e5282a49bb45e93
Merge: fddd061 3b6f158
Author: Brad King 
AuthorDate: Mon Oct 17 10:08:17 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:08:17 2016 -0400

Merge topic 'refactor-folder-name-retrieval' into next

3b6f1587 Factor IDE folder name retrieval out into helper method


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3b6f1587bed536e3d31e6665aff35aa27f5e79bc
commit 3b6f1587bed536e3d31e6665aff35aa27f5e79bc
Author: Gregor Jasny 
AuthorDate: Tue Aug 30 20:55:37 2016 +0200
Commit: Brad King 
CommitDate: Mon Oct 17 10:06:18 2016 -0400

Factor IDE folder name retrieval out into helper method

Add a `cmGeneratorTarget::GetEffectiveFolderName` helper to abstract
lookup of the `FOLDER` property in combination with checking for
generator support of folders.

diff --git a/Source/cmGeneratorTarget.cxx b/Source/cmGeneratorTarget.cxx
index 7eb0ebf..f11149a 100644
--- a/Source/cmGeneratorTarget.cxx
+++ b/Source/cmGeneratorTarget.cxx
@@ -1767,6 +1767,22 @@ std::string cmGeneratorTarget::GetMacContentDirectory(
   return fpath;
 }
 
+std::string cmGeneratorTarget::GetEffectiveFolderName() const
+{
+  std::string effectiveFolder;
+
+  if (!this->GlobalGenerator->UseFolderProperty()) {
+return effectiveFolder;
+  }
+
+  const char* targetFolder = this->GetProperty("FOLDER");
+  if (targetFolder) {
+effectiveFolder += targetFolder;
+  }
+
+  return effectiveFolder;
+}
+
 cmGeneratorTarget::CompileInfo const* cmGeneratorTarget::GetCompileInfo(
   const std::string& config) const
 {
diff --git a/Source/cmGeneratorTarget.h b/Source/cmGeneratorTarget.h
index 68ffd5c..9382726 100644
--- a/Source/cmGeneratorTarget.h
+++ b/Source/cmGeneratorTarget.h
@@ -220,6 +220,9 @@ public:
   std::string GetMacContentDirectory(const std::string& config = CM_NULLPTR,
  bool implib = false) const;
 
+  /** @return folder prefix for IDEs. */
+  std::string GetEffectiveFolderName() const;
+
   cmTarget* Target;
   cmMakefile* Makefile;
   cmLocalGenerator* LocalGenerator;
diff --git a/Source/cmGhsMultiTargetGenerator.cxx 
b/Source/cmGhsMultiTargetGenerator.cxx
index 5fbaea4..3154f8d 100644
--- a/Source/cmGhsMultiTargetGenerator.cxx
+++ b/Source/cmGhsMultiTargetGenerator.cxx
@@ -44,9 +44,7 @@ cmGhsMultiTargetGenerator::~cmGhsMultiTargetGenerator()
 std::string cmGhsMultiTargetGenerator::GetRelBuildFilePath(
   const cmGeneratorTarget* target)
 {
-  std::string output;
-  char const* folderProp = target->GetProperty("FOLDER");
-  output = NULL == folderProp ? "" : folderProp;
+  std::string output = target->GetEffectiveFolderName();
   cmSystemTools::ConvertToUnixSlashes(output);
   if (!output.empty()) {
 output += "/";
diff --git a/Source/cmGlobalGenerator.cxx b/Source/cmGlobalGenerator.cxx
index 1aa6af1..7d0c2da 100644
--- a/Source/cmGlobalGenerator.cxx
+++ b/Source/cmGlobalGenerator.cxx
@@ -2377,7 +2377,7 @@ const char* 
cmGlobalGenerator::GetPredefinedTargetsFolder()
   return "CMakePredefinedTargets";
 }
 
-bool cmGlobalGenerator::UseFolderProperty()
+bool cmGlobalGenerator::UseFolderProperty() const
 {
   const char* prop =
 this->GetCMakeInstance()->GetState()->GetGlobalProperty("USE_FOLDERS");
diff --git a/Source/cmGlobalGenerator.h b/Source/cmGlobalGenerator.h
index 38eaa76..c3498e0 100644
--- a/Source/cmGlobalGenerator.h
+++ b/Source/cmGlobalGenerator.h
@@ -334,6 +334,8 @@ public:
   i.e. "Can I build Debug and Release in the same tree?" */
   virtual bool IsMultiConfig() const { return false; }
 
+  virtual bool UseFolderProperty() const;
+
   std::string GetSharedLibFlagsForLanguage(std::string const& lang) const;
 
   /** Generate an .rule file path for a given command output.  */
@@ -463,7 +465,6 @@ protected:
 std::string const& name) const;
 
   const char* GetPredefinedTargetsFolder();
-  virtual bool UseFolderProperty();
 
 private:
 #if defined(CMAKE_BUILD_WITH_CMAKE)
diff --git a/Source/cmGlobalGhsMultiGenerator.cxx 
b/Source/cmGlobalGhsMultiGenerator.cxx
index 0eac338..d4ae677 100644
--- a/Source/cmGlobalGhsMultiGenerator.cxx
+++ b/Source/cmGlobalGhsMultiGenerator.cxx
@@ -439,11 

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-553-gfddd061

[Brad King]

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, next has been updated
   via  fddd06191565ba067f82b0baa6f33beabe78ccab (commit)
   via  e6ec80ae7c193b318b02c30f7a8f0355635ee170 (commit)
  from  f014b3408a942ed1be8e0bbe7767ec8e6f092f5f (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=fddd06191565ba067f82b0baa6f33beabe78ccab
commit fddd06191565ba067f82b0baa6f33beabe78ccab
Merge: f014b34 e6ec80a
Author: Brad King 
AuthorDate: Mon Oct 17 10:06:12 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Oct 17 10:06:12 2016 -0400

Merge topic 'refactor-folder-name-retrieval' into next

e6ec80ae fixup! Refactor IDE folder name retrieval into 
GetEffectiveFolderName()


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e6ec80ae7c193b318b02c30f7a8f0355635ee170
commit e6ec80ae7c193b318b02c30f7a8f0355635ee170
Author: Brad King 
AuthorDate: Mon Oct 17 10:05:58 2016 -0400
Commit: Brad King 
CommitDate: Mon Oct 17 10:05:58 2016 -0400

fixup! Refactor IDE folder name retrieval into GetEffectiveFolderName()

diff --git a/Source/cmGeneratorTarget.cxx b/Source/cmGeneratorTarget.cxx
index eb9f419..f11149a 100644
--- a/Source/cmGeneratorTarget.cxx
+++ b/Source/cmGeneratorTarget.cxx
@@ -1769,18 +1769,18 @@ std::string cmGeneratorTarget::GetMacContentDirectory(
 
 std::string cmGeneratorTarget::GetEffectiveFolderName() const
 {
-std::string effectiveFolder;
+  std::string effectiveFolder;
 
-if (!this->GlobalGenerator->UseFolderProperty()) {
-return effectiveFolder;
-}
+  if (!this->GlobalGenerator->UseFolderProperty()) {
+return effectiveFolder;
+  }
 
-const char* targetFolder = this->GetProperty("FOLDER");
-if (targetFolder) {
-effectiveFolder += targetFolder;
-}
+  const char* targetFolder = this->GetProperty("FOLDER");
+  if (targetFolder) {
+effectiveFolder += targetFolder;
+  }
 
-return effectiveFolder;
+  return effectiveFolder;
 }
 
 cmGeneratorTarget::CompileInfo const* cmGeneratorTarget::GetCompileInfo(

---

Summary of changes:
 Source/cmGeneratorTarget.cxx |   18 +-
 1 file changed, 9 insertions(+), 9 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [cmake-developers] Java_INCLUDE_DIRS not populated by FindJava.cmake

[Ben Boeckel]

On Mon, Oct 17, 2016 at 15:32:06 +1100, Craig Scott wrote:
> In case anyone is wondering, the use case for me is when implementing a
> SWIG custom command to generate java wrappers, the jni.h header needs to be
> found by the generated sources.

There's FindJNI for that.

--Ben
-- 

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:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] Java_INCLUDE_DIRS not populated by FindJava.cmake

[Brad King]

On 10/17/2016 12:32 AM, Craig Scott wrote:
> Unless I'm missing something, it would seem that even though
> the documentation says FindJava.cmake sets Java_INCLUDE_DIRS

The documentation was wrong and was fixed in 3.7:

 FindJava: Do not document variables we do not provide
 https://gitlab.kitware.com/cmake/cmake/commit/10a7459a

-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:
http://public.kitware.com/mailman/listinfo/cmake-developers

[CMake] Support for Visual Studio Linux cross-compiling extension

[Floh]

Hi,

Microsoft has added support for remote-compiling and -debugging on
Linux from within Visual Studio through an official VS extension:
https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual-c-for-linux-development/

My question: is it already possible to generate a Visual Studio
solution for this scenario? If not, is support for this planned,
similar to the Android cross-compile scenario?

It would be nice if I could generate such a solution with (for instance):

cmake -G "Visual Studio 14" -DCMAKE_SYSTEM_NAME=VSLinux

I've been looking at the generated solution files, and the only
'interesting' part in the vxproj file seems to be this section:

---
  
{2e73db3c-a17c-4694-996c-2cca151ed9f2}
Linux
ConsoleApplication1
14.0
Linux
1.0
Generic
{D51BCBC9-82E9-4017-911E-C93873C4EA2B}
  
---

There seems to be a hardwired mapping between Visual Studio compiler
options and gcc/clang options, for instance setting optimization to
-O3 in the VS property dialog adds these lines to the vxproj file:

---
  

  Full

  
---

Cheers & thanks,
-Floh.
-- 

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:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Cannot get automoc to work properly with recommended Qt5 support method

[Alan W. Irwin]

On 2016-10-16 18:40-0700 Alan W. Irwin wrote:


To be explicit suppose you have some source code named fooqt.cpp
which contains

#include "barqt.h"

which declares some classes for the software package that refer to Q_OBJECT
and some classes that do not refer to Q_OBJECT.

What is the #include recipe to get automoc to work for this specific case?

In the next few hours I plan to try some #include variations allowed
by the ambiguities of the above documentation so I may eventually
answer my own question by these experiments.  But it would be nice to
get a definitive answer.


It turned out I could get it to work by specifying (at the end of
fooqt.cpp)

#include "moc_barqt.cpp"

However, it only looked in the directory where fooqt.cpp was located
for barqt.h, and a special twist for the PLplot case was barqt.h was
located in a separate directory so it could not find it.  I then tried
adding the appropriate -I directive to CMAKE_AUTOMOC_MOC_OPTIONS.
Note, this time I used the correct name of that variable (and not
AUTOMOC_MOC_OPTIONS like I used before.) So VERBOSE=1 output showed
moc being run properly with all the macros defined as well as that -I
directive.  However, it was run on the barqt.h in the same directory
where fooqt.cpp was located and failed because barqt.h only existed in
a separate directory.  I worked around this by temporarily deploying a
symlink, but that method won't work on Windows, and it may generate
name conflicts for the case of our other Qt5-related components
built in separate directories which also use this same header.

So is there a proper method to work with headers that that are used by
multiple software components in different directories?  If not, I
would consider that to be a big deficiency of the latest Qt5 support
method since this is not a problem for the old Qt5 support method.

By the way, even with the symlink workaround that allows automoc to
generate a moc command that actually works, the moc_barqt.cpp results
that are #included in fooqt.cpp generate two compiler errors when
fooqt.cpp is built.  So I will try to use my rudimentary C++ skills to
debug that issue going forward, and I may ask more questions
concerning those build issues if I cannot figure these build issues
out.

A general comment is this whole project to update to the latest Qt5
support method has been painful, and it is not done yet even for just
the one component I am testing it on so far.  And this pain is despite
the fact that the PLplot build worked smoothly (aside from the
plain/keyword target_link_libraries conflict that motivated this
update) before using the old Qt5 support method.  Less ambiguous
documentation of automoc that included how to deal with include files
that are #included by separate software components in different
directories would ease the pain of using the latest Qt5 support method
considerably.

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__
--

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:
http://public.kitware.com/mailman/listinfo/cmake