Re: [CMake] CMP0054 and CMake Modules

2015-09-21 Thread thoni56
I can't find a bug report on this. Is there one? 

Surely Cmake distributed modules should not generate this type of warnings.
Or am I misinterpreting the messages? 

I'm encountering numerous such problems/warnings in Cmake distributed
modules: 

CMake Warning (dev) at
/usr/share/cmake-3.3.1/Modules/CMakeParseImplicitLinkInfo.cmake:58 (if): 
  Policy CMP0054 is not set: Only interpret if() arguments as variables or 
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy 
  details.  Use the cmake_policy command to set the policy and suppress this 
  warning. 

  Quoted variables like "" will no longer be dereferenced when the policy is 
  set to NEW.  Since the policy is not set the OLD behavior will be used. 
Call Stack (most recent call first): 
  /usr/share/cmake-3.3.1/Modules/CMakeDetermineCompilerABI.cmake:80
(CMAKE_PARSE_IMPLICIT_LINK_INFO) 
  /usr/share/cmake-3.3.1/Modules/CMakeTestCXXCompiler.cmake:68
(CMAKE_DETERMINE_COMPILER_ABI) 
  src/CMakeLists.txt:2 (project) 
This warning is for project developers.  Use -Wno-dev to suppress it. 

CMake Warning (dev) at
/usr/share/cmake-3.3.1/Modules/CMakeParseImplicitLinkInfo.cmake:39 (if): 
  Policy CMP0054 is not set: Only interpret if() arguments as variables or 
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy 
  details.  Use the cmake_policy command to set the policy and suppress this 
  warning. 

  Quoted variables like "" will no longer be dereferenced when the policy is 
  set to NEW.  Since the policy is not set the OLD behavior will be used. 
Call Stack (most recent call first): 
  /usr/share/cmake-3.3.1/Modules/CMakeDetermineCompilerABI.cmake:80
(CMAKE_PARSE_IMPLICIT_LINK_INFO) 
  /usr/share/cmake-3.3.1/Modules/CMakeTestCXXCompiler.cmake:68
(CMAKE_DETERMINE_COMPILER_ABI) 
  src/CMakeLists.txt:2 (project) 
This warning is for project developers.  Use -Wno-dev to suppress it. 

CMake Warning (dev) at
/usr/share/cmake-3.3.1/Modules/CMakeParseImplicitLinkInfo.cmake:100
(elseif): 
  Policy CMP0054 is not set: Only interpret if() arguments as variables or 
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy 
  details.  Use the cmake_policy command to set the policy and suppress this 
  warning. 

  Quoted variables like "" will no longer be dereferenced when the policy is 
  set to NEW.  Since the policy is not set the OLD behavior will be used. 
Call Stack (most recent call first): 
  /usr/share/cmake-3.3.1/Modules/CMakeDetermineCompilerABI.cmake:80
(CMAKE_PARSE_IMPLICIT_LINK_INFO) 
  /usr/share/cmake-3.3.1/Modules/CMakeTestCXXCompiler.cmake:68
(CMAKE_DETERMINE_COMPILER_ABI) 
  src/CMakeLists.txt:2 (project) 
This warning is for project developers.  Use -Wno-dev to suppress it. 

-- Detecting CXX compile features 
-- Detecting CXX compile features - done 
CMake Warning (dev) at /usr/share/cmake-3.3.1/Modules/CTest.cmake:96 (if): 
  Policy CMP0054 is not set: Only interpret if() arguments as variables or 
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy 
  details.  Use the cmake_policy command to set the policy and suppress this 
  warning. 

  Quoted variables like "" will no longer be dereferenced when the policy is 
  set to NEW.  Since the policy is not set the OLD behavior will be used. 
Call Stack (most recent call first): 
  /usr/share/cmake-3.3.1/Modules/CTest.cmake:106 (SET_IF_SET_AND_NOT_SET) 
  cmake/Modules/MacroAddUnitTest.cmake:10 (include) 
  CMakeLists.txt:64 (include) 
This warning is for project developers.  Use -Wno-dev to suppress it. 

CMake Warning (dev) at /usr/share/cmake-3.3.1/Modules/CTest.cmake:251 (if): 
  Policy CMP0054 is not set: Only interpret if() arguments as variables or 
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy 
  details.  Use the cmake_policy command to set the policy and suppress this 
  warning. 

  Quoted variables like "" will no longer be dereferenced when the policy is 
  set to NEW.  Since the policy is not set the OLD behavior will be used. 
Call Stack (most recent call first): 
  cmake/Modules/MacroAddUnitTest.cmake:10 (include) 
  CMakeLists.txt:64 (include) 
This warning is for project developers.  Use -Wno-dev to suppress it. 



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/CMP0054-and-CMake-Modules-tp7590137p7591577.html
Sent from the CMake mailing list archive at Nabble.com.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:

Re: [CMake] CMP0054 and CMake Modules

2015-09-21 Thread Thomas Nilsson

Sorry, this turned out kind of brief, it was posted in context in Nabble.

I'm seeing this on Cygwin.

/Thomas


thoni56 
21 september 2015 09:37
I can't find a bug report on this. Is there one?

Surely Cmake distributed modules should not generate this type of 
warnings.

Or am I misinterpreting the messages?

I'm encountering numerous such problems/warnings in Cmake distributed
modules:

CMake Warning (dev) at
/usr/share/cmake-3.3.1/Modules/CMakeParseImplicitLinkInfo.cmake:58 (if):
Policy CMP0054 is not set: Only interpret if() arguments as variables or
keywords when unquoted. Run "cmake --help-policy CMP0054" for policy
details. Use the cmake_policy command to set the policy and suppress this
warning.

Quoted variables like "" will no longer be dereferenced when the 
policy is

set to NEW. Since the policy is not set the OLD behavior will be used.
Call Stack (most recent call first):
/usr/share/cmake-3.3.1/Modules/CMakeDetermineCompilerABI.cmake:80
(CMAKE_PARSE_IMPLICIT_LINK_INFO)
/usr/share/cmake-3.3.1/Modules/CMakeTestCXXCompiler.cmake:68
(CMAKE_DETERMINE_COMPILER_ABI)
src/CMakeLists.txt:2 (project)
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at
/usr/share/cmake-3.3.1/Modules/CMakeParseImplicitLinkInfo.cmake:39 (if):
Policy CMP0054 is not set: Only interpret if() arguments as variables or
keywords when unquoted. Run "cmake --help-policy CMP0054" for policy
details. Use the cmake_policy command to set the policy and suppress this
warning.

Quoted variables like "" will no longer be dereferenced when the 
policy is

set to NEW. Since the policy is not set the OLD behavior will be used.
Call Stack (most recent call first):
/usr/share/cmake-3.3.1/Modules/CMakeDetermineCompilerABI.cmake:80
(CMAKE_PARSE_IMPLICIT_LINK_INFO)
/usr/share/cmake-3.3.1/Modules/CMakeTestCXXCompiler.cmake:68
(CMAKE_DETERMINE_COMPILER_ABI)
src/CMakeLists.txt:2 (project)
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at
/usr/share/cmake-3.3.1/Modules/CMakeParseImplicitLinkInfo.cmake:100
(elseif):
Policy CMP0054 is not set: Only interpret if() arguments as variables or
keywords when unquoted. Run "cmake --help-policy CMP0054" for policy
details. Use the cmake_policy command to set the policy and suppress this
warning.

Quoted variables like "" will no longer be dereferenced when the 
policy is

set to NEW. Since the policy is not set the OLD behavior will be used.
Call Stack (most recent call first):
/usr/share/cmake-3.3.1/Modules/CMakeDetermineCompilerABI.cmake:80
(CMAKE_PARSE_IMPLICIT_LINK_INFO)
/usr/share/cmake-3.3.1/Modules/CMakeTestCXXCompiler.cmake:68
(CMAKE_DETERMINE_COMPILER_ABI)
src/CMakeLists.txt:2 (project)
This warning is for project developers. Use -Wno-dev to suppress it.

-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Warning (dev) at /usr/share/cmake-3.3.1/Modules/CTest.cmake:96 
(if):

Policy CMP0054 is not set: Only interpret if() arguments as variables or
keywords when unquoted. Run "cmake --help-policy CMP0054" for policy
details. Use the cmake_policy command to set the policy and suppress this
warning.

Quoted variables like "" will no longer be dereferenced when the 
policy is

set to NEW. Since the policy is not set the OLD behavior will be used.
Call Stack (most recent call first):
/usr/share/cmake-3.3.1/Modules/CTest.cmake:106 (SET_IF_SET_AND_NOT_SET)
cmake/Modules/MacroAddUnitTest.cmake:10 (include)
CMakeLists.txt:64 (include)
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at /usr/share/cmake-3.3.1/Modules/CTest.cmake:251 
(if):

Policy CMP0054 is not set: Only interpret if() arguments as variables or
keywords when unquoted. Run "cmake --help-policy CMP0054" for policy
details. Use the cmake_policy command to set the policy and suppress this
warning.

Quoted variables like "" will no longer be dereferenced when the 
policy is

set to NEW. Since the policy is not set the OLD behavior will be used.
Call Stack (most recent call first):
cmake/Modules/MacroAddUnitTest.cmake:10 (include)
CMakeLists.txt:64 (include)
This warning is for project developers. Use -Wno-dev to suppress it.



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/CMP0054-and-CMake-Modules-tp7590137p7591577.html

Sent from the CMake mailing list archive at Nabble.com.
Domen Vrankar 
26 mars 2015 10:48

ATM each CMake provided module has to set its own policies otherwise
policies from CMakeLists.txt minimum required version setting are
used.
Please file a bug report.

Thanks,
Domen
Jörg Kreuzberger 
26 mars 2015 10:29
Updated to cmake 3.2.1 from 3.0.0 and got several hints due to POLICY 
CMP0054 (handling of quoted variables)


i set the policy to new and changed my local cmake files.

But i also got a warning from CMake Modules like FindMFC.cmake (Line 39).

do i make 

[CMake] How to create a custom solution with Visual Studio 2010 generator?

2015-09-21 Thread Golebiewski, Jakub
Hi,

I'm trying to create a solution with custom set of projects (in VS sense) for 
Visual Studio 2010.
I have a top level CMakeLists.txt with PROJECT() declared and then several 
CMakeLists.txt below in a tree also with PROJECT() in each of them.
However for lower level PROJECT() directives I get all the targets that I 
specify in CMakeLists.txt and all the targets that they depend on.

My goal is to have a solution only with a specific set of targets, without 
dependencies.

Is there a  way to do that in cmake?

Thanks for help,
Jakub

**
This e-mail and any attachments thereto may contain confidential information 
and/or information protected by intellectual property rights for the exclusive 
attention of the intended addressees named above. If you have received this 
transmission in error, please immediately notify the sender by return e-mail 
and delete this message and its attachments. Unauthorized use, copying or 
further full or partial distribution of this e-mail or its contents is 
prohibited.
**
-- 

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] CMP0054 and CMake Modules

2015-09-21 Thread Nils Gladitz

On 09/21/2015 09:37 AM, thoni56 wrote:

   Quoted variables like "" will no longer be dereferenced when the policy is


You apparently have a variable whose name is the empty string.

With the old (pre CMP0054) behavior this will break comparisons with 
empty strings take e.g.


set("" foobar)
set(MYVAR foobar)

if(MYVAR STREQUAL "")
message("unexpectedly true")
endif()

Where the if() comparison with old behavior will unexpectedly (for most 
authors of such conditions) evaluate true.


With CMP0054's new behavior the same condition will evaluate false.

Since most cmake provided modules have to work with both the old and new 
behavior a common work around is e.g.


if("x${MYVAR}" STREQUAL "x")

This workaround however only works if by convention there are no 
variables starting with a lower case x in their name.


I think by that same reasoning you should avoid defining variables whose 
name is the empty string.


Nils
--

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] Port from Debian to Windows: Include files not found

2015-09-21 Thread Randy Turner
Thanks for all of the input, everyone! Unfortunately the problem still
persists. I don't have much to report this morning. I've removed the calls
to build the assembly file and confirmed that it is an ASM vs C issue as
opposed to an ordering issue. It continued to attempt to build the C file
without calls to include relevant directories and fails at the first
include.

On Fri, Sep 18, 2015 at 3:49 PM, Pau Garcia i Quiles 
wrote:

> Hello,
>
> You may need something like this in the toolchain file:
>
> # search for programs in the build host directories
> SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
>
> # for libraries and headers in the target directories
> SET(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY BOTH)
> SET(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE BOTH)
>
> set(CMAKE_FIND_ROOT_PATH_MODE_PACKAGE ONLY)
>
>
> On Fri, Sep 18, 2015 at 7:22 PM, Randy Turner 
> wrote:
>
>> I am having trouble building a Code Composer Studio project with CMake.
>> Executing from the same directory in Linux compiles successfully, but in
>> Linux it fails to find any included files that aren't in the same directory
>> as the .c file that it's building. I can provide a relative path to help it
>> move on, but it will just fail to find the files referenced by that one.
>>
>> The very first #include of the project is  which is located in
>> the compiler's install files. As shown in my StackOVerflow question about
>> this issue (
>> http://stackoverflow.com/questions/32591626/cmake-header-files-cannot-be-opened)
>> I can confirm that the files are in the directory that is included in the
>> CMakeLists.txt file and can be found while CMake is executing, but fail to
>> be located by make. I am using MinGW's make, and using the commands make
>> and mingw32-make both ellicit the same result, "fatal error: could not open
>> source file "stdbool.h" (no directories in search list)."
>>
>> Is there something that I'm missing here? Is something else necessary
>> beyond using INCLUDE_DIRECTORIES for all of the directories in the project?
>>
>> --
>>
>> 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
>>
>
>
>
> --
> Pau Garcia i Quiles
> http://www.elpauer.org
> (Due to my workload, I may need 10 days to answer)
>
-- 

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] How to create a custom solution with Visual Studio 2010 generator?

2015-09-21 Thread Golebiewski, Jakub
This may be a solution, I will check this asap.

This should be clearer, I have something like this:

Main Project - PROJECT()
\Sub Project 1 - PROJECT()
   \target 1 - ADD_LIBRARY()
   \target 2 - ADD_LIBRARY()
\Sub Project 2 - PROJECT()
   \target 3 - ADD_LIBRARY()
   \target 4 - ADD_LIBRARY()
\Sub Project 3 - PROJECT()
   \target 5 - ADD_LIBRARY()
   \target 6 - ADD_LIBRARY()

Targets  5 and 6 depend on 1, 2, 3 and 4.

Now when I run cmake on Main Project I will get .sln files for Main Project and 
each Sub Project.
.sln file for Sub Project 3 will contain all the targets (So I will get .sln 
with projects for target 1 – 6 in VS terminology).
What I need to have is for Sub Project 3 to have only target 5 and target 6 in 
.sln without dependencies from other Sub Projects.

So I worry that with your solution I will get unknown targets error? Is there 
any way to ignore missing targets errors?

Thanks for help,
JG

-Original Message-
From: J Decker [mailto:d3c...@gmail.com]
Sent: Monday, September 21, 2015 4:50 PM
To: Golebiewski, Jakub
Cc: cmake@cmake.org
Subject: Re: [CMake] How to create a custom solution with Visual Studio 2010 
generator?

CMake's PROJECT directive maps to 'Solution'  (should only be one
project() per chain) ... use set( PROJECT projectname) and then reference 
${PROJECT} later instead of ${PROJECT_NAME} for easy conversion.

add_library, add_executable map to 'project'

from http://www.cmake.org/Wiki/CMake_Useful_Variables

you can wrap the projects you want to omit with If's

if( NOT MSVC10 )
   add_library( one I don't want in 2010) endif( NOT MSVC10 )




On Sun, Sep 20, 2015 at 11:20 PM, Golebiewski, Jakub 
 wrote:
> Hi,
>
>
>
> I’m trying to create a solution with custom set of projects (in VS
> sense) for Visual Studio 2010.
>
> I have a top level CMakeLists.txt with PROJECT() declared and then
> several CMakeLists.txt below in a tree also with PROJECT() in each of them.
>
> However for lower level PROJECT() directives I get all the targets
> that I specify in CMakeLists.txt and all the targets that they depend on.
>
>
>
> My goal is to have a solution only with a specific set of targets,
> without dependencies.
>
>
>
> Is there a  way to do that in cmake?
>
>
>
> Thanks for help,
>
> Jakub
>
>
> **
>  This e-mail and any attachments thereto may contain
> confidential information and/or information protected by intellectual
> property rights for the exclusive attention of the intended addressees
> named above. If you have received this transmission in error, please
> immediately notify the sender by return e-mail and delete this message
> and its attachments. Unauthorized use, copying or further full or
> partial distribution of this e-mail or its contents is prohibited.
> **
> 
>
> --
>
> 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

**
This e-mail and any attachments thereto may contain confidential information 
and/or information protected by intellectual property rights for the exclusive 
attention of the intended addressees named above. If you have received this 
transmission in error, please immediately notify the sender by return e-mail 
and delete this message and its attachments. Unauthorized use, copying or 
further full or partial distribution of this e-mail or its contents is 
prohibited.
**
-- 

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 

Re: [CMake] Continued issues in trying to get CMake working on OpenVMS

2015-09-21 Thread Custin, Jay (CSC Sw Middleware)
I will try adding that option and see what it may reveal... the output 
contained in the CMakeOutput.log and CMakeError.log offered nothing other than 
politely telling me the test failed.

-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Bill Hoffman
Sent: Monday, September 21, 2015 10:55 AM
To: cmake@cmake.org
Subject: Re: [CMake] Continued issues in trying to get CMake working on OpenVMS

On 9/21/2015 10:17 AM, Custin, Jay (CSC Sw Middleware) wrote:
> This gets made even more frustrating in that it appears that the 
> testing phase does a VERY good job cleaning up after itself...


So, the output should all be in CMakeOutput.log and CMakeError.log found in the 
build tree in the CMakeFiles directory.

If you want CMake not to delete the temp files you can use --debug-trycompile

http://www.cmake.org/cmake/help/v3.3/manual/cmake.1.html

-Bill

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
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 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] Continued issues in trying to get CMake working on OpenVMS

2015-09-21 Thread Bill Hoffman

On 9/21/2015 11:29 AM, Custin, Jay (CSC Sw Middleware) wrote:

I will try adding that option and see what it may reveal... the
output contained in the CMakeOutput.log and CMakeError.log offered
nothing other than politely telling me the test failed.


That is odd...  It should have the stderr/stdout.  There maybe some 
issue with that.  Can you send me those files off the list?


You may want to create a small project to test the flag.  Then use the 
bootstraped cmake to configure it with the --debug-trycompile.


-Bill
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake


[CMake] Continued issues in trying to get CMake working on OpenVMS

2015-09-21 Thread Custin, Jay (CSC Sw Middleware)
So I ran into a few minor issues compiling/linking the CMake images (compiler 
threw a few "warnings" which didn't really prove significant so I simply 
"silenced" the warnings to enable the code to compile clean and link).  I 
accomplished this with the following:

bash$ export CFLAGS="-Wc/warnings=disable=all"
bash$ export CXXFLAGS="-Wc/warnings=disable=all"
bash$ ./configure

The bootstrap "happily" compiles and links ALL the code without any issues... 
but then CMake does some self-evaluation and things get very ugly... very fast. 
 For whatever reason the bootstrap has no issues "finding" the various C/C++ 
header files to compile and link the CMake source... but when the "interim" 
CMake itself then tries to find them... complete and utter failure.

At present I have what I would call the "interim" version of CMake built (which 
at this phase requires adding the option -DCMAKE_BOOTSTRAP=1 on the end of the 
cmake command to do much of anything).  I have included an abbreviated version 
of this build below:

bash$ export CFLAGS="-Wc/warnings=disable=all"
bash$ export CXXFLAGS="-Wc/warnings=disable=all"
bash$ ./configure --system-curl --system-zlib --verbose 
--init=BuildCMakeOpenVMS_CacheFlags.cmake
-
Source directory: /PRJ_ROOT/CMAKE-3_3_1
Binary directory: /PRJ_ROOT/CMAKE-3_3_1
Prefix directory: /usr/local
System:   OpenVMS 

-
CMake 3.3.1, Copyright 2000-2015 Kitware, Inc.
C compiler on this system is: cc -Wc/warnings=disable=all
C++ compiler on this system is: CXX -Wc/warnings=disable=all
%DCL-E-PARSEFAIL, error parsing DCL$PATH:"cc".* -RMS-F-FNM, error in file name 
Makefile processor on this system is: make %DCL-E-NOTFR, no transfer address 
CXX is not GNU compiler %DCL-E-NOTFR, no transfer address CXX is not 
SolarisStudio compiler CXX has setenv CXX has unsetenv CXX does not have 
environ in stdlib.h CXX has STL in std:: namespace CXX has ANSI streams CXX has 
streams in std:: namespace CXX has sstream CXX has operator!=(string, char*) 
CXX has stl iterator_traits CXX has standard template allocator CXX has 
allocator<>::rebind<> CXX does not have non-standard allocator<>::max_size 
argument CXX has stl containers supporting allocator objects CXX has stl 
wstring CXX has header cstddef CXX does not require template friends to use <> 
CXX supports member templates CXX has standard template specialization syntax 
CXX has argument dependent lookup CXX does not have struct stat with st_mtim 
member CXX has ios::binary openmode
-
CXX -Wc/warnings=disable=all  -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk 
-I/PRJ_ROOT/CMAKE-3_3_1/Source   -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk -c 
/PRJ_ROOT/CMAKE-3_3_1/Source/cmake.cxx -o cmake.o
CXX -Wc/warnings=disable=all  -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk 
-I/PRJ_ROOT/CMAKE-3_3_1/Source   -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk -c 
/PRJ_ROOT/CMAKE-3_3_1/Source/cmakemain.cxx -o cmakemain.o
CXX -Wc/warnings=disable=all  -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk 
-I/PRJ_ROOT/CMAKE-3_3_1/Source   -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk -c 
/PRJ_ROOT/CMAKE-3_3_1/Source/cmcmd.cxx -o cmcmd.o

<>
<>
<>

cc -Wc/warnings=disable=all -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk 
-I/PRJ_ROOT/CMAKE-3_3_1/Source   -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk 
-DKWSYS_NAMESPACE=cmsys  -c /PRJ_ROOT/CMAKE-3_3_1/Source/kwsys/Terminal.c -o 
Terminal.o
CXX  -Wc/warnings=disable=all  -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk 
-I/PRJ_ROOT/CMAKE-3_3_1/Source   -I/PRJ_ROOT/CMAKE-3_3_1/Bootstrap_cmk  cmake.o 
cmakemain.o cmcmd.o cmCommandArgumentLexer.o cmCommandArgumentParser.o 
cmCommandArgumentParserHelper.o cmCPackPrope rtiesGenerator.o cmDefinitions.o 
cmDepends.o cmDependsC.o cmDocumentationFormatter.o cmPolicies.o cmProperty.o 
cmPropertyMap.o cmPro pertyDefinition.o cmPropertyDefinitionMap.o 
cmMakeDepend.o cmMakefile.o cmExportFileGenerator.o 
cmExportInstallFileGenerator.o cmExp ortTryCompileFileGenerator.o cmExportSet.o 
cmExportSetMap.o cmExternalMakefileProjectGenerator.o 
cmGeneratorExpressionEvaluationFile
.o cmGeneratedFileStream.o cmGeneratorTarget.o cmGeneratorExpressionContext.o 
cmGeneratorExpressionDAGChecker.o cmGeneratorExpressio nEvaluator.o 
cmGeneratorExpressionLexer.o cmGeneratorExpressionNode.o 
cmGeneratorExpressionParser.o cmGeneratorExpression.o cmGlobal Generator.o 
cmInstallDirectoryGenerator.o cmLocalGenerator.o cmInstalledFile.o 
cmInstallGenerator.o cmInstallExportGenerator.o cmIns tallFilesGenerator.o 
cmInstallScriptGenerator.o cmInstallTargetGenerator.o cmScriptGenerator.o 
cmSourceFile.o cmSourceFileLocation.o  cmState.o cmSystemTools.o 
cmTestGenerator.o cmVersion.o cmFileTimeComparison.o 
cmGlobalUnixMakefileGenerator3.o cmLocalUnixMakefile Generator3.o 
cmMakefileExecutableTargetGenerator.o cmMakefileLibraryTargetGenerator.o 
cmMakefileTargetGenerator.o cmMakefileUtilityT argetGenerator.o 
cmOSXBundleGenerator.o cmNewLineStyle.o 

Re: [CMake] How to create a custom solution with Visual Studio 2010 generator?

2015-09-21 Thread J Decker
CMake's PROJECT directive maps to 'Solution'  (should only be one
project() per chain) ... use set( PROJECT projectname) and then
reference ${PROJECT} later instead of ${PROJECT_NAME} for easy
conversion.

add_library, add_executable map to 'project'

from http://www.cmake.org/Wiki/CMake_Useful_Variables

you can wrap the projects you want to omit with If's

if( NOT MSVC10 )
   add_library( one I don't want in 2010)
endif( NOT MSVC10 )




On Sun, Sep 20, 2015 at 11:20 PM, Golebiewski, Jakub
 wrote:
> Hi,
>
>
>
> I’m trying to create a solution with custom set of projects (in VS sense)
> for Visual Studio 2010.
>
> I have a top level CMakeLists.txt with PROJECT() declared and then several
> CMakeLists.txt below in a tree also with PROJECT() in each of them.
>
> However for lower level PROJECT() directives I get all the targets that I
> specify in CMakeLists.txt and all the targets that they depend on.
>
>
>
> My goal is to have a solution only with a specific set of targets, without
> dependencies.
>
>
>
> Is there a  way to do that in cmake?
>
>
>
> Thanks for help,
>
> Jakub
>
>
> **
> This e-mail and any attachments thereto may contain confidential information
> and/or information protected by intellectual property rights for the
> exclusive attention of the intended addressees named above. If you have
> received this transmission in error, please immediately notify the sender by
> return e-mail and delete this message and its attachments. Unauthorized use,
> copying or further full or partial distribution of this e-mail or its
> contents is prohibited.
> **
>
> --
>
> 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 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] Continued issues in trying to get CMake working on OpenVMS

2015-09-21 Thread Bill Hoffman

On 9/21/2015 10:17 AM, Custin, Jay (CSC Sw Middleware) wrote:

This gets made even more frustrating in that it appears that the
testing phase does a VERY good job cleaning up after itself...



So, the output should all be in CMakeOutput.log and CMakeError.log found 
in the build tree in the CMakeFiles directory.


If you want CMake not to delete the temp files you can use 
--debug-trycompile


http://www.cmake.org/cmake/help/v3.3/manual/cmake.1.html

-Bill

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake


[CMake] add(library foo SHARED...) is not creating a PDB file

2015-09-21 Thread Tom Kacvinsky
I am using cmake 2.8.11.2 on Windows 7 with Visual Studio 2008

This is the snipped of my CMakeLists.txt file

  add_library(commoncpp_objects
OBJECT
 
  )

  add_library(commoncpp_static STATIC $)
  add_dependencies(commoncpp_static commoncpp_objects)

add_library(commoncpp SHARED
  $
  commoncpp_exports.def
)

The objects, static library, and dll/import lib/exp files are created, but
there is no commoncpp.pdb file.

Any ideas what I am doing wrong?

Thanks,

Tom
-- 

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] CMP0054 and CMake Modules

2015-09-21 Thread thoni56
Aahh, I was looking at the trace and it only included "include":s so I
thought that offending IF was in cmake's own files since it pointed there.

But, you are saying that probably the culprit is a variable set before the
first include, right? (It was definitely not by intention a variable was as
having the empty name ;-).

And if I look at
/usr/share/cmake-3.3.1/Modules/CMakeParseImplicitLinkInfo.cmake:58 I should
probably see the variable (or one that expands to include it)?

/Thomas


Nils Gladitz-2 wrote
> On 09/21/2015 09:37 AM, thoni56 wrote:
>>Quoted variables like "" will no longer be dereferenced when the
>> policy is
> 
> You apparently have a variable whose name is the empty string.
> 
> ...
> 
> Since most cmake provided modules have to work with both the old and new 
> behavior a common work around is e.g.
> 
>   if("x${MYVAR}" STREQUAL "x")
> 
> This workaround however only works if by convention there are no 
> variables starting with a lower case x in their name.
> 
> I think by that same reasoning you should avoid defining variables whose 
> name is the empty string.
> 
> Nils
> -- 
> 
> 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





--
View this message in context: 
http://cmake.3232098.n2.nabble.com/CMP0054-and-CMake-Modules-tp7590137p7591580.html
Sent from the CMake mailing list archive at Nabble.com.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake


Re: [CMake] CMP0054 and CMake Modules

2015-09-21 Thread Nils Gladitz

On 09/21/2015 10:24 AM, thoni56 wrote:

Aahh, I was looking at the trace and it only included "include":s so I
thought that offending IF was in cmake's own files since it pointed there.

But, you are saying that probably the culprit is a variable set before the
first include, right? (It was definitely not by intention a variable was as
having the empty name ;-).


The culprit is the empty named variable being set before the condition 
in that included module is evaluated, yes.


If you aren't the one setting it it might also be accidentally set 
somewhere in cmake code of course.


It probably isn't something as obvious as set("" foobar) but perhaps 
something like e.g. set("${MY_VAR_NAME}" foobar) (where MY_VAR_NAME is 
an unset variable e.g. due to typo or unexpected program logic).




And if I look at
/usr/share/cmake-3.3.1/Modules/CMakeParseImplicitLinkInfo.cmake:58 I should
probably see the variable (or one that expands to include it)?


The condition in that line is:
if("${cmd}" MATCHES "${linker_regex}")

So apparently ${cmd} expands empty (which may or may not be expected but 
is a distinct issue).


With old behavior cmake will therefor look for a variable with the empty 
name and in your case finds and expands it.


If you don't know where the empty named variable might come from I would 
expect cmake's new --trace-expand might be helpful.


I haven't tried it myself yet and you would have to use a nightly build 
though since it hasn't made it into a release yet.


Nils
--

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] CMP0054 and CMake Modules

2015-09-21 Thread thoni56
Also, this does not happen on MacOSX with Macports cmake. But does on Cygwin.
thoni56 wrote
> 
> Nils Gladitz-2 wrote
>> On 09/21/2015 09:37 AM, thoni56 wrote:
>>>Quoted variables like "" will no longer be dereferenced when the
>>> policy is
>> 
>> You apparently have a variable whose name is the empty string.
>> 
>> ...
>> 
>> Since most cmake provided modules have to work with both the old and new 
>> behavior a common work around is e.g.
>> 
>>  if("x${MYVAR}" STREQUAL "x")
>> 
>> This workaround however only works if by convention there are no 
>> variables starting with a lower case x in their name.
>> 
>> I think by that same reasoning you should avoid defining variables whose 
>> name is the empty string.
>> 
>> Nils
>> -- 
>> 
>> 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





--
View this message in context: 
http://cmake.3232098.n2.nabble.com/CMP0054-and-CMake-Modules-tp7590137p7591581.html
Sent from the CMake mailing list archive at Nabble.com.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake


[Cmake-commits] CMake branch, next, updated. v3.3.2-3183-g58c4057

2015-09-21 Thread Domen Vrankar
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  58c40573e265ae38d64738cf4033373df0f2a6a5 (commit)
   via  b58de9fe2ba4ac3e194403ecd118fd54681ffae8 (commit)
   via  47b060aee0871bdb5fea63b398a1f1cb07fa3b37 (commit)
  from  6d9d7045893e99bc713958ec93f30fcf62555b6f (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=58c40573e265ae38d64738cf4033373df0f2a6a5
commit 58c40573e265ae38d64738cf4033373df0f2a6a5
Merge: 6d9d704 b58de9f
Author: Domen Vrankar 
AuthorDate: Mon Sep 21 20:10:49 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 20:10:49 2015 -0400

Merge topic 'cpack-package-empty-dirs' into next

b58de9fe CPack: allow packaging of empty directories
47b060ae CPackDeb: allow empty directories in component packages


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b58de9fe2ba4ac3e194403ecd118fd54681ffae8
commit b58de9fe2ba4ac3e194403ecd118fd54681ffae8
Author: Domen Vrankar 
AuthorDate: Tue Sep 22 02:08:26 2015 +0200
Commit: Domen Vrankar 
CommitDate: Tue Sep 22 02:08:26 2015 +0200

CPack: allow packaging of empty directories

diff --git a/Help/release/dev/cpack-package-empty-dirs.rts 
b/Help/release/dev/cpack-package-empty-dirs.rts
new file mode 100644
index 000..1f56e1a
--- /dev/null
+++ b/Help/release/dev/cpack-package-empty-dirs.rts
@@ -0,0 +1,4 @@
+cpack-package-empty-dirs
+
+
+* The :module:`CPack` module learned to package empty directories.
diff --git a/Source/CPack/cmCPackGenerator.cxx 
b/Source/CPack/cmCPackGenerator.cxx
index 92a4b2b..aa4f181 100644
--- a/Source/CPack/cmCPackGenerator.cxx
+++ b/Source/CPack/cmCPackGenerator.cxx
@@ -367,6 +367,8 @@ int cmCPackGenerator::InstallProjectViaInstalledDirectories(
   cmCPackLogger(cmCPackLog::LOG_OUTPUT,
 "- Install directory: " << top << std::endl);
   gl.RecurseOn();
+  gl.SetRecurseListDirs(true);
+//  gl.SetRecurseThroughSymlinks(false);
   if ( !gl.FindFiles(findExpr) )
 {
 cmCPackLogger(cmCPackLog::LOG_ERROR,
@@ -869,6 +871,7 @@ int cmCPackGenerator::InstallProjectViaInstallCMakeProjects(
   cmsys::Glob glB;
   findExpr += "/*";
   glB.RecurseOn();
+  glB.SetRecurseListDirs(true);
   glB.FindFiles(findExpr);
   filesBefore = glB.GetFiles();
   std::sort(filesBefore.begin(),filesBefore.end());
@@ -908,6 +911,7 @@ int cmCPackGenerator::InstallProjectViaInstallCMakeProjects(
   {
   cmsys::Glob glA;
   glA.RecurseOn();
+  glA.SetRecurseListDirs(true);
   glA.FindFiles(findExpr);
   std::vector filesAfter = glA.GetFiles();
   std::sort(filesAfter.begin(),filesAfter.end());
@@ -1074,6 +1078,7 @@ int cmCPackGenerator::DoPackage()
   std::string findExpr = tempDirectory;
   findExpr += "/*";
   gl.RecurseOn();
+  gl.SetRecurseListDirs(true);
   gl.SetRecurseThroughSymlinks(false);
   if ( !gl.FindFiles(findExpr) )
 {
diff --git a/Source/cmSystemTools.cxx b/Source/cmSystemTools.cxx
index 2675066..c24b5ea 100644
--- a/Source/cmSystemTools.cxx
+++ b/Source/cmSystemTools.cxx
@@ -895,12 +895,33 @@ std::string 
cmSystemTools::FileExistsInParentDirectories(const char* fname,
 
 bool cmSystemTools::cmCopyFile(const char* source, const char* destination)
 {
+  // FIXME remove if statement once kwsys SystemTools get support for
+  // source is directory handling in CopyFileAlways function
+  if(cmSystemTools::FileIsDirectory(source))
+{
+return Superclass::MakeDirectory(destination);
+}
+
   return Superclass::CopyFileAlways(source, destination);
 }
 
 bool cmSystemTools::CopyFileIfDifferent(const char* source,
   const char* destination)
 {
+  // FIXME remove if statement once kwsys SystemTools get support for
+  // source is directory handling in CopyFileIfDifferent function
+  if(cmSystemTools::FileIsDirectory(source))
+{
+if(SystemTools::FileExists(destination))
+  {
+  return true;
+  }
+else
+  {
+  return Superclass::MakeDirectory(destination);
+  }
+}
+
   return Superclass::CopyFileIfDifferent(source, destination);
 }
 
diff --git a/Tests/RunCMake/CPack/CMakeLists.txt 
b/Tests/RunCMake/CPack/CMakeLists.txt
index 46f1367..449172a 100644
--- a/Tests/RunCMake/CPack/CMakeLists.txt
+++ b/Tests/RunCMake/CPack/CMakeLists.txt
@@ -8,5 +8,5 @@ if(EXISTS 
"${CMAKE_CURRENT_SOURCE_DIR}/${GENERATOR_TYPE}/${RunCMake_TEST}-specif
   

[Cmake-commits] CMake branch, master, updated. v3.3.2-1245-gdce7d8b

2015-09-21 Thread Kitware Robot
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  dce7d8befb94e2531d6c7d68b78b4b4a67ca024f (commit)
  from  cec45e27f6dc2657b00902bcaef5bd93ae16ead7 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dce7d8befb94e2531d6c7d68b78b4b4a67ca024f
commit dce7d8befb94e2531d6c7d68b78b4b4a67ca024f
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Tue Sep 22 00:01:04 2015 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Tue Sep 22 00:01:04 2015 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 17f8db5..e43b424 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 3)
-set(CMake_VERSION_PATCH 20150921)
+set(CMake_VERSION_PATCH 20150922)
 #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-commits] CMake branch, next, updated. v3.3.2-3141-g95d21a8

2015-09-21 Thread 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  95d21a818a0531e148c527c0c64d176c812e718e (commit)
   via  98908b0f3ed997294d4ab40b04d191cf278d658e (commit)
  from  281ecf26db4308e41de0eaa3707d216e1806b5a4 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=95d21a818a0531e148c527c0c64d176c812e718e
commit 95d21a818a0531e148c527c0c64d176c812e718e
Merge: 281ecf2 98908b0
Author: Brad King 
AuthorDate: Mon Sep 21 09:02:30 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:02:30 2015 -0400

Merge topic 'fix-windows-version-detection' into next

98908b0f fixup! Windows: Fix CMAKE_HOST_SYSTEM_VERSION on Windows >= 8 
(#15674)


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=98908b0f3ed997294d4ab40b04d191cf278d658e
commit 98908b0f3ed997294d4ab40b04d191cf278d658e
Author: Brad King 
AuthorDate: Mon Sep 21 09:02:14 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 09:02:14 2015 -0400

fixup! Windows: Fix CMAKE_HOST_SYSTEM_VERSION on Windows >= 8 (#15674)

diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt
index 7a671be..e2a7ff2 100644
--- a/Source/CMakeLists.txt
+++ b/Source/CMakeLists.txt
@@ -505,7 +505,7 @@ if (WIN32)
 
 # Add a manifest file to executables on Windows to allow for
 # GetVersion to work properly on Windows 8 and above.
-set(MANIFEST_FILE cmake.version.manifest)
+set(MANIFEST_FILE ${CMAKE_CURRENT_SOURCE_DIR}/cmake.version.manifest)
   endif()
 endif ()
 

---

Summary of changes:
 Source/CMakeLists.txt |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.3.2-3150-gdec07ad

2015-09-21 Thread 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  dec07adacff8a62c0c68b4ab3caf0f2be03aa45a (commit)
   via  1f4358134f2cf5b9fe72088d6534084a8fb71a52 (commit)
   via  38830fc0cabb742cf95160429cc99cdb5326cce7 (commit)
   via  dd8285c6880e08e4c6cbb0e2ca1a1684df3e11d1 (commit)
   via  4f640afc1aa571a4a1a9083b62e3d2787db84bf3 (commit)
   via  82a0c7be3f6a00119f3ba00b0d1a4f73cbbb140c (commit)
   via  358b56414563d21006e482e8441d29fa8f55 (commit)
  from  b1c162ff8874a23434e314254f00b91e9efd699a (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dec07adacff8a62c0c68b4ab3caf0f2be03aa45a
commit dec07adacff8a62c0c68b4ab3caf0f2be03aa45a
Merge: b1c162f 1f43581
Author: Brad King 
AuthorDate: Mon Sep 21 09:25:41 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 09:25:41 2015 -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.3.2-1232-g4f640af

2015-09-21 Thread 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  4f640afc1aa571a4a1a9083b62e3d2787db84bf3 (commit)
   via  109a7a245acf0c367ac092f6c9a20661e7a31529 (commit)
   via  828c05b9f567e0652ebbee6df2799a189ff586fe (commit)
   via  c73fbda66b5985e4ba99499f871ffd19bcf32aaa (commit)
  from  82a0c7be3f6a00119f3ba00b0d1a4f73cbbb140c (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4f640afc1aa571a4a1a9083b62e3d2787db84bf3
commit 4f640afc1aa571a4a1a9083b62e3d2787db84bf3
Merge: 82a0c7b 109a7a2
Author: Brad King 
AuthorDate: Mon Sep 21 09:25:27 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:25:27 2015 -0400

Merge topic 'ninja-refactor-msvc-deps'

109a7a24 Ninja: Detect MSVC /showIncludes prefix with compiler flags 
(#15596)
828c05b9 Ninja: Refactor lookup of cmcldeps location
c73fbda6 CMakeDetermineCompilerId: Drop unused code path


---

Summary of changes:
 Modules/CMakeCCompiler.cmake.in |8 ++--
 Modules/CMakeCXXCompiler.cmake.in   |8 ++--
 Modules/CMakeClDeps.cmake   |   34 
 Modules/CMakeDetermineCCompiler.cmake   |1 -
 Modules/CMakeDetermineCXXCompiler.cmake |1 -
 Modules/CMakeDetermineCompilerId.cmake  |   65 ---
 Source/cmNinjaTargetGenerator.cxx   |2 +-
 Source/cmSystemTools.cxx|   14 +++
 Source/cmSystemTools.h  |1 +
 9 files changed, 68 insertions(+), 66 deletions(-)
 delete mode 100644 Modules/CMakeClDeps.cmake


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.3.2-1228-g82a0c7b

2015-09-21 Thread 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  82a0c7be3f6a00119f3ba00b0d1a4f73cbbb140c (commit)
   via  fd47df45030733341858fa33ee96015d64c73c03 (commit)
   via  6e3151f6ccd035ffd704d3cb0162c873d5e95e15 (commit)
  from  358b56414563d21006e482e8441d29fa8f55 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=82a0c7be3f6a00119f3ba00b0d1a4f73cbbb140c
commit 82a0c7be3f6a00119f3ba00b0d1a4f73cbbb140c
Merge: 358b564 fd47df4
Author: Brad King 
AuthorDate: Mon Sep 21 09:25:24 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:25:24 2015 -0400

Merge topic 'ctest-custom-output-size'

fd47df45 CTest: Add options to limit output of passed and failed tests
6e3151f6 CTest: Document and test custom output size settings


---

Summary of changes:
 Help/command/ctest_test.rst|3 ++
 Help/manual/cmake-variables.7.rst  |2 +
 Help/manual/ctest.1.rst|6 +++
 Help/release/dev/ctest-custom-output-size.rst  |7 
 ...TEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.rst |6 +++
 ...TEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE.rst |6 +++
 Source/CTest/cmCTestTestHandler.h  |5 +++
 Source/cmCTest.cxx |   41 +++-
 Source/ctest.cxx   |4 ++
 Tests/RunCMake/CTestCommandLine/RunCMakeTest.cmake |   17 
 .../CTestCommandLine/TestOutputSize-check.cmake|   17 
 .../CTestCommandLine/TestOutputSize-result.txt |1 +
 .../CTestCommandLine/TestOutputSize-stderr.txt |1 +
 Tests/RunCMake/ctest_test/CMakeLists.txt.in|1 +
 Tests/RunCMake/ctest_test/RunCMakeTest.cmake   |   15 +++
 .../RunCMake/ctest_test/TestOutputSize-check.cmake |   17 
 16 files changed, 148 insertions(+), 1 deletion(-)
 create mode 100644 Help/release/dev/ctest-custom-output-size.rst
 create mode 100644 
Help/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.rst
 create mode 100644 
Help/variable/CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE.rst
 create mode 100644 Tests/RunCMake/CTestCommandLine/TestOutputSize-check.cmake
 create mode 100644 Tests/RunCMake/CTestCommandLine/TestOutputSize-result.txt
 create mode 100644 Tests/RunCMake/CTestCommandLine/TestOutputSize-stderr.txt
 create mode 100644 Tests/RunCMake/ctest_test/TestOutputSize-check.cmake


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.3.2-1236-gdd8285c

2015-09-21 Thread 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  dd8285c6880e08e4c6cbb0e2ca1a1684df3e11d1 (commit)
   via  2514e4265c1914f53f9445f331ddb7183f0d9501 (commit)
   via  b98f7712eab7fd928e7e332124b2a6fdcdfec7e6 (commit)
   via  b5de2bd9dea2d1b7bd2c128e0b1dff0f3bbda02b (commit)
  from  4f640afc1aa571a4a1a9083b62e3d2787db84bf3 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dd8285c6880e08e4c6cbb0e2ca1a1684df3e11d1
commit dd8285c6880e08e4c6cbb0e2ca1a1684df3e11d1
Merge: 4f640af 2514e42
Author: Brad King 
AuthorDate: Mon Sep 21 09:25:29 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:25:29 2015 -0400

Merge topic 'fix-compatibility-mode-LOCATION'

2514e426 CMP0026: Use compatibility codepath until configure is finished 
(#15748)
b98f7712 cmGlobalGenerator: Add API for the configure step being finished.
b5de2bd9 cmLocalGenerator: Simplify condition.


---

Summary of changes:
 Source/cmGeneratorTarget.cxx |   12 ++--
 Source/cmGlobalGenerator.cxx |5 +
 Source/cmGlobalGenerator.h   |3 +++
 Source/cmLocalGenerator.cxx  |2 +-
 Source/cmTarget.cxx  |4 ++--
 Tests/RunCMake/CMP0026/RunCMakeTest.cmake|1 +
 .../CMP0026/clear-cached-information-dir/CMakeLists.txt  |2 ++
 Tests/RunCMake/CMP0026/clear-cached-information.cmake|   14 ++
 8 files changed, 34 insertions(+), 9 deletions(-)
 create mode 100644 
Tests/RunCMake/CMP0026/clear-cached-information-dir/CMakeLists.txt
 create mode 100644 Tests/RunCMake/CMP0026/clear-cached-information.cmake


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.3.2-1241-g1f43581

2015-09-21 Thread 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  1f4358134f2cf5b9fe72088d6534084a8fb71a52 (commit)
   via  bc2e54db5516ed884f0affe020e52256f0c8b3d5 (commit)
  from  38830fc0cabb742cf95160429cc99cdb5326cce7 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1f4358134f2cf5b9fe72088d6534084a8fb71a52
commit 1f4358134f2cf5b9fe72088d6534084a8fb71a52
Merge: 38830fc bc2e54d
Author: Brad King 
AuthorDate: Mon Sep 21 09:25:34 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:25:34 2015 -0400

Merge topic 'cpack-verbatim-variables'

bc2e54db Introduction of CPACK_VERBATIM_VARIABLES variable


---

Summary of changes:
 Help/release/dev/CPack-updates.rst  |5 +++
 Modules/CPack.cmake |   46 +++
 Tests/RunCMake/CPackConfig/RunCMakeTest.cmake   |2 +
 Tests/RunCMake/CPackConfig/Special-check.cmake  |5 +++
 Tests/RunCMake/CPackConfig/Special.cmake|3 ++
 Tests/RunCMake/CPackConfig/Verbatim-check.cmake |   10 +
 Tests/RunCMake/CPackConfig/Verbatim.cmake   |5 +++
 7 files changed, 68 insertions(+), 8 deletions(-)
 create mode 100644 Tests/RunCMake/CPackConfig/Special-check.cmake
 create mode 100644 Tests/RunCMake/CPackConfig/Special.cmake
 create mode 100644 Tests/RunCMake/CPackConfig/Verbatim-check.cmake
 create mode 100644 Tests/RunCMake/CPackConfig/Verbatim.cmake


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.3.2-1239-g38830fc

2015-09-21 Thread 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  38830fc0cabb742cf95160429cc99cdb5326cce7 (commit)
   via  da295f450da2781e82632b6a5df29df6fbf7daad (commit)
   via  7c7874c86ef14f2866d38d5ee85709db6e71d217 (commit)
  from  dd8285c6880e08e4c6cbb0e2ca1a1684df3e11d1 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=38830fc0cabb742cf95160429cc99cdb5326cce7
commit 38830fc0cabb742cf95160429cc99cdb5326cce7
Merge: dd8285c da295f4
Author: Brad King 
AuthorDate: Mon Sep 21 09:25:31 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:25:31 2015 -0400

Merge topic 'cpack-deb-checksum-on-symlinks'

da295f45 CPack/Deb: checksum on symlinks release notes
7c7874c8 CPackDeb: preventing md5sum on symlinks


---

Summary of changes:
 .../release/dev/cpack-deb-checksum-on-symlinks.rts |4 +++
 Source/CPack/cmCPackDebGenerator.cxx   |   29 +++-
 Tests/CPackComponentsDEB/CMakeLists.txt|   19 +
 ...yResult-components-lintian-dpkgdeb-checks.cmake |2 +-
 .../CPackComponentsDEB/RunCPackVerifyResult.cmake  |   12 ++--
 5 files changed, 49 insertions(+), 17 deletions(-)
 create mode 100644 Help/release/dev/cpack-deb-checksum-on-symlinks.rts


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.3.2-3143-gb1c162f

2015-09-21 Thread 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  b1c162ff8874a23434e314254f00b91e9efd699a (commit)
   via  17009189f8bbf264b386bb610deafdd0d8ce53c2 (commit)
  from  95d21a818a0531e148c527c0c64d176c812e718e (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b1c162ff8874a23434e314254f00b91e9efd699a
commit b1c162ff8874a23434e314254f00b91e9efd699a
Merge: 95d21a8 1700918
Author: Brad King 
AuthorDate: Mon Sep 21 09:02:57 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:02:57 2015 -0400

Merge topic 'fix-windows-version-detection' into next

17009189 Windows: Fix CMAKE_HOST_SYSTEM_VERSION on Windows >= 8 (#15674)


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=17009189f8bbf264b386bb610deafdd0d8ce53c2
commit 17009189f8bbf264b386bb610deafdd0d8ce53c2
Author: Gilles Khouzam 
AuthorDate: Fri Sep 18 10:23:21 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 09:02:41 2015 -0400

Windows: Fix CMAKE_HOST_SYSTEM_VERSION on Windows >= 8 (#15674)

According to GetVersionEx documentation:

 https://msdn.microsoft.com/en-us/library/windows/desktop/ms724451.aspx
 https://msdn.microsoft.com/en-us/library/windows/desktop/dn481241.aspx

we must manifest each application to explicitly declare support for each
version of Windows.

diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt
index 16b9ea1..e2a7ff2 100644
--- a/Source/CMakeLists.txt
+++ b/Source/CMakeLists.txt
@@ -502,6 +502,10 @@ if (WIN32)
   cmGhsMultiGpj.cxx
   cmGhsMultiGpj.h
   )
+
+# Add a manifest file to executables on Windows to allow for
+# GetVersion to work properly on Windows 8 and above.
+set(MANIFEST_FILE ${CMAKE_CURRENT_SOURCE_DIR}/cmake.version.manifest)
   endif()
 endif ()
 
@@ -531,7 +535,7 @@ set(SRCS ${SRCS}
 
 if(WIN32 AND NOT CYGWIN)
   set_source_files_properties(cmcldeps.cxx PROPERTIES COMPILE_DEFINITIONS 
_WIN32_WINNT=0x0501)
-  add_executable(cmcldeps cmcldeps.cxx)
+  add_executable(cmcldeps cmcldeps.cxx ${MANIFEST_FILE})
   target_link_libraries(cmcldeps CMakeLib)
   install(TARGETS cmcldeps DESTINATION bin)
 endif()
@@ -720,15 +724,15 @@ if(APPLE)
 endif()
 
 # Build CMake executable
-add_executable(cmake cmakemain.cxx cmcmd.cxx cmcmd.h)
+add_executable(cmake cmakemain.cxx cmcmd.cxx cmcmd.h ${MANIFEST_FILE})
 target_link_libraries(cmake CMakeLib)
 
 # Build CTest executable
-add_executable(ctest ctest.cxx)
+add_executable(ctest ctest.cxx ${MANIFEST_FILE})
 target_link_libraries(ctest CTestLib)
 
 # Build CPack executable
-add_executable(cpack CPack/cpack.cxx)
+add_executable(cpack CPack/cpack.cxx ${MANIFEST_FILE})
 target_link_libraries(cpack CPackLib)
 
 # Curses GUI
diff --git a/Source/QtDialog/CMakeLists.txt b/Source/QtDialog/CMakeLists.txt
index 570b537..66fd18b 100644
--- a/Source/QtDialog/CMakeLists.txt
+++ b/Source/QtDialog/CMakeLists.txt
@@ -152,7 +152,7 @@ endif()
 
 set(CMAKE_INCLUDE_CURRENT_DIR ON)
 
-add_executable(cmake-gui WIN32 MACOSX_BUNDLE ${SRCS})
+add_executable(cmake-gui WIN32 MACOSX_BUNDLE ${SRCS} ${MANIFEST_FILE})
 target_link_libraries(cmake-gui CMakeLib ${QT_QTMAIN_LIBRARY} 
${CMake_QT_LIBRARIES})
 
 if(APPLE)
diff --git a/Source/cmake.version.manifest b/Source/cmake.version.manifest
new file mode 100644
index 000..e7010c9
--- /dev/null
+++ b/Source/cmake.version.manifest
@@ -0,0 +1,18 @@
+
+   
+   
+   
+   
+   
+   
+   
+   
+   
+   
+   
+   
+   
+   
+

---

Summary of changes:


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


Re: [cmake-developers] Add command line options for deprecation message control

2015-09-21 Thread Brad King
On 09/19/2015 06:32 PM, Michael Scott wrote:
> whether the -W options are intended to only be applicable
> for the message command (and so the current behaviour is correct),
> or whether they should affect all author and deprecated messages
> output by other parts of CMake?

The -Wdev/-Wno-dev options have always been for all messages
output by any part of CMake.  This needs to be preserved/corrected.

> If the current behaviour isn't correct, then one thing to have a
> good think about, is how to handle turning warnings into errors
> when -Werr-dev or -Werr-deprecated (and also the required behaviour
> when -Wno- is used). As some users of IssueMessage do different
> things if an error occurs (and is output), *after* IssueMessage
> is called. So there might need to be a way to signal to the caller
> when a warning has been upgraded to an error because of the users
> options perhaps?

Likely yes.  This may require sweeping changes to address.  We're
too close to the freeze for 3.4 to do this now.  Perhaps we should
simply remove -Werr-dev for now.

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


Re: [cmake-developers] CPack/NSIS is broken after extended length paths fix

2015-09-21 Thread Clinton Stimpson
On Monday, September 21, 2015 12:28:37 PM Dmitry Kochkin wrote:
>  Hi Clint,
> 
> >>Actually it's even worse because in current master HEAD I can see that
> >>INST_DIR is empty in generated project: !define INST_DIR ""
> >>(not sure if that's caused by your change)
> >
> >Interesting... Do you know why this happens?  How is this problem related
> >to extended paths (with the \\?\ prefix)?  Do you have an example to
> >demonstrate this problem? That was my mistake, please ignore.>
> >>I've figured out that NSIS was not going to fix this (see 
> >>http://sourceforge.net/p/nsis/feature-requests/241/ )>
> >Maybe they'll accept a patch to fix it there?  Was there any effort to fix
> >it there?
> In the URL I've put they claim you should just use "\\?\" in your NSIS
> project. I guess it's also possible to fix NSIS, but we cannot rely that
> user have latest NSIS.

Using "\\?\" in a NSIS project is a workaround, not a fix.
If a workaround is put into CMake, then you are relying on the latest CMake, 
right?


> >>I've made a small patch to NSIS generator and template to put infamous
> >>\\?\ there.
> >>
> >>I can send directly to you as I guess you know more about these parts of
> >>code.>
> >You can send your patch to this mailing list for review.
> 
> Patch attached. It's a bit hacky, more fixing symptoms I guess. The purpose
> is only to demonstrate the idea. Let me know if it can be done in better
> way.

Yes, it fixes symptoms.  The correct and robust way to fix this is to fix NSIS.

I have concerns with this patch:

1. Are the paths cleaned before placed into the NSIS template?  Only clean 
paths can be prepended with \\?\.  For example, these paths may not contain 
"." or "../" in them.

2. This patch can break UNC paths.  UNC paths must be prepended with a "\\?
\UNC\" prefix instead of "\\?\".  If CPACK_TEMPORARY_DIRECTORY is a UNC path, 
this patch breaks it.

3. For the uninstall code put into the NSIS template, how do you know whether 
INSTDIR is a UNC path or not?  INSTDIR is determined by the end-user when 
installing the software.  Blindly prepending "\\?\" may not work all the time.

Clint
-- 

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-commits] CMake branch, next, updated. v3.3.2-3157-g7defd7c

2015-09-21 Thread 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  7defd7c0006bbdf054c85ada3508b8bb7487da86 (commit)
   via  7c7a3c35add0380622e827866985aa9bde286676 (commit)
  from  47462f48357918309a2019510586bae2410ddcb7 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7defd7c0006bbdf054c85ada3508b8bb7487da86
commit 7defd7c0006bbdf054c85ada3508b8bb7487da86
Merge: 47462f4 7c7a3c3
Author: Brad King 
AuthorDate: Mon Sep 21 09:39:18 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:39:18 2015 -0400

Merge topic 'pkg-config-variable-function' into next

7c7a3c35 fixup! FindPkgConfig: add a command to query arbitrary variables


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7c7a3c35add0380622e827866985aa9bde286676
commit 7c7a3c35add0380622e827866985aa9bde286676
Author: Brad King 
AuthorDate: Mon Sep 21 09:38:58 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 09:38:58 2015 -0400

fixup! FindPkgConfig: add a command to query arbitrary variables

diff --git a/Modules/FindPkgConfig.cmake b/Modules/FindPkgConfig.cmake
index 9c725fc..e822b9c 100644
--- a/Modules/FindPkgConfig.cmake
+++ b/Modules/FindPkgConfig.cmake
@@ -94,13 +94,13 @@ endmacro()
 #[[.rst:
 .. command:: pkg_get_variable
 
- Retrieves the value of a variable from a package. ::
+  Retrieves the value of a variable from a package::
 
- pkg_get_variable(  )
+pkg_get_variable(  )
 
- Examples
+  For example:
 
- .. code-block:: cmake
+  .. code-block:: cmake
 
 pkg_get_variable(GI_GIRDIR gobject-introspection-1.0 girdir)
 #]]

---

Summary of changes:
 Modules/FindPkgConfig.cmake |8 
 1 file changed, 4 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.3.2-3159-g98366c3

2015-09-21 Thread 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  98366c3d0b5bd189e0aee10bf8846b38f07d4ccc (commit)
   via  51b83f1445521a210eee7e92ed03aff8fe8e9dc6 (commit)
  from  7defd7c0006bbdf054c85ada3508b8bb7487da86 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=98366c3d0b5bd189e0aee10bf8846b38f07d4ccc
commit 98366c3d0b5bd189e0aee10bf8846b38f07d4ccc
Merge: 7defd7c 51b83f1
Author: Brad King 
AuthorDate: Mon Sep 21 09:39:33 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:39:33 2015 -0400

Merge topic 'pkg-config-variable-function' into next

51b83f14 FindPkgConfig: add a command to query arbitrary variables


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=51b83f1445521a210eee7e92ed03aff8fe8e9dc6
commit 51b83f1445521a210eee7e92ed03aff8fe8e9dc6
Author: Ben Boeckel 
AuthorDate: Thu Sep 17 21:05:29 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 09:39:26 2015 -0400

FindPkgConfig: add a command to query arbitrary variables

diff --git a/Help/release/dev/pkg-config-variable-function.rst 
b/Help/release/dev/pkg-config-variable-function.rst
new file mode 100644
index 000..e181d13
--- /dev/null
+++ b/Help/release/dev/pkg-config-variable-function.rst
@@ -0,0 +1,6 @@
+pkg-config-variable-function
+
+
+* The :module:`FindPkgConfig` learned a new :command:`pkg_get_variable`
+  command which may be used to query for arbitrary variables from a package
+  (such as for related tools or data and plugin install paths).
diff --git a/Modules/FindPkgConfig.cmake b/Modules/FindPkgConfig.cmake
index 0f2e22d..e822b9c 100644
--- a/Modules/FindPkgConfig.cmake
+++ b/Modules/FindPkgConfig.cmake
@@ -91,6 +91,26 @@ macro(_pkgconfig_invoke _pkglist _prefix _varname _regexp)
   endif()
 endmacro()
 
+#[[.rst:
+.. command:: pkg_get_variable
+
+  Retrieves the value of a variable from a package::
+
+pkg_get_variable(  )
+
+  For example:
+
+  .. code-block:: cmake
+
+pkg_get_variable(GI_GIRDIR gobject-introspection-1.0 girdir)
+#]]
+function (pkg_get_variable result pkg variable)
+  _pkgconfig_invoke("${pkg}" "prefix" "result" "" "--variable=${variable}")
+  set("${result}"
+"${prefix_result}"
+PARENT_SCOPE)
+endfunction ()
+
 # Invokes pkgconfig two times; once without '--static' and once with
 # '--static'
 macro(_pkgconfig_invoke_dyn _pkglist _prefix _varname cleanup_regexp)
@@ -356,9 +376,9 @@ macro(_pkg_check_modules_internal _is_required _is_silent 
_no_cmake_path _no_cma
 endif()
 
 _pkgconfig_invoke(${_pkg_check_modules_pkg} "${_pkg_check_prefix}" 
VERSION""   --modversion )
-_pkgconfig_invoke(${_pkg_check_modules_pkg} "${_pkg_check_prefix}" 
PREFIX ""   --variable=prefix )
-_pkgconfig_invoke(${_pkg_check_modules_pkg} "${_pkg_check_prefix}" 
INCLUDEDIR ""   --variable=includedir )
-_pkgconfig_invoke(${_pkg_check_modules_pkg} "${_pkg_check_prefix}" 
LIBDIR ""   --variable=libdir )
+pkg_get_variable("${_pkg_check_prefix}_PREFIX" 
${_pkg_check_modules_pkg} "prefix")
+pkg_get_variable("${_pkg_check_prefix}_INCLUDEDIR" 
${_pkg_check_modules_pkg} "includedir")
+pkg_get_variable("${_pkg_check_prefix}_LIBDIR" 
${_pkg_check_modules_pkg} "libdir")
 
 if (NOT ${_is_silent})
   message(STATUS "  Found ${_pkg_check_modules_pkg}, version 
${_pkgconfig_VERSION}")
diff --git a/Tests/RunCMake/FindPkgConfig/FindPkgConfig_GET_VARIABLE-stdout.txt 
b/Tests/RunCMake/FindPkgConfig/FindPkgConfig_GET_VARIABLE-stdout.txt
new file mode 100644
index 000..5f211eb
--- /dev/null
+++ b/Tests/RunCMake/FindPkgConfig/FindPkgConfig_GET_VARIABLE-stdout.txt
@@ -0,0 +1 @@
+-- g_ir_scanner: .*/g-ir-scanner
diff --git a/Tests/RunCMake/FindPkgConfig/FindPkgConfig_GET_VARIABLE.cmake 
b/Tests/RunCMake/FindPkgConfig/FindPkgConfig_GET_VARIABLE.cmake
new file mode 100644
index 000..c85efaa
--- /dev/null
+++ b/Tests/RunCMake/FindPkgConfig/FindPkgConfig_GET_VARIABLE.cmake
@@ -0,0 +1,9 @@
+find_package(PkgConfig REQUIRED)
+pkg_check_modules(GOBJECT_INTROSPECTION QUIET gobject-introspection-1.0)
+
+if (GOBJECT_INTROSPECTION_FOUND)
+  pkg_get_variable(g_ir_scanner gobject-introspection-1.0 g_ir_scanner)
+  message(STATUS "g_ir_scanner: ${g_ir_scanner}")
+else ()
+  message(STATUS "g_ir_scanner: skipping test; gobject-introspection-1.0 not 
found /g-ir-scanner")
+endif ()
diff --git 

[Cmake-commits] CMake branch, master, updated. v3.3.2-1244-gcec45e2

2015-09-21 Thread 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  cec45e27f6dc2657b00902bcaef5bd93ae16ead7 (commit)
   via  51b83f1445521a210eee7e92ed03aff8fe8e9dc6 (commit)
   via  7f7f1eecfd6834b8a499f0fde49469a10a1b2905 (commit)
  from  1f4358134f2cf5b9fe72088d6534084a8fb71a52 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=cec45e27f6dc2657b00902bcaef5bd93ae16ead7
commit cec45e27f6dc2657b00902bcaef5bd93ae16ead7
Merge: 1f43581 51b83f1
Author: Brad King 
AuthorDate: Mon Sep 21 09:39:36 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:39:36 2015 -0400

Merge topic 'pkg-config-variable-function'

51b83f14 FindPkgConfig: add a command to query arbitrary variables
7f7f1eec FindPkgConfig: use execute_process to strip trailing whitespace


---

Summary of changes:
 Help/release/dev/pkg-config-variable-function.rst  |6 
 Modules/FindPkgConfig.cmake|   30 
 .../FindPkgConfig_GET_VARIABLE-stdout.txt  |1 +
 .../FindPkgConfig/FindPkgConfig_GET_VARIABLE.cmake |9 ++
 Tests/RunCMake/FindPkgConfig/RunCMakeTest.cmake|6 
 5 files changed, 47 insertions(+), 5 deletions(-)
 create mode 100644 Help/release/dev/pkg-config-variable-function.rst
 create mode 100644 
Tests/RunCMake/FindPkgConfig/FindPkgConfig_GET_VARIABLE-stdout.txt
 create mode 100644 
Tests/RunCMake/FindPkgConfig/FindPkgConfig_GET_VARIABLE.cmake


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.3.2-3161-g451505b

2015-09-21 Thread 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  451505b3bb8a400552c99d31e9f0c26f15fa3059 (commit)
   via  cec45e27f6dc2657b00902bcaef5bd93ae16ead7 (commit)
  from  98366c3d0b5bd189e0aee10bf8846b38f07d4ccc (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=451505b3bb8a400552c99d31e9f0c26f15fa3059
commit 451505b3bb8a400552c99d31e9f0c26f15fa3059
Merge: 98366c3 cec45e2
Author: Brad King 
AuthorDate: Mon Sep 21 09:39:51 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 09:39:51 2015 -0400

Merge branch 'master' into next


---

Summary of changes:


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


[cmake-developers] [CMake 0015753]: CMake cannot detect changes in nested header files when using '-iquote'

2015-09-21 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=15753 
== 
Reported By:danilcha
Assigned To:
== 
Project:CMake
Issue ID:   15753
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2015-09-21 08:49 EDT
Last Modified:  2015-09-21 08:49 EDT
== 
Summary:CMake cannot detect changes in nested header files
when using '-iquote'
Description: 
Create a new project with such CMakeLists.txt:

cmake_minimum_required(VERSION 3.3)
project(test)
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -iquote ${CMAKE_CURRENT_SOURCE_DIR}")
add_executable(test-iquote main.cpp dir/1.h dir/2.h)

And such structure:

CMakeLists.txt
Main.cpp  (contains #include "dir/1.h")
dir\
1.h   (contains #include "dir/2.h")
2.h

Build. Then modify 2.h. Build again. Nothing will happen, it will just say
'[100%] Built target test-iquote'. 

Additional Information: 
Tried with both clang and GCC. GNU Make 3.81.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-09-21 08:49 danilcha   New Issue
==

-- 

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-commits] CMake branch, next, updated. v3.3.2-3155-g47462f4

2015-09-21 Thread 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  47462f48357918309a2019510586bae2410ddcb7 (commit)
   via  0ef2e214ed204ae9ef41ce01d5eaf6ea92c81a57 (commit)
   via  70c0cc72f085b4252e8b3578cdf1624b36c4e2c8 (commit)
   via  71c67e83bfe65f449b69b610b5be71164e5eee64 (commit)
   via  936a95d4059ce3c57b79a1bf28dd4f2bdf26ba29 (commit)
  from  dec07adacff8a62c0c68b4ab3caf0f2be03aa45a (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=47462f48357918309a2019510586bae2410ddcb7
commit 47462f48357918309a2019510586bae2410ddcb7
Merge: dec07ad 0ef2e21
Author: Brad King 
AuthorDate: Mon Sep 21 09:30:01 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:30:01 2015 -0400

Merge topic 'ctest-variable-docs' into next

0ef2e214 Help: document CTEST_CUSTOM_* variables
70c0cc72 ctest_read_custom_files: mention that ctest does this automatically
71c67e83 CTEST_CUSTOM_*: treat variables as lists
936a95d4 CTestCoverageCollectGCOV: replace tabulators


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0ef2e214ed204ae9ef41ce01d5eaf6ea92c81a57
commit 0ef2e214ed204ae9ef41ce01d5eaf6ea92c81a57
Author: Ben Boeckel 
AuthorDate: Thu Sep 17 10:57:46 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 09:27:54 2015 -0400

Help: document CTEST_CUSTOM_* variables

diff --git a/Help/manual/cmake-variables.7.rst 
b/Help/manual/cmake-variables.7.rst
index 660d544..991cd55 100644
--- a/Help/manual/cmake-variables.7.rst
+++ b/Help/manual/cmake-variables.7.rst
@@ -374,8 +374,23 @@ Variables for CTest
/variable/CTEST_COVERAGE_COMMAND
/variable/CTEST_COVERAGE_EXTRA_FLAGS
/variable/CTEST_CURL_OPTIONS
+   /variable/CTEST_CUSTOM_COVERAGE_EXCLUDE
+   /variable/CTEST_CUSTOM_ERROR_EXCEPTION
+   /variable/CTEST_CUSTOM_ERROR_MATCH
+   /variable/CTEST_CUSTOM_ERROR_POST_CONTEXT
+   /variable/CTEST_CUSTOM_ERROR_PRE_CONTEXT
/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE
+   /variable/CTEST_CUSTOM_MAXIMUM_NUMBER_OF_ERRORS
+   /variable/CTEST_CUSTOM_MAXIMUM_NUMBER_OF_WARNINGS
/variable/CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE
+   /variable/CTEST_CUSTOM_MEMCHECK_IGNORE
+   /variable/CTEST_CUSTOM_POST_MEMCHECK
+   /variable/CTEST_CUSTOM_POST_TEST
+   /variable/CTEST_CUSTOM_PRE_MEMCHECK
+   /variable/CTEST_CUSTOM_PRE_TEST
+   /variable/CTEST_CUSTOM_TEST_IGNORE
+   /variable/CTEST_CUSTOM_WARNING_EXCEPTION
+   /variable/CTEST_CUSTOM_WARNING_MATCH
/variable/CTEST_CVS_CHECKOUT
/variable/CTEST_CVS_COMMAND
/variable/CTEST_CVS_UPDATE_OPTIONS
@@ -385,6 +400,7 @@ Variables for CTest
/variable/CTEST_DROP_SITE_CDASH
/variable/CTEST_DROP_SITE_PASSWORD
/variable/CTEST_DROP_SITE_USER
+   /variable/CTEST_EXTRA_COVERAGE_GLOB
/variable/CTEST_GIT_COMMAND
/variable/CTEST_GIT_UPDATE_CUSTOM
/variable/CTEST_GIT_UPDATE_OPTIONS
diff --git a/Help/variable/CTEST_CUSTOM_COVERAGE_EXCLUDE.rst 
b/Help/variable/CTEST_CUSTOM_COVERAGE_EXCLUDE.rst
new file mode 100644
index 000..946114c
--- /dev/null
+++ b/Help/variable/CTEST_CUSTOM_COVERAGE_EXCLUDE.rst
@@ -0,0 +1,8 @@
+CTEST_CUSTOM_COVERAGE_EXCLUDE
+-
+
+A list of regular expressions which will be used to exclude files by their
+path from coverage output by the :command:`ctest_coverage` command.
+
+.. |CTEST_CUSTOM_XXX| replace:: CTEST_CUSTOM_COVERAGE_EXCLUDE
+.. include:: CTEST_CUSTOM_XXX.txt
diff --git a/Help/variable/CTEST_CUSTOM_ERROR_EXCEPTION.rst 
b/Help/variable/CTEST_CUSTOM_ERROR_EXCEPTION.rst
new file mode 100644
index 000..cfb1093
--- /dev/null
+++ b/Help/variable/CTEST_CUSTOM_ERROR_EXCEPTION.rst
@@ -0,0 +1,8 @@
+CTEST_CUSTOM_ERROR_EXCEPTION
+
+
+A list of regular expressions which will be used to exclude when detecting
+error messages in build outputs by the :command:`ctest_test` command.
+
+.. |CTEST_CUSTOM_XXX| replace:: CTEST_CUSTOM_ERROR_EXCEPTION
+.. include:: CTEST_CUSTOM_XXX.txt
diff --git a/Help/variable/CTEST_CUSTOM_ERROR_MATCH.rst 
b/Help/variable/CTEST_CUSTOM_ERROR_MATCH.rst
new file mode 100644
index 000..dbb9c19
--- /dev/null
+++ b/Help/variable/CTEST_CUSTOM_ERROR_MATCH.rst
@@ -0,0 +1,8 @@
+CTEST_CUSTOM_ERROR_MATCH
+
+
+A list of regular expressions which will be used to detect error messages in
+build outputs by the :command:`ctest_test` command.
+
+.. |CTEST_CUSTOM_XXX| replace:: CTEST_CUSTOM_ERROR_MATCH
+.. include:: CTEST_CUSTOM_XXX.txt
diff --git a/Help/variable/CTEST_CUSTOM_ERROR_POST_CONTEXT.rst 

[Cmake-commits] CMake branch, next, updated. v3.3.2-3172-gda378b6

2015-09-21 Thread Rolf Eike Beer
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  da378b6182c89d31d97524efd086fcb119ef0572 (commit)
   via  8633df503365e43cb966938bc3bb895a08da0862 (commit)
  from  f7b8e9fc7446ba57138811776dac5a06acfd3f06 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=da378b6182c89d31d97524efd086fcb119ef0572
commit da378b6182c89d31d97524efd086fcb119ef0572
Merge: f7b8e9f 8633df5
Author: Rolf Eike Beer 
AuthorDate: Mon Sep 21 12:02:46 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 12:02:46 2015 -0400

Merge topic 'Threads-CXX' into next

8633df50 FindThreads: add simple testcase


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8633df503365e43cb966938bc3bb895a08da0862
commit 8633df503365e43cb966938bc3bb895a08da0862
Author: Rolf Eike Beer 
AuthorDate: Mon Sep 21 17:57:33 2015 +0200
Commit: Rolf Eike Beer 
CommitDate: Mon Sep 21 17:57:33 2015 +0200

FindThreads: add simple testcase

diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt
index fff04ce..dc65a2e 100644
--- a/Tests/CMakeLists.txt
+++ b/Tests/CMakeLists.txt
@@ -1365,6 +1365,8 @@ ${CMake_BINARY_DIR}/bin/cmake -DDIR=dev -P 
${CMake_SOURCE_DIR}/Utilities/Release
 add_subdirectory(FindOpenSSL)
   endif()
 
+  add_subdirectory(FindThreads)
+
   # Matlab module
   if(CMake_TEST_FindMatlab)
 ADD_TEST_MACRO(FindMatlab.basic_checks  ${CMAKE_CTEST_COMMAND} -C 
$)
diff --git a/Tests/FindThreads/C-only/CMakeLists.txt 
b/Tests/FindThreads/C-only/CMakeLists.txt
new file mode 100644
index 000..c366b79
--- /dev/null
+++ b/Tests/FindThreads/C-only/CMakeLists.txt
@@ -0,0 +1,8 @@
+cmake_minimum_required(VERSION 3.3 FATAL_ERROR)
+project(FindThreads C)
+
+set(CMAKE_THREAD_PREFER_PTHREAD On)
+find_package(Threads REQUIRED)
+
+add_executable(thr 
${CMAKE_CURRENT_SOURCE_DIR}/../../../Modules/CheckForPthreads.c)
+target_link_libraries(thr Threads::Threads)
diff --git a/Tests/FindThreads/CMakeLists.txt b/Tests/FindThreads/CMakeLists.txt
new file mode 100644
index 000..36518a3
--- /dev/null
+++ b/Tests/FindThreads/CMakeLists.txt
@@ -0,0 +1,9 @@
+add_test(NAME FindThreads.C-only COMMAND ${CMAKE_CTEST_COMMAND}
+  --build-and-test
+  "${CMake_SOURCE_DIR}/Tests/FindThreads/C-only"
+  "${CMake_BINARY_DIR}/Tests/FindThreads/C-only"
+  ${build_generator_args}
+  --build-project FindThreads_C-only
+  --build-options ${build_options}
+  --test-command ${CMAKE_CTEST_COMMAND} -V
+  )

---

Summary of changes:
 Tests/CMakeLists.txt|2 ++
 Tests/FindThreads/C-only/CMakeLists.txt |8 
 Tests/FindThreads/CMakeLists.txt|9 +
 3 files changed, 19 insertions(+)
 create mode 100644 Tests/FindThreads/C-only/CMakeLists.txt
 create mode 100644 Tests/FindThreads/CMakeLists.txt


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


Re: [cmake-developers] generator expression for path slash conversion

2015-09-21 Thread Kislinskiy, Stefan
Ah, thank you very much! I was confused as the distinction between WIN32 and 
UNIX worked nevertheless.

-Original Message-
From: Brad King [mailto:brad.k...@kitware.com] 
Sent: Montag, 21. September 2015 16:17
To: Kislinskiy, Stefan
Cc: CHEVRIER, Marc; cmake-developers@cmake.org; James Johnston
Subject: Re: [cmake-developers] generator expression for path slash conversion

On 09/21/2015 10:05 AM, Kislinskiy, Stefan wrote:
> if(MSYS)
>   check(test_shell_path "/c/shell/path")
> elseif(WIN32)
>   check(test_shell_path "c:shellpath")
> elseif(UNIX)
>   check(test_shell_path "c:/shell/path")
> endif()
> 
> No matter what I'm doing, it always ends up in the WIN32 branch with 
> FORWARD slashes. Additionally the drive letter is NOT converted to a posix 
> path as it should be the case for MSYS. I tried MSYS from the official MinGW 
> package, and I tried the MSYS2 installer. In both cases I called cmake from 
> MinGW-sh, MSYS-sh, and even cmd.exe. I used the "MSYS Makefiles" Generator. 
> In addition I tried the "MinGW Makefiles" generator just to check if 
> "if(MINGW)" is working... which also fails. The configuring/generating itself 
> is working.. Any ideas?

The code in the check-part4.cmake script runs in a cmake script (via "cmake 
-P").  That does not have any information about the configuration of the 
project, generator used, or target platform.
If you need this information it needs to be passed in through additional 
"-Dvar=val" arguments prior to the -P argument.

-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-commits] CMake branch, next, updated. v3.3.2-3170-gf7b8e9f

2015-09-21 Thread Ben Boeckel
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  f7b8e9fc7446ba57138811776dac5a06acfd3f06 (commit)
   via  1d7e2081cd4adc0e1dc35c50d3fcd7cc785d4816 (commit)
  from  f7b4f40af838f66acbef763f215d697dd12cdff6 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f7b8e9fc7446ba57138811776dac5a06acfd3f06
commit f7b8e9fc7446ba57138811776dac5a06acfd3f06
Merge: f7b4f40 1d7e208
Author: Ben Boeckel 
AuthorDate: Mon Sep 21 11:53:03 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 11:53:03 2015 -0400

Merge topic 'ctest-variable-docs' into next

1d7e2081 fixup! Help: document CTEST_CUSTOM_* variables


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1d7e2081cd4adc0e1dc35c50d3fcd7cc785d4816
commit 1d7e2081cd4adc0e1dc35c50d3fcd7cc785d4816
Author: Ben Boeckel 
AuthorDate: Mon Sep 21 11:34:31 2015 -0400
Commit: Ben Boeckel 
CommitDate: Mon Sep 21 11:50:41 2015 -0400

fixup! Help: document CTEST_CUSTOM_* variables

diff --git a/Help/variable/CTEST_CUSTOM_COVERAGE_EXCLUDE.rst 
b/Help/variable/CTEST_CUSTOM_COVERAGE_EXCLUDE.rst
index 946114c..d5893c9 100644
--- a/Help/variable/CTEST_CUSTOM_COVERAGE_EXCLUDE.rst
+++ b/Help/variable/CTEST_CUSTOM_COVERAGE_EXCLUDE.rst
@@ -4,5 +4,4 @@ CTEST_CUSTOM_COVERAGE_EXCLUDE
 A list of regular expressions which will be used to exclude files by their
 path from coverage output by the :command:`ctest_coverage` command.
 
-.. |CTEST_CUSTOM_XXX| replace:: CTEST_CUSTOM_COVERAGE_EXCLUDE
 .. include:: CTEST_CUSTOM_XXX.txt
diff --git a/Help/variable/CTEST_CUSTOM_ERROR_EXCEPTION.rst 
b/Help/variable/CTEST_CUSTOM_ERROR_EXCEPTION.rst
index cfb1093..cd65ae3 100644
--- a/Help/variable/CTEST_CUSTOM_ERROR_EXCEPTION.rst
+++ b/Help/variable/CTEST_CUSTOM_ERROR_EXCEPTION.rst
@@ -4,5 +4,4 @@ CTEST_CUSTOM_ERROR_EXCEPTION
 A list of regular expressions which will be used to exclude when detecting
 error messages in build outputs by the :command:`ctest_test` command.
 
-.. |CTEST_CUSTOM_XXX| replace:: CTEST_CUSTOM_ERROR_EXCEPTION
 .. include:: CTEST_CUSTOM_XXX.txt
diff --git a/Help/variable/CTEST_CUSTOM_ERROR_MATCH.rst 
b/Help/variable/CTEST_CUSTOM_ERROR_MATCH.rst
index dbb9c19..558f5e5 100644
--- a/Help/variable/CTEST_CUSTOM_ERROR_MATCH.rst
+++ b/Help/variable/CTEST_CUSTOM_ERROR_MATCH.rst
@@ -4,5 +4,4 @@ CTEST_CUSTOM_ERROR_MATCH
 A list of regular expressions which will be used to detect error messages in
 build outputs by the :command:`ctest_test` command.
 
-.. |CTEST_CUSTOM_XXX| replace:: CTEST_CUSTOM_ERROR_MATCH
 .. include:: CTEST_CUSTOM_XXX.txt
diff --git a/Help/variable/CTEST_CUSTOM_ERROR_POST_CONTEXT.rst 
b/Help/variable/CTEST_CUSTOM_ERROR_POST_CONTEXT.rst
index f4ee2e8..614859b 100644
--- a/Help/variable/CTEST_CUSTOM_ERROR_POST_CONTEXT.rst
+++ b/Help/variable/CTEST_CUSTOM_ERROR_POST_CONTEXT.rst
@@ -4,5 +4,4 @@ CTEST_CUSTOM_ERROR_POST_CONTEXT
 The number of lines to include as context which follow an error message by the
 :command:`ctest_test` command. The default is 10.
 
-.. |CTEST_CUSTOM_XXX| replace:: CTEST_CUSTOM_ERROR_POST_CONTEXT
 .. include:: CTEST_CUSTOM_XXX.txt
diff --git a/Help/variable/CTEST_CUSTOM_ERROR_PRE_CONTEXT.rst 
b/Help/variable/CTEST_CUSTOM_ERROR_PRE_CONTEXT.rst
index b1b3e0d..74dc47a 100644
--- a/Help/variable/CTEST_CUSTOM_ERROR_PRE_CONTEXT.rst
+++ b/Help/variable/CTEST_CUSTOM_ERROR_PRE_CONTEXT.rst
@@ -4,5 +4,4 @@ CTEST_CUSTOM_ERROR_PRE_CONTEXT
 The number of lines to include as context which precede an error message by
 the :command:`ctest_test` command. The default is 10.
 
-.. |CTEST_CUSTOM_XXX| replace:: CTEST_CUSTOM_ERROR_PRE_CONTEXT
 .. include:: CTEST_CUSTOM_XXX.txt
diff --git a/Help/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.rst 
b/Help/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.rst
index 524be5d..5aeae88 100644
--- a/Help/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.rst
+++ b/Help/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.rst
@@ -5,5 +5,4 @@ When saving a failing test's output, this is the maximum size, 
in bytes, that
 will be collected by the :command:`ctest_test` command. Defaults to 307200
 (300 KiB).
 
-.. |CTEST_CUSTOM_XXX| replace:: CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE
 .. include:: CTEST_CUSTOM_XXX.txt
diff --git a/Help/variable/CTEST_CUSTOM_MAXIMUM_NUMBER_OF_ERRORS.rst 
b/Help/variable/CTEST_CUSTOM_MAXIMUM_NUMBER_OF_ERRORS.rst
index 3213d34..920cb04 100644
--- a/Help/variable/CTEST_CUSTOM_MAXIMUM_NUMBER_OF_ERRORS.rst
+++ 

Re: [cmake-developers] Generator expressions for install destination

2015-09-21 Thread Brad King
On 09/18/2015 03:49 PM, Robert Goulet wrote:
> Here's a version that is more conservative. It doesn't change
> the install(EXPORT) behavior.

> install(TARGET) already supported genex

Right.  I'd forgotten about these changes:

 install: Allow generator expressions in TARGETS DESTINATION (#14317)
 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f30022eb
 http://www.cmake.org/Bug/view.php?id=14317#c37959

>, so basically this patch adds install(FILES) destination genex.

Okay.  I see many hunks of this form:

> -   this->Destination,
> +   this->GetDestination(),

Making the Destination member private and moving GetDestination()
back into cmInstallGenerator is refactoring that should be split
out into its own commit.  Note that GetDestination() was removed
from the base class here:

 cmInstallGenerator: Move GetDestination to subclasses that need it
 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f1db

Restoring it will need a justification in the commit message.
I'm concerned about having both overloads avilable:

> +  std::string GetDestination() const;
> +  std::string GetDestination(std::string const& config) const;

when only one is safe to call from each subclass.  This is why the
above-linked commit removed the method from cmInstallGenerator in
favor of having the needed overload in each subclass.

> -  cmInstallGenerator(const char* destination,
> +  cmInstallGenerator(cmMakefile* mf,
> + const char* destination,

This and its related changes are also refactoring that should go
in its own commit.

> +  // We need per-config actions if destination have generator expressions.
> +  if(cmGeneratorExpression::Find(Destination) != std::string::npos)
> +{
> +this->ActionsPerConfig = true;
> +}

Was this the solution to the availability of a configuration for
calls to GetDestination()?

> Perhaps we should update the Help to only mention install(FILES)
> destination instead of all variations of install?

Yes, the actual availability of the behavior should be documented.

Also please look at making the test suite actually verify that
the installation works as expected.  The above-linked commit
f30022eb adds a test that fails if generator expressions are
not evaluated to the correct values.

Thanks,
-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-commits] CMake branch, next, updated. v3.3.2-3163-ge723550

2015-09-21 Thread 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  e723550b1a75d8a9e7b4615bbf7037eb2ba1 (commit)
   via  2c738c945175b554db1e79672bff076620185063 (commit)
  from  451505b3bb8a400552c99d31e9f0c26f15fa3059 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e723550b1a75d8a9e7b4615bbf7037eb2ba1
commit e723550b1a75d8a9e7b4615bbf7037eb2ba1
Merge: 451505b 2c738c9
Author: Brad King 
AuthorDate: Mon Sep 21 09:44:57 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 09:44:57 2015 -0400

Merge topic 'revert-conflicting-unfinished-topics' into next

2c738c94 Revert topics 'lib_depends-in-property' and 
'restrict-shlib-link-flags-to-enable-exports'


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2c738c945175b554db1e79672bff076620185063
commit 2c738c945175b554db1e79672bff076620185063
Author: Brad King 
AuthorDate: Mon Sep 21 09:43:57 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 09:43:57 2015 -0400

Revert topics 'lib_depends-in-property' and 
'restrict-shlib-link-flags-to-enable-exports'

They conflict and each need to be rebased and revised.

diff --git a/Help/command/try_compile.rst b/Help/command/try_compile.rst
index 28dae80..1ed24df 100644
--- a/Help/command/try_compile.rst
+++ b/Help/command/try_compile.rst
@@ -100,7 +100,6 @@ If set, the following variables are passed in to the 
generated
 try_compile CMakeLists.txt to initialize compile target properties with
 default values:
 
-* :variable:`CMAKE_ENABLE_EXPORTS`
 * :variable:`CMAKE_LINK_SEARCH_START_STATIC`
 * :variable:`CMAKE_LINK_SEARCH_END_STATIC`
 * :variable:`CMAKE_POSITION_INDEPENDENT_CODE`
@@ -108,7 +107,5 @@ default values:
 If :policy:`CMP0056` is set to ``NEW``, then
 :variable:`CMAKE_EXE_LINKER_FLAGS` is passed in as well.
 
-The current setting of :policy:`CMP0065` is set in the generated project.
-
 Set the :variable:`CMAKE_TRY_COMPILE_CONFIGURATION` variable to choose
 a build configuration.
diff --git a/Help/manual/cmake-policies.7.rst b/Help/manual/cmake-policies.7.rst
index 38047ef..590f10d 100644
--- a/Help/manual/cmake-policies.7.rst
+++ b/Help/manual/cmake-policies.7.rst
@@ -122,5 +122,3 @@ All Policies
/policy/CMP0062
/policy/CMP0063
/policy/CMP0064
-   /policy/CMP0065
-   /policy/CMP0066
diff --git a/Help/manual/cmake-variables.7.rst 
b/Help/manual/cmake-variables.7.rst
index 1fa117f..e0dbdeb 100644
--- a/Help/manual/cmake-variables.7.rst
+++ b/Help/manual/cmake-variables.7.rst
@@ -245,7 +245,6 @@ Variables that Control the Build
/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG
/variable/CMAKE_CONFIG_POSTFIX
/variable/CMAKE_DEBUG_POSTFIX
-   /variable/CMAKE_ENABLE_EXPORTS
/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG
/variable/CMAKE_EXE_LINKER_FLAGS
/variable/CMAKE_Fortran_FORMAT
diff --git a/Help/policy/CMP0065.rst b/Help/policy/CMP0065.rst
deleted file mode 100644
index fbdb4a9..000
--- a/Help/policy/CMP0065.rst
+++ /dev/null
@@ -1,14 +0,0 @@
-CMP0065

-
-Restrict the addition of CMAKE_SHARED_LIBRARY_LINK__FLAGS
-to executable targets only when the :prop_tgt:`ENABLE_EXPORTS`
-target property is turned on.
-
-The ``OLD`` behavior of this policy is to always use the additional link
-flags when linking executables regardless of the value of the
-:prop_tgt:`ENABLE_EXPORTS` target property.
-
-The ``NEW`` behavior of this policy is to only use the additional link
-flags when linking executables if the :prop_tgt:`ENABLE_EXPORTS` target
-property is set to ``True``.
diff --git a/Help/policy/CMP0066.rst b/Help/policy/CMP0066.rst
deleted file mode 100644
index afe21ee..000
--- a/Help/policy/CMP0066.rst
+++ /dev/null
@@ -1,16 +0,0 @@
-CMP0066

-
-Deprecate the ``_LIB_DEPENDS`` variables.
-
-Instead, the values are stored as global properties.
-
-The ``OLD`` behavior for this policy is to set ``_LIB_DEPENDS`` variables. The
-``NEW`` behavior is to only store them as properties.
-
-This policy was introduced in CMake version 3.4.  CMake version
-|release| warns when the policy is not set and uses ``OLD`` behavior.  Use
-the :command:`cmake_policy()` command to set it to ``OLD`` or ``NEW``
-explicitly.
-
-.. include:: DEPRECATED.txt
diff --git a/Help/prop_tgt/ENABLE_EXPORTS.rst b/Help/prop_tgt/ENABLE_EXPORTS.rst
index dfd4af7..283f5a8 100644
--- a/Help/prop_tgt/ENABLE_EXPORTS.rst
+++ b/Help/prop_tgt/ENABLE_EXPORTS.rst
@@ -7,7 +7,7 @@ Normally an executable does not export any symbols because it 
is the
 final program.  It is 

[cmake-developers] [CMake 0015755]: add_dependencies() undoes include_directories()

2015-09-21 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=15755 
== 
Reported By:Dimitri Merejkowsky
Assigned To:
== 
Project:CMake
Issue ID:   15755
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2015-09-21 12:27 EDT
Last Modified:  2015-09-21 12:27 EDT
== 
Summary:add_dependencies() undoes include_directories()
Description: 
Calling add_dependencies() between two targets causes some calls to
include_directories() to no longer be taken into account

Steps to Reproduce: 
See attached project.

$ mkdir b1
$ cmake ..
$ make
...
[ 25%] Linking C executable eggs
CMakeFiles/eggs.dir/eggs.c.o: In function `main':
eggs.c:(.text+0xa): undefined reference to `spam

$ mkdir b2
$ cmake -DADD_DEPENDENCIES=ON ..
$ make
[ 25%] Building C object spam/CMakeFiles/spam.dir/src/spam.c.o
spam/src/spam.c:1:23: fatal error: spam/spam.h: No such file or directory

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-09-21 12:27 Dimitri MerejkowskyNew Issue   

2015-09-21 12:27 Dimitri MerejkowskyFile Added: spam.zip

==

-- 

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-commits] CMake branch, next, updated. v3.3.2-3165-g8831ba6

2015-09-21 Thread 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  8831ba64a606c4eae7e16e41a83533711c075bf0 (commit)
   via  402bf096ec4aac75af096c3708ce51efaf4589d0 (commit)
  from  e723550b1a75d8a9e7b4615bbf7037eb2ba1 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8831ba64a606c4eae7e16e41a83533711c075bf0
commit 8831ba64a606c4eae7e16e41a83533711c075bf0
Merge: e723550 402bf09
Author: Brad King 
AuthorDate: Mon Sep 21 10:07:11 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 10:07:11 2015 -0400

Merge topic 'fix-policy-CMP0064-version' into next

402bf096 CMP0064: Fix recorded version of introduction to be 3.4


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=402bf096ec4aac75af096c3708ce51efaf4589d0
commit 402bf096ec4aac75af096c3708ce51efaf4589d0
Author: Brad King 
AuthorDate: Mon Sep 21 10:05:02 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 10:05:02 2015 -0400

CMP0064: Fix recorded version of introduction to be 3.4

This policy was added for CMake 3.4 but accidentally recorded as 3.3.
Fix this and update the RunCMake.CMP0064 test WARN case accordingly.

diff --git a/Source/cmPolicies.h b/Source/cmPolicies.h
index a791b89..b20c7a9 100644
--- a/Source/cmPolicies.h
+++ b/Source/cmPolicies.h
@@ -220,7 +220,7 @@ class cmPolicy;
 3, 3, 0, cmPolicies::WARN) \
   SELECT(POLICY, CMP0064, \
 "Support new TEST if() operator.", \
-3, 3, 0, cmPolicies::WARN)
+3, 4, 0, cmPolicies::WARN)
 
 #define CM_SELECT_ID(F, A1, A2, A3, A4, A5, A6) F(A1)
 #define CM_FOR_EACH_POLICY_ID(POLICY) \
diff --git a/Tests/RunCMake/CMP0064/CMP0064-WARN-stderr.txt 
b/Tests/RunCMake/CMP0064/CMP0064-WARN-stderr.txt
new file mode 100644
index 000..71f1ab7
--- /dev/null
+++ b/Tests/RunCMake/CMP0064/CMP0064-WARN-stderr.txt
@@ -0,0 +1,10 @@
+CMake Warning \(dev\) at CMP0064-WARN.cmake:3 \(if\):
+  Policy CMP0064 is not set: Support new TEST if\(\) operator.  Run "cmake
+  --help-policy CMP0064" for policy details.  Use the cmake_policy command to
+  set the policy and suppress this warning.
+
+  TEST will be interpreted as an operator when the policy is set to NEW.
+  Since the policy is not set the OLD behavior will be used.
+Call Stack \(most recent call first\):
+  CMakeLists.txt:3 \(include\)
+This warning is for project developers.  Use -Wno-dev to suppress it.
diff --git a/Tests/RunCMake/CMP0064/CMP0064-WARN.cmake 
b/Tests/RunCMake/CMP0064/CMP0064-WARN.cmake
index bffd3f3..8f26ec6 100644
--- a/Tests/RunCMake/CMP0064/CMP0064-WARN.cmake
+++ b/Tests/RunCMake/CMP0064/CMP0064-WARN.cmake
@@ -1,4 +1,4 @@
-cmake_policy(SET CMP0064 OLD)
+
 
 if(TEST)
   message(FATAL_ERROR "TEST was not recognized to be undefined")

---

Summary of changes:
 Source/cmPolicies.h|2 +-
 Tests/RunCMake/CMP0064/CMP0064-WARN-stderr.txt |   10 ++
 Tests/RunCMake/CMP0064/CMP0064-WARN.cmake  |2 +-
 3 files changed, 12 insertions(+), 2 deletions(-)
 create mode 100644 Tests/RunCMake/CMP0064/CMP0064-WARN-stderr.txt


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.3.2-3168-gf7b4f40

2015-09-21 Thread 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  f7b4f40af838f66acbef763f215d697dd12cdff6 (commit)
   via  b15f4e9b86bc3dc31b6a01c0ffc30747f467ec1f (commit)
   via  9784af1b50a142c0160058734c7e12cee5f2a15e (commit)
  from  8831ba64a606c4eae7e16e41a83533711c075bf0 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f7b4f40af838f66acbef763f215d697dd12cdff6
commit f7b4f40af838f66acbef763f215d697dd12cdff6
Merge: 8831ba6 b15f4e9
Author: Brad King 
AuthorDate: Mon Sep 21 10:20:54 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 10:20:54 2015 -0400

Merge topic 'restrict-shlib-link-flags-to-enable-exports' into next

b15f4e9b try_compile: Propogate CMP0065 to the generated project.
9784af1b CMP0065: Restrict the use of CMAKE_SHARED_LIBRARY_LINK__FLAGS


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b15f4e9b86bc3dc31b6a01c0ffc30747f467ec1f
commit b15f4e9b86bc3dc31b6a01c0ffc30747f467ec1f
Author: Chuck Atkins 
AuthorDate: Mon Aug 24 22:56:31 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 10:12:13 2015 -0400

try_compile: Propogate CMP0065 to the generated project.

Set policy CMP0065 to the value used in the calling project.

Set the the value of CMAKE_ENABLE_EXPORTS if set in the calling
project to initialize the target property appropriately.

diff --git a/Help/command/try_compile.rst b/Help/command/try_compile.rst
index 1ed24df..28dae80 100644
--- a/Help/command/try_compile.rst
+++ b/Help/command/try_compile.rst
@@ -100,6 +100,7 @@ If set, the following variables are passed in to the 
generated
 try_compile CMakeLists.txt to initialize compile target properties with
 default values:
 
+* :variable:`CMAKE_ENABLE_EXPORTS`
 * :variable:`CMAKE_LINK_SEARCH_START_STATIC`
 * :variable:`CMAKE_LINK_SEARCH_END_STATIC`
 * :variable:`CMAKE_POSITION_INDEPENDENT_CODE`
@@ -107,5 +108,7 @@ default values:
 If :policy:`CMP0056` is set to ``NEW``, then
 :variable:`CMAKE_EXE_LINKER_FLAGS` is passed in as well.
 
+The current setting of :policy:`CMP0065` is set in the generated project.
+
 Set the :variable:`CMAKE_TRY_COMPILE_CONFIGURATION` variable to choose
 a build configuration.
diff --git a/Source/cmCoreTryCompile.cxx b/Source/cmCoreTryCompile.cxx
index 9411555..e489ad2 100644
--- a/Source/cmCoreTryCompile.cxx
+++ b/Source/cmCoreTryCompile.cxx
@@ -481,6 +481,16 @@ int 
cmCoreTryCompile::TryCompileCode(std::vector const& argv)
   fprintf(fout, "set(CMAKE_LINK_SEARCH_END_STATIC \"%s\")\n", lssDef);
   }
 
+/* Set the appropriate policy information for ENABLE_EXPORTS */
+fprintf(fout, "cmake_policy(SET CMP0065 %s)\n",
+   this->Makefile->GetPolicyStatus(cmPolicies::CMP0065) ==
+ cmPolicies::NEW ? "NEW" : "OLD");
+if(const char *ee = this->Makefile->GetDefinition(
+"CMAKE_ENABLE_EXPORTS"))
+  {
+  fprintf(fout, "set(CMAKE_ENABLE_EXPORTS %s)\n", ee);
+  }
+
 /* Put the executable at a known location (for COPY_FILE).  */
 fprintf(fout, "set(CMAKE_RUNTIME_OUTPUT_DIRECTORY \"%s\")\n",
 this->BinaryDirectory.c_str());

http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9784af1b50a142c0160058734c7e12cee5f2a15e
commit 9784af1b50a142c0160058734c7e12cee5f2a15e
Author: Chuck Atkins 
AuthorDate: Mon Aug 24 14:33:31 2015 -0400
Commit: Brad King 
CommitDate: Mon Sep 21 10:12:13 2015 -0400

CMP0065: Restrict the use of CMAKE_SHARED_LIBRARY_LINK__FLAGS

This new policy restricts the addition of the shared library link flags
to executables only when the ENABLE_EXPORTS property is set to True.

diff --git a/Help/manual/cmake-policies.7.rst b/Help/manual/cmake-policies.7.rst
index 590f10d..ae5354f 100644
--- a/Help/manual/cmake-policies.7.rst
+++ b/Help/manual/cmake-policies.7.rst
@@ -122,3 +122,4 @@ All Policies
/policy/CMP0062
/policy/CMP0063
/policy/CMP0064
+   /policy/CMP0065
diff --git a/Help/manual/cmake-variables.7.rst 
b/Help/manual/cmake-variables.7.rst
index 660d544..e679962 100644
--- a/Help/manual/cmake-variables.7.rst
+++ b/Help/manual/cmake-variables.7.rst
@@ -245,6 +245,7 @@ Variables that Control the Build
/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG
/variable/CMAKE_CONFIG_POSTFIX
/variable/CMAKE_DEBUG_POSTFIX
+   /variable/CMAKE_ENABLE_EXPORTS
/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG
/variable/CMAKE_EXE_LINKER_FLAGS
/variable/CMAKE_Fortran_FORMAT
diff --git 

Re: [cmake-developers] [PATCH] [CMake 0015674]: Windows: Correctly determine Windows version

2015-09-21 Thread Brad King
On 09/18/2015 02:24 PM, Brad King wrote:
> After working out the support for manifests across all generators
> as discussed elsewhere in this thread, I've added your manifest
> file to CMake's own build:
> 
>  Windows: Fix CMAKE_HOST_SYSTEM_VERSION on Windows >= 8 (#15674)
>  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=cdd15551

That broke the build of cmake-gui due to an incorrect relative path
to the manifest file.  I've revised the commit accordingly:

 Windows: Fix CMAKE_HOST_SYSTEM_VERSION on Windows >= 8 (#15674)
 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=17009189

-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


Re: [cmake-developers] generator expression for path slash conversion

2015-09-21 Thread Kislinskiy, Stefan
I wrote the documentation and extended the GeneratorExpression tests for the 
SHELL_PATH genex. It works fine for WIN32 and UNIX. However, I'm having some 
trouble to test for MSYS. The check looks like:

if(MSYS)
  check(test_shell_path "/c/shell/path")
elseif(WIN32)
  check(test_shell_path "c:shellpath")
elseif(UNIX)
  check(test_shell_path "c:/shell/path")
endif()

No matter what I'm doing, it always ends up in the WIN32 branch with FORWARD 
slashes. Additionally the drive letter is NOT converted to a posix path as it 
should be the case for MSYS. I tried MSYS from the official MinGW package, and 
I tried the MSYS2 installer. In both cases I called cmake from MinGW-sh, 
MSYS-sh, and even cmd.exe. I used the "MSYS Makefiles" Generator. In addition I 
tried the "MinGW Makefiles" generator just to check if "if(MINGW)" is 
working... which also fails. The configuring/generating itself is working.. Any 
ideas?

Stefan

-Original Message-
From: Brad King [mailto:brad.k...@kitware.com] 
Sent: Donnerstag, 17. September 2015 15:56
To: Kislinskiy, Stefan
Cc: CHEVRIER, Marc; cmake-developers@cmake.org; James Johnston
Subject: Re: [cmake-developers] generator expression for path slash conversion

On 09/17/2015 09:51 AM, Kislinskiy, Stefan wrote:
> I wrote a SHELL_PATH genex which uses
> cmOutputConverter->ConvertToOutputFormat(..., SHELL) for the conversion.
> I decided to name the genex SHELL_PATH instead of TO_SHELL_PATH for 
> the sake of consistency to other genexes like LOWER_CASE. What do you think?

LGTM.

> I would write some documentation as well of course.

Yes, please.  Also please look at extending the test suite to cover it.
See Tests/GeneratorExpression for genex unit test examples.  If possible we 
should also have a case that uses it in practice in a way that fails on 
invocation of an actual native tool if the slashes are wrong.  That will 
confirm not only that the genex does what we expect but that it also solves the 
problem we're trying to solve.

Thanks,
-Brad



shell_path_genex_v2.patch
Description: shell_path_genex_v2.patch
-- 

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] generator expression for path slash conversion

2015-09-21 Thread Brad King
On 09/21/2015 10:05 AM, Kislinskiy, Stefan wrote:
> if(MSYS)
>   check(test_shell_path "/c/shell/path")
> elseif(WIN32)
>   check(test_shell_path "c:shellpath")
> elseif(UNIX)
>   check(test_shell_path "c:/shell/path")
> endif()
> 
> No matter what I'm doing, it always ends up in the WIN32 branch
> with FORWARD slashes. Additionally the drive letter is NOT converted to a 
> posix path as it should be the case for MSYS. I tried MSYS from the official 
> MinGW package, and I tried the MSYS2 installer. In both cases I called cmake 
> from MinGW-sh, MSYS-sh, and even cmd.exe. I used the "MSYS Makefiles" 
> Generator. In addition I tried the "MinGW Makefiles" generator just to check 
> if "if(MINGW)" is working... which also fails. The configuring/generating 
> itself is working.. Any ideas?

The code in the check-part4.cmake script runs in a cmake script
(via "cmake -P").  That does not have any information about the
configuration of the project, generator used, or target platform.
If you need this information it needs to be passed in through
additional "-Dvar=val" arguments prior to the -P argument.

-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


Re: [cmake-developers] [PATCH] [CMake 0015674]: Windows: Correctly determine Windows version

2015-09-21 Thread Brad King
On 09/18/2015 02:58 PM, James Johnston wrote:
> While on the subject, there are some other additions to the manifest you
> might want to consider.

I think these are worth considering but we're too close to the 3.4 freeze
to make these changes now.  Please look at adding these during post-3.4
development.

Thanks,
-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-developers] [CMake 0015754]: Visual Studio incremental build not working properly when target names start with a capital letter

2015-09-21 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=15754 
== 
Reported By:Johannes Asal
Assigned To:
== 
Project:CMake
Issue ID:   15754
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2015-09-21 10:54 EDT
Last Modified:  2015-09-21 10:54 EDT
== 
Summary:Visual Studio incremental build not working properly
when target names start with a capital letter
Description: 
When using a target name starting with a capital letter (e.g. Mylibrary) in
add_library (and probably also add_executable), GCC toolchains build fine but
Visual Studio (tested with 2010 specifically) refuses to compile new .cpp files
in the first incremental build after adding them to the CMakeLists.txt. However,
it correctly detects that the CMakeLists.txt has changed and reconfigures
accordingly. The second incremental build compiles the added files, which makes
it even more strange. Please note that the bug occurs only when building via the
CMake command line interface (cmake.exe --build). Building from within Visual
Studio works always which is why I think it must be a problem with CMake.

Steps to Reproduce: 
Install Visual Studio 2010. Unzip the attached ZIP file. Open a command line in
the /build subfolder and call

cmake -G"Visual Studio 10" ..

Then do a

cmake --build .

Watch how test1.cpp is compiled properly. Then open CMakeLists.txt and uncomment
the line with test2.cpp. Do an incremental build by calling

cmake --build .

The change of CMakeLists.txt is detected but test2.cpp is NOT COMPILED! Do a
second incremental build

cmake --build .

Now test2.cpp is compiled.

Delete the bugreport folder and extract it again from the ZIP file to return to
the initial state. Open the CMakeLists.txt and rename the 'Notworking' target
name in add_library to 'working'. Repeat all steps above and you will see that
test2.cpp is compiled in the first incremental build already, as one would
expect.

I tested a lot of combinations and it seems that the capital letter in front
seems to be the source of the problem.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-09-21 10:54 Johannes Asal  New Issue
2015-09-21 10:54 Johannes Asal  File Added: bugreport.zip
==

-- 

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-commits] CMake branch, next, updated. v3.3.2-3176-g6930abc

2015-09-21 Thread Rolf Eike Beer
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  6930abc0d88ae587a717b9343780ac32499da4c1 (commit)
   via  80963782a3726472dacfc82f357d5ceccca3b543 (commit)
  from  8db1b40ef504bc2ac102877bc767d608891d16f4 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6930abc0d88ae587a717b9343780ac32499da4c1
commit 6930abc0d88ae587a717b9343780ac32499da4c1
Merge: 8db1b40 8096378
Author: Rolf Eike Beer 
AuthorDate: Mon Sep 21 14:32:59 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 14:32:59 2015 -0400

Merge topic 'Threads-CXX' into next

80963782 FindThreads: add simple testcase


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=80963782a3726472dacfc82f357d5ceccca3b543
commit 80963782a3726472dacfc82f357d5ceccca3b543
Author: Rolf Eike Beer 
AuthorDate: Mon Sep 21 17:57:33 2015 +0200
Commit: Rolf Eike Beer 
CommitDate: Mon Sep 21 20:32:47 2015 +0200

FindThreads: add simple testcase

diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt
index fff04ce..dc65a2e 100644
--- a/Tests/CMakeLists.txt
+++ b/Tests/CMakeLists.txt
@@ -1365,6 +1365,8 @@ ${CMake_BINARY_DIR}/bin/cmake -DDIR=dev -P 
${CMake_SOURCE_DIR}/Utilities/Release
 add_subdirectory(FindOpenSSL)
   endif()
 
+  add_subdirectory(FindThreads)
+
   # Matlab module
   if(CMake_TEST_FindMatlab)
 ADD_TEST_MACRO(FindMatlab.basic_checks  ${CMAKE_CTEST_COMMAND} -C 
$)
diff --git a/Tests/FindThreads/C-only/CMakeLists.txt 
b/Tests/FindThreads/C-only/CMakeLists.txt
new file mode 100644
index 000..ffbb8b1
--- /dev/null
+++ b/Tests/FindThreads/C-only/CMakeLists.txt
@@ -0,0 +1,8 @@
+cmake_minimum_required(VERSION 3.3 FATAL_ERROR)
+project(FindThreads_C-only C)
+
+set(CMAKE_THREAD_PREFER_PTHREAD On)
+find_package(Threads REQUIRED)
+
+add_executable(thr 
${CMAKE_CURRENT_SOURCE_DIR}/../../../Modules/CheckForPthreads.c)
+target_link_libraries(thr Threads::Threads)
diff --git a/Tests/FindThreads/CMakeLists.txt b/Tests/FindThreads/CMakeLists.txt
new file mode 100644
index 000..36518a3
--- /dev/null
+++ b/Tests/FindThreads/CMakeLists.txt
@@ -0,0 +1,9 @@
+add_test(NAME FindThreads.C-only COMMAND ${CMAKE_CTEST_COMMAND}
+  --build-and-test
+  "${CMake_SOURCE_DIR}/Tests/FindThreads/C-only"
+  "${CMake_BINARY_DIR}/Tests/FindThreads/C-only"
+  ${build_generator_args}
+  --build-project FindThreads_C-only
+  --build-options ${build_options}
+  --test-command ${CMAKE_CTEST_COMMAND} -V
+  )

---

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, next, updated. v3.3.2-3174-g8db1b40

2015-09-21 Thread Rolf Eike Beer
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  8db1b40ef504bc2ac102877bc767d608891d16f4 (commit)
   via  6f9516c587aad56212b06f64a35c7037acec84e2 (commit)
  from  da378b6182c89d31d97524efd086fcb119ef0572 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8db1b40ef504bc2ac102877bc767d608891d16f4
commit 8db1b40ef504bc2ac102877bc767d608891d16f4
Merge: da378b6 6f9516c
Author: Rolf Eike Beer 
AuthorDate: Mon Sep 21 14:32:38 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 14:32:38 2015 -0400

Merge topic 'Threads-CXX' into next

6f9516c5 fixup FindThreads test


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6f9516c587aad56212b06f64a35c7037acec84e2
commit 6f9516c587aad56212b06f64a35c7037acec84e2
Author: Rolf Eike Beer 
AuthorDate: Mon Sep 21 20:32:04 2015 +0200
Commit: Rolf Eike Beer 
CommitDate: Mon Sep 21 20:32:29 2015 +0200

fixup FindThreads test

diff --git a/Tests/FindThreads/C-only/CMakeLists.txt 
b/Tests/FindThreads/C-only/CMakeLists.txt
index c366b79..ffbb8b1 100644
--- a/Tests/FindThreads/C-only/CMakeLists.txt
+++ b/Tests/FindThreads/C-only/CMakeLists.txt
@@ -1,5 +1,5 @@
 cmake_minimum_required(VERSION 3.3 FATAL_ERROR)
-project(FindThreads C)
+project(FindThreads_C-only C)
 
 set(CMAKE_THREAD_PREFER_PTHREAD On)
 find_package(Threads REQUIRED)

---

Summary of changes:
 Tests/FindThreads/C-only/CMakeLists.txt |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.3.2-3178-g6685dcd

2015-09-21 Thread Rolf Eike Beer
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  6685dcd54221f56e1047142fd728000c9484101a (commit)
   via  5ba56a89c82689102294b412784d9c938cf7f472 (commit)
  from  6930abc0d88ae587a717b9343780ac32499da4c1 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6685dcd54221f56e1047142fd728000c9484101a
commit 6685dcd54221f56e1047142fd728000c9484101a
Merge: 6930abc 5ba56a8
Author: Rolf Eike Beer 
AuthorDate: Mon Sep 21 15:17:24 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 15:17:24 2015 -0400

Merge topic 'Threads-CXX' into next

5ba56a89 fixup Threads test


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5ba56a89c82689102294b412784d9c938cf7f472
commit 5ba56a89c82689102294b412784d9c938cf7f472
Author: Rolf Eike Beer 
AuthorDate: Mon Sep 21 21:17:14 2015 +0200
Commit: Rolf Eike Beer 
CommitDate: Mon Sep 21 21:17:14 2015 +0200

fixup Threads test

diff --git a/Tests/FindThreads/C-only/CMakeLists.txt 
b/Tests/FindThreads/C-only/CMakeLists.txt
index ffbb8b1..ab4ca0d 100644
--- a/Tests/FindThreads/C-only/CMakeLists.txt
+++ b/Tests/FindThreads/C-only/CMakeLists.txt
@@ -4,5 +4,7 @@ project(FindThreads_C-only C)
 set(CMAKE_THREAD_PREFER_PTHREAD On)
 find_package(Threads REQUIRED)
 
-add_executable(thr 
${CMAKE_CURRENT_SOURCE_DIR}/../../../Modules/CheckForPthreads.c)
-target_link_libraries(thr Threads::Threads)
+if (NOT WIN32)
+  add_executable(thr 
${CMAKE_CURRENT_SOURCE_DIR}/../../../Modules/CheckForPthreads.c)
+  target_link_libraries(thr Threads::Threads)
+endif ()

---

Summary of changes:
 Tests/FindThreads/C-only/CMakeLists.txt |6 --
 1 file changed, 4 insertions(+), 2 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.3.2-3180-g6d9d704

2015-09-21 Thread Rolf Eike Beer
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  6d9d7045893e99bc713958ec93f30fcf62555b6f (commit)
   via  7279f2939e98ae9ecfb8fda2dc82f6b0048b9316 (commit)
  from  6685dcd54221f56e1047142fd728000c9484101a (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6d9d7045893e99bc713958ec93f30fcf62555b6f
commit 6d9d7045893e99bc713958ec93f30fcf62555b6f
Merge: 6685dcd 7279f29
Author: Rolf Eike Beer 
AuthorDate: Mon Sep 21 15:17:52 2015 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Sep 21 15:17:52 2015 -0400

Merge topic 'Threads-CXX' into next

7279f293 FindThreads: add simple testcase


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7279f2939e98ae9ecfb8fda2dc82f6b0048b9316
commit 7279f2939e98ae9ecfb8fda2dc82f6b0048b9316
Author: Rolf Eike Beer 
AuthorDate: Mon Sep 21 17:57:33 2015 +0200
Commit: Rolf Eike Beer 
CommitDate: Mon Sep 21 21:17:32 2015 +0200

FindThreads: add simple testcase

diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt
index fff04ce..dc65a2e 100644
--- a/Tests/CMakeLists.txt
+++ b/Tests/CMakeLists.txt
@@ -1365,6 +1365,8 @@ ${CMake_BINARY_DIR}/bin/cmake -DDIR=dev -P 
${CMake_SOURCE_DIR}/Utilities/Release
 add_subdirectory(FindOpenSSL)
   endif()
 
+  add_subdirectory(FindThreads)
+
   # Matlab module
   if(CMake_TEST_FindMatlab)
 ADD_TEST_MACRO(FindMatlab.basic_checks  ${CMAKE_CTEST_COMMAND} -C 
$)
diff --git a/Tests/FindThreads/C-only/CMakeLists.txt 
b/Tests/FindThreads/C-only/CMakeLists.txt
new file mode 100644
index 000..ab4ca0d
--- /dev/null
+++ b/Tests/FindThreads/C-only/CMakeLists.txt
@@ -0,0 +1,10 @@
+cmake_minimum_required(VERSION 3.3 FATAL_ERROR)
+project(FindThreads_C-only C)
+
+set(CMAKE_THREAD_PREFER_PTHREAD On)
+find_package(Threads REQUIRED)
+
+if (NOT WIN32)
+  add_executable(thr 
${CMAKE_CURRENT_SOURCE_DIR}/../../../Modules/CheckForPthreads.c)
+  target_link_libraries(thr Threads::Threads)
+endif ()
diff --git a/Tests/FindThreads/CMakeLists.txt b/Tests/FindThreads/CMakeLists.txt
new file mode 100644
index 000..36518a3
--- /dev/null
+++ b/Tests/FindThreads/CMakeLists.txt
@@ -0,0 +1,9 @@
+add_test(NAME FindThreads.C-only COMMAND ${CMAKE_CTEST_COMMAND}
+  --build-and-test
+  "${CMake_SOURCE_DIR}/Tests/FindThreads/C-only"
+  "${CMake_BINARY_DIR}/Tests/FindThreads/C-only"
+  ${build_generator_args}
+  --build-project FindThreads_C-only
+  --build-options ${build_options}
+  --test-command ${CMAKE_CTEST_COMMAND} -V
+  )

---

Summary of changes:


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


[cmake-developers] [CMake 0015756]: FindLua.cmake doesn't work when both Lua5.2 and Lua5.3 are installed.

2015-09-21 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=15756 
== 
Reported By:Alan Witkowski
Assigned To:
== 
Project:CMake
Issue ID:   15756
Category:   Modules
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2015-09-21 15:15 MDT
Last Modified:  2015-09-21 15:15 MDT
== 
Summary:FindLua.cmake doesn't work when both Lua5.2 and
Lua5.3 are installed.
Description: 
If you call find_package(Lua 5.2 REQUIRED) or find_package(Lua REQUIRED) this
happens:

Found Lua: /usr/lib64/liblua5.2.so;/usr/lib64/libm.so (found suitable version
"5.3.1", minimum required is "5.2")

Basically the 5.2 library is found but it still uses the 5.3 include path, hence
the wrong "suitable version":

CMakeCache.txt
LUA_INCLUDE_DIR:PATH=/usr/include
LUA_LIBRARY:FILEPATH=/usr/lib64/liblua5.2.so

Calling find_package(Lua 5.3 REQUIRED) works fine though.

Additional Information: 
lua5.3 is installed to /usr/include
lua5.2 is installed to /usr/include/lua5.2
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-09-21 15:15 Alan Witkowski New Issue
==

-- 

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] Add command line options for deprecation message control

2015-09-21 Thread Michael Scott

The -Wdev/-Wno-dev options have always been for all messages
output by any part of CMake.  This needs to be preserved/corrected.
Okay, I've fixed the change to cmake::PrintMessagePreamble, so that 
it'll stop warning or error dev or deprecated messages getting printed 
out when the relevant CMake variables have been set. I just need to add 
some more test cases to cover this and I'll submit a patch.



Likely yes.  This may require sweeping changes to address.  We're
too close to the freeze for 3.4 to do this now.  Perhaps we should
simply remove -Werr-dev for now.


Yes the -Werr-dev, -Wno-err-dev, -Werr-deprectated and 
-Wno-err-deprecated may be trickier than expected to get behaving as 
intended. I'll try and get a better idea of the users of IssueMessage 
and see if some ideas come to mind. Removing them would be fair enough 
at this point, better to not include them than to include broken 
functionality I'm sure. Do new features, such as -Werr-dev, have to be 
sent by October 1st is it?


Cheers,
Michael

--

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] CPack/NSIS is broken after extended length paths fix

2015-09-21 Thread Dmitry Kochkin
 Hi Clint,

>>Actually it's even worse because in current master HEAD I can see that 
>>INST_DIR is empty in generated project:
>>  !define INST_DIR ""
>>(not sure if that's caused by your change)
>Interesting... Do you know why this happens?  How is this problem related to 
>extended paths (with the \\?\ prefix)?  Do you have an example to demonstrate 
>this problem? That was my mistake, please ignore.
>>I've figured out that NSIS was not going to fix this (see  
>>http://sourceforge.net/p/nsis/feature-requests/241/ )
>
>Maybe they'll accept a patch to fix it there?  Was there any effort to fix it 
>there?
In the URL I've put they claim you should just use "\\?\" in your NSIS project.
I guess it's also possible to fix NSIS, but we cannot rely that user have 
latest NSIS.

>
>>
>>I've made a small patch to NSIS generator and template to put infamous \\?\ 
>>there.
>>
>>I can send directly to you as I guess you know more about these parts of code.
>
>You can send your patch to this mailing list for review.
Patch attached. It's a bit hacky, more fixing symptoms I guess. The purpose is 
only to demonstrate the idea.
Let me know if it can be done in better way.

Regards,
Dmitry


From a14fc375593f2d150dba8f93d34f04b954c9365e Mon Sep 17 00:00:00 2001
From: Dmitry Kochkin 
Date: Mon, 21 Sep 2015 11:23:19 +0200
Subject: [PATCH] Fixing NSIS packer for very long filenames on Windows

---
 Modules/NSIS.template.in  |  4 ++--
 Source/CPack/cmCPackNSISGenerator.cxx | 10 --
 2 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/Modules/NSIS.template.in b/Modules/NSIS.template.in
index 76310af..0fe19fe 100644
--- a/Modules/NSIS.template.in
+++ b/Modules/NSIS.template.in
@@ -5,7 +5,7 @@
 
   !define VERSION "@CPACK_PACKAGE_VERSION@"
   !define PATCH  "@CPACK_PACKAGE_VERSION_PATCH@"
-  !define INST_DIR "@CPACK_TEMPORARY_DIRECTORY@"
+  !define INST_DIR "@CPACK_TEMPORARY_DIRECTORY_SAFE@"
 
 ;
 ;Variables
@@ -639,7 +639,7 @@ FunctionEnd
 Section "-Core installation"
   ;Use the entire tree produced by the INSTALL target.  Keep the
   ;list of directories here in sync with the RMDir commands below.
-  SetOutPath "$INSTDIR"
+  SetOutPath "\\?\$INSTDIR"
   @CPACK_NSIS_EXTRA_PREINSTALL_COMMANDS@
   @CPACK_NSIS_FULL_INSTALL@
 
diff --git a/Source/CPack/cmCPackNSISGenerator.cxx b/Source/CPack/cmCPackNSISGenerator.cxx
index 6cdda28..6676d3a 100644
--- a/Source/CPack/cmCPackNSISGenerator.cxx
+++ b/Source/CPack/cmCPackNSISGenerator.cxx
@@ -46,6 +46,12 @@ cmCPackNSISGenerator::~cmCPackNSISGenerator()
 //--
 int cmCPackNSISGenerator::PackageFiles()
 {
+  std::string win_safe_tmp( this->GetOption( "CPACK_TEMPORARY_DIRECTORY" ) );
+#ifdef _WIN32
+  cmSystemTools::ReplaceString(win_safe_tmp, "/", "\\");
+  win_safe_tmp = "?\\" + win_safe_tmp;
+#endif
+  this->SetOptionIfNotSet( "CPACK_TEMPORARY_DIRECTORY_SAFE", win_safe_tmp.c_str( ) );
   // TODO: Fix nsis to force out file name
 
   std::string nsisInFileName = this->FindTemplate("NSIS.template.in");
@@ -83,7 +89,7 @@ int cmCPackNSISGenerator::PackageFiles()
   fileN = fileN.substr(fileN.find('/')+1, std::string::npos);
   }
 cmSystemTools::ReplaceString(fileN, "/", "\\");
-str << "  Delete \"$INSTDIR\\" << fileN << "\"" << std::endl;
+str << "  Delete \"?\\$INSTDIR\\" << fileN << "\"" << std::endl;
 }
   cmCPackLogger(cmCPackLog::LOG_DEBUG, "Uninstall Files: "
 << str.str() << std::endl);
@@ -117,7 +123,7 @@ int cmCPackNSISGenerator::PackageFiles()
 }
   }
 cmSystemTools::ReplaceString(fileN, "/", "\\");
-dstr << "  RMDir \"$INSTDIR\\" << fileN << "\"" << std::endl;
+dstr << "  RMDir \"?\\$INSTDIR\\" << fileN << "\"" << std::endl;
 if (!componentName.empty())
   {
   this->Components[componentName].Directories.push_back(fileN);
-- 
2.5.1.windows.1

-- 

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