date:20160401

[CMake] Parsing command line arguments from the make

2016-04-01 Thread Fedja Jeleskovic

Since I am converting existing makefile project to use cmake instead I need
to accept values that come from command line which looks like this:
VARIABLE_NAME="/home/user/project" make ENV=VERSION_2

First one is used like this:
include $(VARIABLE_NAME)/Makefile.include

Second one has this code that triggers different paths later:
ifneq ($(ENV),)
DEPLOYMENT_VERSION=$(ENV)
endif

How do I do this in cmake?

Thanks!
-- 

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] Creating a list of link directories from a variable

2016-04-01 Thread Salazar De Troya, Miguel

Hello

Thanks for your response. Is there automatic way to know which libraries my 
executable will need and which ones it won’t? Why is this the case for only 
shared libraries? Is it because the linking symbols are already in that shared 
library and I don’t need to link them again if I’m not using them directly?

Miguel
From: Hendrik Sattler >
Date: Thursday, March 31, 2016 at 10:27 PM
To: Miguel Salazar >, 
"cmake@cmake.org" 
>
Subject: Re: [CMake] Creating a list of link directories from a variable

Hi,

If the library is a shared object, try to NOT use all those libraries. If they 
are used in the library but are not part of its public API, you most likely 
don't need to link them. If you have no missing symbols when linking, you can 
avoid overlinking you program.

If this is a static library, you have a lot more work. For each library without 
-l, use find_library() and use the library dirs as hints. Do NOT use 
link_directories().

HS

Am 1. April 2016 00:22:09 MESZ, schrieb "Salazar De Troya, Miguel" 
>:
Hello

I am trying to compile a program with a library that provides a bash script to 
generate the dependencies, libraries and the link directories for the Makefile. 
I want to generate a CMakeLists.txt that can handle these dependencies from 
that library. I have been able to come up with regexp that can extract the 
information and put it into a variable with the dirs or library names separated 
by comma, for instance:

INCLUDE_DIRS =

/g/g92/miguel/code/libmesh_2D/include;/usr/include/curl;/usr/include/glpk;/usr/local/tools/vtk-6.1.0/include/vtk-6.1;/g/g92/miguel/petsc-3.6.2/include;/g/g92/miguel/petsc-3.6.2/miguel-opt/include;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi/opal/mca/hwloc/hwloc191/hwloc/include;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent/include;/usr/local/tools/openmpi-intel-1.8.4/include;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi;/usr/local/tools/boost-mpi-1.55.0//include

LIBS =

-lcurl;-lhdf5;-lglpk;-lvtkIOCore-6.1;-lvtkCommonCore-6.1;-lvtkCommonDataModel-6.1;-lvtkFiltersCore-6.1;-lvtkIOXML-6.1;-lvtkImagingCore-6.1;-lvtkIOImage-6.1;-lvtkImagingMath-6.1;-lz;-lpetsc;-lcmumps;-ldmumps;-lsmumps;-lzmumps;-lmumps_common;-lpord;-lscalapack;-lHYPRE;-lml;-llapack;-lblas;-lparmetis;-lmetis;-lX11;-lhwloc;-lssl;-lcrypto;-lmpi_usempif08;-lmpi_usempi_ignore_tkr;-lmpi_mpifh;-lifport;-lifcore;-lm;-lmpi;-limf;-lsvml;-lirng;-lipgo;-ldecimal;-lcilkrts;-lstdc++;-lgcc_s;-lirc;-lpthread;-lirc_s;-ldl;-lmesh_opt

LIB_DIRS =

/usr/lib;/lib;/usr/lib64;/usr/local/tools/vtk-6.1.0/lib;/g/g92/miguel/petsc-3.6.2/miguel-opt/lib;/usr/local/tools/openmpi-intel-1.8.4/lib;/usr/local/tools/ic-14.0.174/composer_xe_2013_sp1.3.174/compiler/lib/intel64;/usr/lib/gcc/x86_64-redhat-linux/4.4.7;/g/g92/miguel/code/libmesh_2D/lib

These are variables in my environment that I use in CMake with $ENV{VAR}. How 
can I use this information for the commands:

include_directories($ENV{INCLUDE_DIRS})

link_directories($ENV{LIB_DIRS})

target_link_libraries($ENV{LIBS}) ?

It seems that cmake can digest the include directories and the 
target_link_libraries (because they appear correctly in the compilation), but 
not the link_directories. Why? Also, I’ve read that it is more correct to use 
find_library() instead. How would I iterate over the LIBS? Can I use a single 
LIB_DIRS (with all the information above) in the PATHS argument of 
find_library()

Thanks

Miguel

--

Powered by 
http://secure-web.cisco.com/1SkTeDpqcSTqs7V0Q2yjUdQEsQ1huaYLleRl_DSB40mZrJmSB4Lr6utBlMnP2n8teBgjMf-JqbxyEzxRwI33xdCPfZ4V-R2DL7hRPikFqd9-Rs0WFTInnFgBOVb385LKZzSj7s6rnXOZg-2XG27MJ2-q9sNDHuOdRClebWLFsHqVgj0HGuWMrWGh1kE2S9-TyKuTes7ceD6P0h7C_OsCM_EQXdmhkDGCqyKLK6MRTupY6_HJ1roZBy2Y98SiMF_6LXWUyvKR_raD6crErzRofBLqtBN4vsNeqHBC88J3gYM2BgpkiDnNxonEQy0GonMqIPBKPG9ORW1sEj7-QXajnhYY6cXvu-1TI6aW8FSgTSzZxgdA9zvzoea-DB1

ANk22B/http%3A%2F%2Fwww.kitware.com

Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] Building a tool immediately so it can be used later in same CMake run

2016-04-01 Thread Scott Aron Bloom

I had asked a similar question 2 weeks or so ago.  The conclusion, which DID 
work well was the following.

Rather than having 1 “large” cmake project with sub libraries.

Use the “super-project” system, where you do an ExternalProject_Add for each of 
the projects.  Then for the projects that need the “first executable” you list 
that project as a dependency

Scott

From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Craig Scott
Sent: Thursday, March 31, 2016 4:53 PM
To: cmake@cmake.org
Subject: [CMake] Building a tool immediately so it can be used later in same 
CMake run

All,

I originally planned to ask this question directly on this mailing list, but it 
got a bit more involved, so I posted it to stackoverflow instead. I'm 
interested if anyone can shed some more authoritative light on the proposed 
method for the following question:

http://stackoverflow.com/q/36084785/1938798

Short version: invoke a nested cmake-and-build immediately within the main 
CMake run to build a specific target via execute_process(). This makes that 
tool available for use still within the same (main) CMake run. An 
ExternalProject-based technique would normally be a better solution, but in 
this particular case, that wasn't possible.

I'd be interested if anyone can confirm whether the suggested approach is 
guaranteed to be safe for all generators and platforms, or whether there are 
other factors I have not considered in the proposed technique.

Cheers

--
Craig Scott
Melbourne, Australia
http://crascit.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] Creating a list of link directories from a variable

2016-04-01 Thread Salazar De Troya, Miguel

The library that I am using uses libtool for this purpose I think. This is what 
the Makefile to build the application looks like:

$(notdir $(target)): $(objects)
@echo "Linking "$@"..."
@$(libmesh_LIBTOOL) --tag=CXX $(LIBTOOLFLAGS) --mode=link \
$(libmesh_CXX) $(libmesh_CXXFLAGS) $(objects) -o $@ $(libmesh_LIBS) 
$(libmesh_LDFLAGS) $(EXTERNAL_FLAGS)

where $(libmesh_LIBTOOL) is the libtool executable, $(libmesh_CXX) is the 
compiler, etc. $(libmesh_LIBS) is the same I described before, I.e., all the 
libraries the library I am using uses.  Is there anyway I can use libtool 
within cmake?

Thanks
Miguel
From: Hendrik Sattler >
Date: Friday, April 1, 2016 at 10:02 AM
To: Miguel Salazar >, 
"cmake@cmake.org" 
>
Subject: Re: [CMake] Creating a list of link directories from a variable

Hi,

yes, exactly. The easiest way to find out is to simply try it. The linker will 
tell you if some symbols need to be resolved. Static libraries are not linked 
but only compiled, so the application or library that links to such a static 
library must do this step.

If that library you use would use some established method like pkg-config to 
expose those values, it would be much easier (if used correctly by the library 
author). It can differentiate between those cases.

HS


Am 1. April 2016 18:25:46 MESZ, schrieb "Salazar De Troya, Miguel" 
>:
Hello

Thanks for your response. Is there automatic way to know which libraries my 
executable will need and which ones it won’t? Why is this the case for only 
shared libraries? Is it because the linking symbols are already in that shared 
library and I don’t need to link them again if I’m not using them directly?

Miguel
From: Hendrik Sattler >
Date: Thursday, March 31, 2016 at 10:27 PM
To: Miguel Salazar >, 
"cmake@cmake.org" 
>
Subject: Re: [CMake] Creating a list of link directories from a variable

Hi,

If the library is a shared object, try to NOT use all those libraries. If they 
are used in the library but are not part of its public API, you most likely 
don't need to link them. If you have no missing symbols when linking, you can 
avoid overlinking you program.

If this is a static library, you have a lot more work. For each library without 
-l, use find_library() and use the library dirs as hints. Do NOT use 
link_directories().

HS




Am 1. April 2016 00:22:09 MESZ, schrieb "Salazar De Troya, Miguel" 
>:
Hello

I am trying to compile a program with a library that provides a bash script to 
generate the dependencies, libraries and the link directories for the Makefile. 
I want to generate a CMakeLists.txt that can handle these dependencies from 
that library. I have been able to come up with regexp that can extract the 
information and put it into a variable with the dirs or library names separated 
by comma, for instance:

INCLUDE_DIRS =

/g/g92/miguel/code/libmesh_2D/include;/usr/include/curl;/usr/include/glpk;/usr/local/tools/vtk-6.1.0/include/vtk-6.1;/g/g92/miguel/petsc-3.6.2/include;/g/g92/miguel/petsc-3.6.2/miguel-opt/include;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi/opal/mca/hwloc/hwloc191/hwloc/include;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent/include;/usr/local/tools/openmpi-intel-1.8.4/include;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi;/usr/local/tools/boost-mpi-1.55.0//include


LIBS =

-lcurl;-lhdf5;-lglpk;-lvtkIOCore-6.1;-lvtkCommonCore-6.1;-lvtkCommonDataModel-6.1;-lvtkFiltersCore-6.1;-lvtkIOXML-6.1;-lvtkImagingCore-6.1;-lvtkIOImage-6.1;-lvtkImagingMath-6.1;-lz;-lpetsc;-lcmumps;-ldmumps;-lsmumps;-lzmumps;-lmumps_common;-lpord;-lscalapack;-lHYPRE;-lml;-llapack;-lblas;-lparmetis;-lmetis;-lX11;-lhwloc;-lssl;-lcrypto;-lmpi_usempif08;-lmpi_usempi_ignore_tkr;-lmpi_mpifh;-lifport;-lifcore;-lm;-lmpi;-limf;-lsvml;-lirng;-lipgo;-ldecimal;-lcilkrts;-lstdc++;-lgcc_s;-lirc;-lpthread;-lirc_s;-ldl;-lmesh_opt


LIB_DIRS =

/usr/lib;/lib;/usr/lib64;/usr/local/tools/vtk-6.1.0/lib;/g/g92/miguel/petsc-3.6.2/miguel-opt/lib;/usr/local/tools/openmpi-intel-1.8.4/lib;/usr/local/tools/ic-14.0.174/composer_xe_2013_sp1.3.174/compiler/lib/intel64;/usr/lib/gcc/x86_64-redhat-linux/4.4.7;/g/g92/miguel/code/libmesh_2D/lib


These are variables in my environment that I use in CMake with $ENV{VAR}. How 
can I use this information for the commands:

include_directories($ENV{INCLUDE_DIRS})

link_directories($ENV{LIB_DIRS})

target_link_libraries($ENV{LIBS}) ?


It seems that cmake can

Re: [CMake] Creating a list of link directories from a variable

2016-04-01 Thread Hendrik Sattler

Hi,

yes, exactly. The easiest way to find out is to simply try it. The linker will 
tell you if some symbols need to be resolved. Static libraries are not linked 
but only compiled, so the application or library that links to such a static 
library must do this step.

If that library you use would use some established method like pkg-config  to 
expose those values, it would be much easier (if used correctly by the library 
author). It can differentiate between those cases.

HS


Am 1. April 2016 18:25:46 MESZ, schrieb "Salazar De Troya, Miguel" 
:
>Hello
>
>Thanks for your response. Is there automatic way to know which
>libraries my executable will need and which ones it won’t? Why is this
>the case for only shared libraries? Is it because the linking symbols
>are already in that shared library and I don’t need to link them again
>if I’m not using them directly?
>
>Miguel
>From: Hendrik Sattler
>>
>Date: Thursday, March 31, 2016 at 10:27 PM
>To: Miguel Salazar
>>,
>"cmake@cmake.org"
>>
>Subject: Re: [CMake] Creating a list of link directories from a
>variable
>
>Hi,
>
>If the library is a shared object, try to NOT use all those libraries.
>If they are used in the library but are not part of its public API, you
>most likely don't need to link them. If you have no missing symbols
>when linking, you can avoid overlinking you program.
>
>If this is a static library, you have a lot more work. For each library
>without -l, use find_library() and use the library dirs as hints. Do
>NOT use link_directories().
>
>HS
>
>
>
>
>Am 1. April 2016 00:22:09 MESZ, schrieb "Salazar De Troya, Miguel"
>>:
>Hello
>
>I am trying to compile a program with a library that provides a bash
>script to generate the dependencies, libraries and the link directories
>for the Makefile. I want to generate a CMakeLists.txt that can handle
>these dependencies from that library. I have been able to come up with
>regexp that can extract the information and put it into a variable with
>the dirs or library names separated by comma, for instance:
>
>INCLUDE_DIRS =
>
>/g/g92/miguel/code/libmesh_2D/include;/usr/include/curl;/usr/include/glpk;/usr/local/tools/vtk-6.1.0/include/vtk-6.1;/g/g92/miguel/petsc-3.6.2/include;/g/g92/miguel/petsc-3.6.2/miguel-opt/include;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi/opal/mca/hwloc/hwloc191/hwloc/include;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent/include;/usr/local/tools/openmpi-intel-1.8.4/include;/usr/local/tools/openmpi-intel-1.8.4/include/openmpi;/usr/local/tools/boost-mpi-1.55.0//include
>
>
>LIBS =
>
>-lcurl;-lhdf5;-lglpk;-lvtkIOCore-6.1;-lvtkCommonCore-6.1;-lvtkCommonDataModel-6.1;-lvtkFiltersCore-6.1;-lvtkIOXML-6.1;-lvtkImagingCore-6.1;-lvtkIOImage-6.1;-lvtkImagingMath-6.1;-lz;-lpetsc;-lcmumps;-ldmumps;-lsmumps;-lzmumps;-lmumps_common;-lpord;-lscalapack;-lHYPRE;-lml;-llapack;-lblas;-lparmetis;-lmetis;-lX11;-lhwloc;-lssl;-lcrypto;-lmpi_usempif08;-lmpi_usempi_ignore_tkr;-lmpi_mpifh;-lifport;-lifcore;-lm;-lmpi;-limf;-lsvml;-lirng;-lipgo;-ldecimal;-lcilkrts;-lstdc++;-lgcc_s;-lirc;-lpthread;-lirc_s;-ldl;-lmesh_opt
>
>
>LIB_DIRS =
>
>/usr/lib;/lib;/usr/lib64;/usr/local/tools/vtk-6.1.0/lib;/g/g92/miguel/petsc-3.6.2/miguel-opt/lib;/usr/local/tools/openmpi-intel-1.8.4/lib;/usr/local/tools/ic-14.0.174/composer_xe_2013_sp1.3.174/compiler/lib/intel64;/usr/lib/gcc/x86_64-redhat-linux/4.4.7;/g/g92/miguel/code/libmesh_2D/lib
>
>
>These are variables in my environment that I use in CMake with
>$ENV{VAR}. How can I use this information for the commands:
>
>include_directories($ENV{INCLUDE_DIRS})
>
>link_directories($ENV{LIB_DIRS})
>
>target_link_libraries($ENV{LIBS}) ?
>
>
>It seems that cmake can digest the include directories and the
>target_link_libraries (because they appear correctly in the
>compilation), but not the link_directories. Why? Also, I’ve read that
>it is more correct to use find_library() instead. How would I iterate
>over the LIBS? Can I use a single LIB_DIRS (with all the information
>above) in the PATHS argument of find_library()
>
>
>Thanks
>
>Miguel
>
>--
>
>Powered by
>http://secure-web.cisco.com/1SkTeDpqcSTqs7V0Q2yjUdQEsQ1huaYLleRl_DSB40mZrJmSB4Lr6utBlMnP2n8teBgjMf-JqbxyEzxRwI33xdCPfZ4V-R2DL7hRPikFqd9-Rs0WFTInnFgBOVb385LKZzSj7s6rnXOZg-2XG27MJ2-q9sNDHuOdRClebWLFsHqVgj0HGuWMrWGh1kE2S9-TyKuTes7ceD6P0h7C_OsCM_EQXdmhkDGCqyKLK6MRTupY6_HJ1roZBy2Y98SiMF_6LXWUyvKR_raD6crErzRofBLqtBN4vsNeqHBC88J3gYM2BgpkiDnNxonEQy0GonMqIPBKPG9ORW1sEj7-QXajnhYY6cXvu-1TI6aW8FSgTSzZxgdA9zvzoea-DB1
>

Re: [CMake] Parsing command line arguments from the make

2016-04-01 Thread Fedja Jeleskovic

To make my question a bit more clear, I am trying to figure out how to add
these things so my make will be able to use them. If I need environment
variable inside the cmake, I could use $ENV{VARIABLE_NAME} and have it.

The problem is to create the code inside the CMakeLists.txt, so that
generated Makefile will be able to get before and after arguments that are
supplied.
-- 

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] Building a tool immediately so it can be used later in same CMake run

2016-04-01 Thread Tamás Kenéz

Craig,

My cmake-based build system in my company's CI framework works exactly that
way: there's a generic cmake script[1] (invoked with cmake -P) that reads
in a file which contains repo-urls and build parameters for 50+ projects
and builds them for 3 platforms (linux, win, mac) 5 compilers
(cross-compilers, too) invoking child cmake builds with execute_process.
This is done after each push and one daily clean build.

I've never had any problems with that approach.

On the other hand, the system was originally designed with ExternalProject
and I had many problems.

[1]: https://github.com/tamaskenez/centralbuilder

Tamas



On Fri, Apr 1, 2016 at 1:53 AM, Craig Scott  wrote:

> All,
>
> I originally planned to ask this question directly on this mailing list,
> but it got a bit more involved, so I posted it to stackoverflow instead.
> I'm interested if anyone can shed some more authoritative light on the
> proposed method for the following question:
>
> http://stackoverflow.com/q/36084785/1938798
>
> *Short version*: invoke a nested cmake-and-build immediately within the
> main CMake run to build a specific target via execute_process(). This makes
> that tool available for use still within the same (main) CMake run. An
> ExternalProject-based technique would normally be a better solution, but in
> this particular case, that wasn't possible.
>
> I'd be interested if anyone can confirm whether the suggested approach is
> guaranteed to be safe for all generators and platforms, or whether there
> are other factors I have not considered in the proposed technique.
>
> Cheers
>
> --
> Craig Scott
> Melbourne, Australia
> http://crascit.com
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
>
-- 

Powered by www.kitware.com

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

Kitware offers various 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] Is there any ongoing work to support toolset Clang 3.7 with Microsoft CodeGen (v140_clang_3_7)

2016-04-01 Thread forumer


Hi,

Microsoft has released a new toolset using clang for the code analysis 
and with VS2015 code generator.


https://blogs.msdn.microsoft.com/vcblog/2015/12/04/clang-with-microsoft-codegen-in-vs-2015-update-1/
https://blogs.msdn.microsoft.com/vcblog/2016/01/20/clang-with-microsoft-codegen-january-2016-released/

IS there any ongoing work to support the v140_clang_3_7 for VS2015 ?
Something like:


cmake -G "Visual Studio 14 2015" -T v140_clang_3_7


For the moment if I want to test I have to use the VS2015 generator and 
then manually change the Platform Toolset and warnings level



Thanks

--

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] Regarding installation of ITK

2016-04-01 Thread Mavitha Sri

Hello Sir/Madam,

Great Day,

I am going to use ITK tool kit for my project,So,i tried to install ITK
tool in my system.But it showing some error when configuring the CMake. And
i have also attached the error.So,please kindly help me  to solve this
error.

ITK version-3.20.1
CMake version-2.8.9
-- 

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] Building a tool immediately so it can be used later in same CMake run

2016-04-01 Thread Craig Scott

All,

I originally planned to ask this question directly on this mailing list,
but it got a bit more involved, so I posted it to stackoverflow instead.
I'm interested if anyone can shed some more authoritative light on the
proposed method for the following question:

http://stackoverflow.com/q/36084785/1938798

*Short version*: invoke a nested cmake-and-build immediately within the
main CMake run to build a specific target via execute_process(). This makes
that tool available for use still within the same (main) CMake run. An
ExternalProject-based technique would normally be a better solution, but in
this particular case, that wasn't possible.

I'd be interested if anyone can confirm whether the suggested approach is
guaranteed to be safe for all generators and platforms, or whether there
are other factors I have not considered in the proposed technique.

Cheers

-- 
Craig Scott
Melbourne, Australia
http://crascit.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.5.1-778-g67ca15f

2016-04-01 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  67ca15ff15fe4fd0e8a873ff076517e6d5e312a3 (commit)
   via  6cece60ce47ac9b764d3e0e652acd2abdde4ce40 (commit)
   via  a0fc9e24d2ff8f1653b5729047fcf8db22481d6f (commit)
  from  128278a644e91110672cd0a3579478dcc1b32d96 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=67ca15ff15fe4fd0e8a873ff076517e6d5e312a3
commit 67ca15ff15fe4fd0e8a873ff076517e6d5e312a3
Merge: 128278a 6cece60
Author: Brad King 
AuthorDate: Fri Apr 1 10:34:07 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 10:34:07 2016 -0400

Merge topic 'fix-target-alias-in-subdir' into next

6cece60c Rename local target lookup methods to clarify purpose
a0fc9e24 fixup! Fix lookup of an ALIAS target outside aliased target's 
directory


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6cece60ce47ac9b764d3e0e652acd2abdde4ce40
commit 6cece60ce47ac9b764d3e0e652acd2abdde4ce40
Author: Brad King 
AuthorDate: Fri Apr 1 10:26:08 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 10:29:26 2016 -0400

Rename local target lookup methods to clarify purpose

Rename methods:

* `cmMakefile::Find{ => LocalNonAlias}Target`
* `cmLocalGenerator::Find{ => LocalNonAlias}GeneratorTarget`

These names clarify that they are for directory-local target names
and do not consider alias targets.

diff --git a/Source/cmFLTKWrapUICommand.cxx b/Source/cmFLTKWrapUICommand.cxx
index d17d664..c64e813 100644
--- a/Source/cmFLTKWrapUICommand.cxx
+++ b/Source/cmFLTKWrapUICommand.cxx
@@ -117,7 +117,7 @@ void cmFLTKWrapUICommand::FinalPass()
   // people should add the srcs to the target themselves, but the old command
   // didn't support that, so check and see if they added the files in and if
   // they didn;t then print a warning and add then anyhow
-  cmTarget* target = this->Makefile->FindTarget(this->Target);
+  cmTarget* target = this->Makefile->FindLocalNonAliasTarget(this->Target);
   if(!target)
 {
 std::string msg =
diff --git a/Source/cmInstallCommand.cxx b/Source/cmInstallCommand.cxx
index 2d78a41..7e72a8a 100644
--- a/Source/cmInstallCommand.cxx
+++ b/Source/cmInstallCommand.cxx
@@ -381,7 +381,7 @@ bool 
cmInstallCommand::HandleTargetsMode(std::vector const& args)
   return false;
   }
 // Lookup this target in the current directory.
-if(cmTarget* target=this->Makefile->FindTarget(*targetIt))
+if(cmTarget* target=this->Makefile->FindLocalNonAliasTarget(*targetIt))
   {
   // Found the target.  Check its type.
   if(target->GetType() != cmState::EXECUTABLE &&
diff --git a/Source/cmInstallTargetGenerator.cxx 
b/Source/cmInstallTargetGenerator.cxx
index 5e88fa2..b93fb8d 100644
--- a/Source/cmInstallTargetGenerator.cxx
+++ b/Source/cmInstallTargetGenerator.cxx
@@ -446,7 +446,7 @@ 
cmInstallTargetGenerator::GetInstallFilename(cmGeneratorTarget const* target,
 
 void cmInstallTargetGenerator::Compute(cmLocalGenerator* lg)
 {
-  this->Target = lg->FindGeneratorTarget(this->TargetName);
+  this->Target = lg->FindLocalNonAliasGeneratorTarget(this->TargetName);
 }
 
 //
diff --git a/Source/cmLocalGenerator.cxx b/Source/cmLocalGenerator.cxx
index 6153fbd..586e4c6 100644
--- a/Source/cmLocalGenerator.cxx
+++ b/Source/cmLocalGenerator.cxx
@@ -485,7 +485,7 @@ private:
   std::string Name;
 };
 
-cmGeneratorTarget* cmLocalGenerator::FindGeneratorTarget(
+cmGeneratorTarget* cmLocalGenerator::FindLocalNonAliasGeneratorTarget(
 const std::string& name) const
 {
   std::vector::const_iterator ti =
@@ -1828,7 +1828,7 @@ cmLocalGenerator::FindGeneratorTargetToUse(const 
std::string& name) const
 return *imported;
 }
 
-  if(cmGeneratorTarget* t = this->FindGeneratorTarget(name))
+  if(cmGeneratorTarget* t = this->FindLocalNonAliasGeneratorTarget(name))
 {
 return t;
 }
diff --git a/Source/cmLocalGenerator.h b/Source/cmLocalGenerator.h
index 68e7667..b673a85 100644
--- a/Source/cmLocalGenerator.h
+++ b/Source/cmLocalGenerator.h
@@ -129,7 +129,8 @@ public:
   void AddImportedGeneratorTarget(cmGeneratorTarget* gt);
   void AddOwnedImportedGeneratorTarget(cmGeneratorTarget* gt);
 
-  cmGeneratorTarget* FindGeneratorTarget(const std::string& name) const;
+  cmGeneratorTarget*
+FindLocalNonAliasGeneratorTarget(const std::string& name) const;
   cmGeneratorTarget* FindGeneratorTargetToUse(const std::string& name) const;

[Cmake-commits] CMake branch, master, updated. v3.5.1-361-ge8c1363

2016-04-01 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  e8c1363ee8f08cf0b36e17f85ddb461abd06e0b6 (commit)
   via  168e44e2028d905272323e0a66e3735c30460f5a (commit)
   via  731ad1724f08fb4255664fe8e09c581ad9c062fb (commit)
  from  9e33f02bd9ac9e35256b371df936ab67e615601a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e8c1363ee8f08cf0b36e17f85ddb461abd06e0b6
commit e8c1363ee8f08cf0b36e17f85ddb461abd06e0b6
Merge: 9e33f02 168e44e
Author: Brad King 
AuthorDate: Fri Apr 1 10:01:52 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 10:01:52 2016 -0400

Merge topic 'update-kwsys'

168e44e2 Merge branch 'upstream-KWSys' into update-kwsys
731ad172 KWSys 2016-03-31 (3392da1d)


---

Summary of changes:
 Source/kwsys/SystemTools.cxx |5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)


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

Re: [cmake-developers] [PATCH] language detection in FindBLAS and FindLAPACK (#0016039)

2016-04-01 Thread Ben Boeckel

On Fri, Apr 01, 2016 at 16:20:10 +0200, Nils Gladitz wrote:
> This might be a use case for the newish IN_LIST operator?
> 
> e.g. if(Fortran IN_LIST _LANGUAGES_)

How have I missed this‽

*goes and makes minimum version of all CMake projects 3.3* ;)

--Ben
-- 

Powered by www.kitware.com

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

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

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

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

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

[Cmake-commits] CMake branch, next, updated. v3.5.1-773-gc34d735

2016-04-01 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  c34d7353a1e05cc766394691d166daeac01c84e6 (commit)
   via  e0cc8bf5d7f82cf38ef5e1a643843e244a8f98d6 (commit)
   via  05f2ca70ad50d877059a4434fa28ac77c2cb7930 (commit)
   via  2d226ea895d9ca987e3fc8be897df91033d011a4 (commit)
   via  de7f2ae3f13c183c534f2298a1452ddd5c6e0aaa (commit)
   via  e8c1363ee8f08cf0b36e17f85ddb461abd06e0b6 (commit)
   via  9e33f02bd9ac9e35256b371df936ab67e615601a (commit)
  from  cf723c4cfbf1a71749c7b987a5348034703f91cc (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c34d7353a1e05cc766394691d166daeac01c84e6
commit c34d7353a1e05cc766394691d166daeac01c84e6
Merge: cf723c4 e0cc8bf
Author: Brad King 
AuthorDate: Fri Apr 1 10:06:25 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 10:06:25 2016 -0400

Merge branch 'master' into next


---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


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

[Cmake-commits] CMake branch, next, updated. v3.5.1-766-gcf723c4

2016-04-01 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  cf723c4cfbf1a71749c7b987a5348034703f91cc (commit)
   via  af7c29f98c7fd569afcf8f37f76b1ff6cd23edb8 (commit)
  from  5b146672d69eb0fc001d468fb82699a89f73cf3c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=cf723c4cfbf1a71749c7b987a5348034703f91cc
commit cf723c4cfbf1a71749c7b987a5348034703f91cc
Merge: 5b14667 af7c29f
Author: Ben Boeckel 
AuthorDate: Fri Apr 1 10:04:51 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 10:04:51 2016 -0400

Merge topic 'ctest-run-submodule-sync' into next

af7c29f9 fixup! cmCTestGIT: add an option to initialize submodules on update


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=af7c29f98c7fd569afcf8f37f76b1ff6cd23edb8
commit af7c29f98c7fd569afcf8f37f76b1ff6cd23edb8
Author: Ben Boeckel 
AuthorDate: Fri Apr 1 10:03:47 2016 -0400
Commit: Ben Boeckel 
CommitDate: Fri Apr 1 10:03:47 2016 -0400

fixup! cmCTestGIT: add an option to initialize submodules on update

diff --git a/Modules/DartConfiguration.tcl.in b/Modules/DartConfiguration.tcl.in
index 2da8354..c2341c9 100644
--- a/Modules/DartConfiguration.tcl.in
+++ b/Modules/DartConfiguration.tcl.in
@@ -52,6 +52,7 @@ SVNUpdateOptions: @SVN_UPDATE_OPTIONS@
 
 # Git options
 GITCommand: @GITCOMMAND@
+GITInitSubmodules: @GIT_INIT_SUBMODULES@
 GITUpdateOptions: @GIT_UPDATE_OPTIONS@
 GITUpdateCustom: @CTEST_GIT_UPDATE_CUSTOM@
 

---

Summary of changes:
 Modules/DartConfiguration.tcl.in |1 +
 1 file changed, 1 insertion(+)


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.5.1-775-g128278a

2016-04-01 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  128278a644e91110672cd0a3579478dcc1b32d96 (commit)
   via  102a40f156eaf989ccb333d4949d788491a9baf9 (commit)
  from  c34d7353a1e05cc766394691d166daeac01c84e6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=128278a644e91110672cd0a3579478dcc1b32d96
commit 128278a644e91110672cd0a3579478dcc1b32d96
Merge: c34d735 102a40f
Author: Brad King 
AuthorDate: Fri Apr 1 10:15:07 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 10:15:07 2016 -0400

Merge topic 'ctest-run-submodule-sync' into next

102a40f1 fixup! cmCTestGIT: add an option to initialize submodules on update


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=102a40f156eaf989ccb333d4949d788491a9baf9
commit 102a40f156eaf989ccb333d4949d788491a9baf9
Author: Brad King 
AuthorDate: Fri Apr 1 10:14:51 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 10:14:51 2016 -0400

fixup! cmCTestGIT: add an option to initialize submodules on update

diff --git a/Help/manual/ctest.1.rst b/Help/manual/ctest.1.rst
index ede4b78..1179f56 100644
--- a/Help/manual/ctest.1.rst
+++ b/Help/manual/ctest.1.rst
@@ -593,7 +593,7 @@ Configuration settings to specify the version control tool 
include:
   If set, CTest will update the repository's submodules before updating.
 
   * `CTest Script`_ variable: :variable:`CTEST_GIT_INIT_SUBMODULES`
-  * :module:`CTest` module variable: ``GIT_INIT_SUBMODULES``
+  * :module:`CTest` module variable: ``CTEST_GIT_INIT_SUBMODULES``
 
 ``GITUpdateCustom``
   Specify a custom command line (as a semicolon-separated list) to run
diff --git a/Modules/DartConfiguration.tcl.in b/Modules/DartConfiguration.tcl.in
index c2341c9..0ff2eed 100644
--- a/Modules/DartConfiguration.tcl.in
+++ b/Modules/DartConfiguration.tcl.in
@@ -52,7 +52,7 @@ SVNUpdateOptions: @SVN_UPDATE_OPTIONS@
 
 # Git options
 GITCommand: @GITCOMMAND@
-GITInitSubmodules: @GIT_INIT_SUBMODULES@
+GITInitSubmodules: @CTEST_GIT_INIT_SUBMODULES@
 GITUpdateOptions: @GIT_UPDATE_OPTIONS@
 GITUpdateCustom: @CTEST_GIT_UPDATE_CUSTOM@
 

---

Summary of changes:
 Help/manual/ctest.1.rst  |2 +-
 Modules/DartConfiguration.tcl.in |2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)


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

[cmake-developers] [PATCH v2] ExternalProject: Allow TLS_VERIFY for git clones

2016-04-01 Thread Samir Benmendil

Use the git config `http.sslVerify=false` to disable strict ssl for git
commands.
---
Changes in v2:
- git_options is now a list

 Modules/ExternalProject.cmake | 23 +--
 1 file changed, 17 insertions(+), 6 deletions(-)

diff --git a/Modules/ExternalProject.cmake b/Modules/ExternalProject.cmake
index 1185a81..8d8382f 100644
--- a/Modules/ExternalProject.cmake
+++ b/Modules/ExternalProject.cmake
@@ -499,7 +499,7 @@ define_property(DIRECTORY PROPERTY "EP_UPDATE_DISCONNECTED" 
INHERITED
   "ExternalProject module."
   )
 
-function(_ep_write_gitclone_script script_filename source_dir git_EXECUTABLE 
git_repository git_tag git_remote_name git_submodules src_name work_dir 
gitclone_infofile gitclone_stampfile)
+function(_ep_write_gitclone_script script_filename source_dir git_EXECUTABLE 
git_repository git_tag git_remote_name git_submodules src_name work_dir 
gitclone_infofile gitclone_stampfile tls_verify)
   file(WRITE ${script_filename}
 "if(\"${git_tag}\" STREQUAL \"\")
   message(FATAL_ERROR \"Tag for git checkout should not be empty.\")
@@ -524,12 +524,18 @@ if(error_code)
   message(FATAL_ERROR \"Failed to remove directory: '${source_dir}'\")
 endif()
 
+set(git_options)
+if(NOT tls_verify)
+  list(APPEND git_options
+-c http.sslVerify=false)
+endif()
+
 # try the clone 3 times incase there is an odd git clone issue
 set(error_code 1)
 set(number_of_tries 0)
 while(error_code AND number_of_tries LESS 3)
   execute_process(
-COMMAND \"${git_EXECUTABLE}\" clone --origin \"${git_remote_name}\" 
\"${git_repository}\" \"${src_name}\"
+COMMAND \"${git_EXECUTABLE}\" \${git_options} clone --origin 
\"${git_remote_name}\" \"${git_repository}\" \"${src_name}\"
 WORKING_DIRECTORY \"${work_dir}\"
 RESULT_VARIABLE error_code
 )
@@ -544,7 +550,7 @@ if(error_code)
 endif()
 
 execute_process(
-  COMMAND \"${git_EXECUTABLE}\" checkout ${git_tag}
+  COMMAND \"${git_EXECUTABLE}\" \${git_options} checkout ${git_tag}
   WORKING_DIRECTORY \"${work_dir}/${src_name}\"
   RESULT_VARIABLE error_code
   )
@@ -553,7 +559,7 @@ if(error_code)
 endif()
 
 execute_process(
-  COMMAND \"${git_EXECUTABLE}\" submodule init ${git_submodules}
+  COMMAND \"${git_EXECUTABLE}\" \${git_options} submodule init 
${git_submodules}
   WORKING_DIRECTORY \"${work_dir}/${src_name}\"
   RESULT_VARIABLE error_code
   )
@@ -562,7 +568,7 @@ if(error_code)
 endif()
 
 execute_process(
-  COMMAND \"${git_EXECUTABLE}\" submodule update --recursive ${git_submodules}
+  COMMAND \"${git_EXECUTABLE}\" \${git_options} submodule update --recursive 
${git_submodules}
   WORKING_DIRECTORY \"${work_dir}/${src_name}\"
   RESULT_VARIABLE error_code
   )
@@ -1777,6 +1783,11 @@ function(_ep_add_download_command name)
   set(git_remote_name "origin")
 endif()
 
+get_property(tls_verify TARGET ${name} PROPERTY _EP_TLS_VERIFY)
+if(NOT tls_verify)
+  set(tls_verify OFF)
+endif()
+
 # For the download step, and the git clone operation, only the repository
 # should be recorded in a configured RepositoryInfo file. If the repo
 # changes, the clone script should be run again. But if only the tag
@@ -1801,7 +1812,7 @@ function(_ep_add_download_command name)
 #
 _ep_write_gitclone_script(${tmp_dir}/${name}-gitclone.cmake ${source_dir}
   ${GIT_EXECUTABLE} ${git_repository} ${git_tag} ${git_remote_name} 
"${git_submodules}" ${src_name} ${work_dir}
-  ${stamp_dir}/${name}-gitinfo.txt 
${stamp_dir}/${name}-gitclone-lastrun.txt
+  ${stamp_dir}/${name}-gitinfo.txt 
${stamp_dir}/${name}-gitclone-lastrun.txt ${tls_verify}
   )
 set(comment "Performing download step (git clone) for '${name}'")
 set(cmd ${CMAKE_COMMAND} -P ${tmp_dir}/${name}-gitclone.cmake)
-- 
2.8.0

-- 

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] language detection in FindBLAS and FindLAPACK (#0016039)

2016-04-01 Thread Rolf Eike Beer

Am Freitag, 1. April 2016, 16:20:10 schrieb Nils Gladitz:
> On 04/01/2016 02:44 PM, melven.roehrig-zoell...@dlr.de wrote:
> > Patch for a problem with find_package(BLAS/LAPACK) on Windows for pure
> > Fortran projects reported by me in
> > https://cmake.org/Bug/view.php?id=16039.
> This might be a use case for the newish IN_LIST operator?
> 
> e.g. if(Fortran IN_LIST _LANGUAGES_)

Why not simply:

 if (CMAKE_Fortran_COMPILER_LOADED)

Greetings,

Eike

signature.asc
Description: This is a digitally signed message part.
-- 

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] ExternalProject: Allow TLS_VERIFY for git clones

2016-04-01 Thread Ben Boeckel

On Fri, Apr 01, 2016 at 10:58:50 +0100, Samir Benmendil wrote:
> +# set git_options
> +if(NOT tls_verify)
> +  set(git_options -c http.sslVerify=false)
> +endif()

Looks good overall, but could this be turned into a pattern like:

set(git_options)
if (NOT tls_verify)
  list(APPEND git_options
-c http.sslVerify=false)
endif ()

to help out future options which might make sense?

Thanks,

--Ben
-- 

Powered by www.kitware.com

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

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

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

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

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

[Cmake-commits] CMake branch, master, updated. v3.5.1-372-ge0cc8bf

2016-04-01 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  e0cc8bf5d7f82cf38ef5e1a643843e244a8f98d6 (commit)
   via  eae4eef0c48188027b5c25657054b12b6b301c85 (commit)
  from  05f2ca70ad50d877059a4434fa28ac77c2cb7930 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e0cc8bf5d7f82cf38ef5e1a643843e244a8f98d6
commit e0cc8bf5d7f82cf38ef5e1a643843e244a8f98d6
Merge: 05f2ca7 eae4eef
Author: Brad King 
AuthorDate: Fri Apr 1 10:04:32 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 10:04:32 2016 -0400

Merge topic 'cpack-rpm-external-symlink-handling'

eae4eef0 CPack/RPM external symlink handling


---

Summary of changes:
 .../dev/cpack-rpm-external-symlink-handling.rst|5 
 Modules/CPackRPM.cmake |   30 +++-
 Tests/CPackComponentsForAll/CMakeLists.txt |3 ++
 .../RunCPackVerifyResult.cmake |3 ++
 4 files changed, 34 insertions(+), 7 deletions(-)
 create mode 100644 Help/release/dev/cpack-rpm-external-symlink-handling.rst


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.5.1-370-g05f2ca7

2016-04-01 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  05f2ca70ad50d877059a4434fa28ac77c2cb7930 (commit)
   via  fae80ee2c347b87a65b80a3c8caa598c40680cc0 (commit)
  from  2d226ea895d9ca987e3fc8be897df91033d011a4 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=05f2ca70ad50d877059a4434fa28ac77c2cb7930
commit 05f2ca70ad50d877059a4434fa28ac77c2cb7930
Merge: 2d226ea fae80ee
Author: Brad King 
AuthorDate: Fri Apr 1 10:02:50 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 10:02:50 2016 -0400

Merge topic 'check-compiler-flag-clang-cl'

fae80ee2 Check*CompilerFlag: Add another pattern for Clang (#16038)


---

Summary of changes:
 Modules/CMakeCheckCompilerFlagCommonPatterns.cmake |1 +
 1 file changed, 1 insertion(+)


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.5.1-368-g2d226ea

2016-04-01 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  2d226ea895d9ca987e3fc8be897df91033d011a4 (commit)
   via  fad5d59cf42ad876aa5553fe34beaf6a8f5a6cd1 (commit)
   via  72a862a55bdf16f4ff41239d400bd6b1aacfc7c2 (commit)
   via  a3468b78f21d6f3520a351fde6db6dd9153df948 (commit)
   via  85b2bb6cb48a431c3f941227302b42bd7588edfb (commit)
  from  de7f2ae3f13c183c534f2298a1452ddd5c6e0aaa (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2d226ea895d9ca987e3fc8be897df91033d011a4
commit 2d226ea895d9ca987e3fc8be897df91033d011a4
Merge: de7f2ae fad5d59
Author: Brad King 
AuthorDate: Fri Apr 1 10:02:47 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 10:02:47 2016 -0400

Merge topic 'add-CMAKE_EXTRA_INCLUDE_FILES-to-CMakePushCheckState'

fad5d59c PushCheckStateTest: Update test to check CMAKE_EXTRA_INCLUDE_FILES
72a862a5 CMakePushCheckState: Add support for CMAKE_EXTRA_INCLUDE_FILES
a3468b78 PushCheckStateTest: Test all variables managed by the module
85b2bb6c PushCheckStateTest: Fix syntax warning


---

Summary of changes:
 ...akePushCheckState-CMAKE_EXTRA_INCLUDE_FILES.rst |5 ++
 Modules/CMakePushCheckState.cmake  |7 ++-
 Tests/CMakeTests/PushCheckStateTest.cmake.in   |   57 
 3 files changed, 58 insertions(+), 11 deletions(-)
 create mode 100644 
Help/release/dev/CMakePushCheckState-CMAKE_EXTRA_INCLUDE_FILES.rst


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

Re: [cmake-developers] [PATCH] language detection in FindBLAS and FindLAPACK (#0016039)

2016-04-01 Thread Ben Boeckel

On Fri, Apr 01, 2016 at 12:44:29 +, melven.roehrig-zoell...@dlr.de wrote:
> Patch for a problem with find_package(BLAS/LAPACK) on Windows for pure
> Fortran projects reported by me in
> https://cmake.org/Bug/view.php?id=16039.

Thanks. My patch looks similar (differs in variable names basically),
but I hadn't gotten around to testing it.

--Ben
-- 

Powered by www.kitware.com

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

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

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

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

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

[Cmake-commits] CMake branch, next, updated. v3.5.1-781-g5d94f12

2016-04-01 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  5d94f12a78d259d4453913f345b882067cf45333 (commit)
   via  e47ec3c9ffe0effce184bff89b36d893a5fda971 (commit)
   via  e1eae2a3fb5b03dca3275cc8c637286ae4ce1e2f (commit)
  from  67ca15ff15fe4fd0e8a873ff076517e6d5e312a3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5d94f12a78d259d4453913f345b882067cf45333
commit 5d94f12a78d259d4453913f345b882067cf45333
Merge: 67ca15f e47ec3c
Author: Brad King 
AuthorDate: Fri Apr 1 10:39:33 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 10:39:33 2016 -0400

Merge topic 'fix-target-alias-in-subdir' into next

e47ec3c9 Rename local target lookup methods to clarify purpose
e1eae2a3 Fix lookup of an ALIAS target outside aliased target's directory 
(#16044)


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e47ec3c9ffe0effce184bff89b36d893a5fda971
commit e47ec3c9ffe0effce184bff89b36d893a5fda971
Author: Brad King 
AuthorDate: Fri Apr 1 10:26:08 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 10:39:25 2016 -0400

Rename local target lookup methods to clarify purpose

Rename methods:

* `cmMakefile::Find{ => LocalNonAlias}Target`
* `cmLocalGenerator::Find{ => LocalNonAlias}GeneratorTarget`

These names clarify that they are for directory-local target names
and do not consider alias targets.

diff --git a/Source/cmFLTKWrapUICommand.cxx b/Source/cmFLTKWrapUICommand.cxx
index d17d664..c64e813 100644
--- a/Source/cmFLTKWrapUICommand.cxx
+++ b/Source/cmFLTKWrapUICommand.cxx
@@ -117,7 +117,7 @@ void cmFLTKWrapUICommand::FinalPass()
   // people should add the srcs to the target themselves, but the old command
   // didn't support that, so check and see if they added the files in and if
   // they didn;t then print a warning and add then anyhow
-  cmTarget* target = this->Makefile->FindTarget(this->Target);
+  cmTarget* target = this->Makefile->FindLocalNonAliasTarget(this->Target);
   if(!target)
 {
 std::string msg =
diff --git a/Source/cmInstallCommand.cxx b/Source/cmInstallCommand.cxx
index 2d78a41..7e72a8a 100644
--- a/Source/cmInstallCommand.cxx
+++ b/Source/cmInstallCommand.cxx
@@ -381,7 +381,7 @@ bool 
cmInstallCommand::HandleTargetsMode(std::vector const& args)
   return false;
   }
 // Lookup this target in the current directory.
-if(cmTarget* target=this->Makefile->FindTarget(*targetIt))
+if(cmTarget* target=this->Makefile->FindLocalNonAliasTarget(*targetIt))
   {
   // Found the target.  Check its type.
   if(target->GetType() != cmState::EXECUTABLE &&
diff --git a/Source/cmInstallTargetGenerator.cxx 
b/Source/cmInstallTargetGenerator.cxx
index 5e88fa2..b93fb8d 100644
--- a/Source/cmInstallTargetGenerator.cxx
+++ b/Source/cmInstallTargetGenerator.cxx
@@ -446,7 +446,7 @@ 
cmInstallTargetGenerator::GetInstallFilename(cmGeneratorTarget const* target,
 
 void cmInstallTargetGenerator::Compute(cmLocalGenerator* lg)
 {
-  this->Target = lg->FindGeneratorTarget(this->TargetName);
+  this->Target = lg->FindLocalNonAliasGeneratorTarget(this->TargetName);
 }
 
 //
diff --git a/Source/cmLocalGenerator.cxx b/Source/cmLocalGenerator.cxx
index 6153fbd..586e4c6 100644
--- a/Source/cmLocalGenerator.cxx
+++ b/Source/cmLocalGenerator.cxx
@@ -485,7 +485,7 @@ private:
   std::string Name;
 };
 
-cmGeneratorTarget* cmLocalGenerator::FindGeneratorTarget(
+cmGeneratorTarget* cmLocalGenerator::FindLocalNonAliasGeneratorTarget(
 const std::string& name) const
 {
   std::vector::const_iterator ti =
@@ -1828,7 +1828,7 @@ cmLocalGenerator::FindGeneratorTargetToUse(const 
std::string& name) const
 return *imported;
 }
 
-  if(cmGeneratorTarget* t = this->FindGeneratorTarget(name))
+  if(cmGeneratorTarget* t = this->FindLocalNonAliasGeneratorTarget(name))
 {
 return t;
 }
diff --git a/Source/cmLocalGenerator.h b/Source/cmLocalGenerator.h
index 68e7667..b673a85 100644
--- a/Source/cmLocalGenerator.h
+++ b/Source/cmLocalGenerator.h
@@ -129,7 +129,8 @@ public:
   void AddImportedGeneratorTarget(cmGeneratorTarget* gt);
   void AddOwnedImportedGeneratorTarget(cmGeneratorTarget* gt);
 
-  cmGeneratorTarget* FindGeneratorTarget(const std::string& name) const;
+  cmGeneratorTarget*
+FindLocalNonAliasGeneratorTarget(const std::string& name) const;
   cmGeneratorTarget* FindGeneratorTargetToUse(const std::string& name)

[Cmake-commits] CMake branch, master, updated. v3.5.1-363-gde7f2ae

2016-04-01 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  de7f2ae3f13c183c534f2298a1452ddd5c6e0aaa (commit)
   via  4828a78c1080d36935904a9620911a6f3743d792 (commit)
  from  e8c1363ee8f08cf0b36e17f85ddb461abd06e0b6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=de7f2ae3f13c183c534f2298a1452ddd5c6e0aaa
commit de7f2ae3f13c183c534f2298a1452ddd5c6e0aaa
Merge: e8c1363 4828a78
Author: Brad King 
AuthorDate: Fri Apr 1 10:01:58 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 10:01:58 2016 -0400

Merge topic 'eclipse-source-groups'

4828a78c Eclipse: Implement traversal of nested source groups (#15701)


---

Summary of changes:
 Source/cmExtraEclipseCDT4Generator.cxx |   72 +++-
 Source/cmExtraEclipseCDT4Generator.h   |3 ++
 2 files changed, 47 insertions(+), 28 deletions(-)


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

[cmake-developers] [CMake 0016047]: automoc generates wrong #includes for projects in a symlinked path

2016-04-01 Thread Mantis Bug Tracker


The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16047 
== 
Reported By:Maurizio Paolini
Assigned To:
== 
Project:CMake
Issue ID:   16047
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-01 13:36 EDT
Last Modified:  2016-04-01 13:36 EDT
== 
Summary:automoc generates wrong #includes for projects in a
symlinked path
Description: 
project "kig" uses cmake and automoc.
My local copy of the git sources are located in a folder that I reach following
a symlink
(it resides in a local partition whereas my home is on an NFS-mounted
filesystem).
after a cmake and then a "make", the generated "moc*" files contain
an "#include" like this:

#include
"../../../../../misc/euclide/paolini/Git/kdeedu/kig/modes/popup/popup.h"

There is a wrong number of ".." and the path does not work.
using "make VERBOSE=1 kigpart_automoc" it turns out that the following command
is issued:

/usr/lib/qt5/bin/moc -I/home/matem/paolini/Git/kdeedu/kig/modes [...] -o
/home/matem/paolini/Git/kdeedu/kig/moc_popup.cpp
/home/misc/euclide/paolini/Git/kdeedu/kig/modes/popup/popup.h

where the [...] part contains many more -I and various options. Notice that
"/home/matem/paolini/Git/" and "/home/misc/euclide/paolini/Git/" point to the
same place, the first through the symlink "Git", the second is the physical
path.
I guess that then "moc" tries hard to walk (with a relative path) from
one path to the other, but there is no way to successfully climb up
a path with a symlink in it using the ".." directory.

This problem was previously reported in the QT bug tracker
https://bugreports.qt.io/browse/QTBUG-51964



Steps to Reproduce: 
$ mkdir -p a/b
$ ln -s a/b a.lnk
$ cd a.lnk
$ 
$ cd 
$ cmake . [...]
$ make

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-01 13:36 Maurizio PaoliniNew 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] [PATCH v2] ExternalProject: Allow TLS_VERIFY for git clones

2016-04-01 Thread Ben Boeckel

On Fri, Apr 01, 2016 at 15:39:26 +0100, Samir Benmendil wrote:
> Use the git config `http.sslVerify=false` to disable strict ssl for git
> commands.
> ---
> Changes in v2:
> - git_options is now a list

Thanks.

I've pushed this into next for testing.

--Ben
-- 

Powered by www.kitware.com

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

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

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

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

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

[Cmake-commits] CMake branch, next, updated. v3.5.1-783-g6aadc4a

2016-04-01 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  6aadc4a25a07856a81262946b514884df95f795f (commit)
   via  272779ce6aa4dbf15e2791ca3f3f5cbf1ce57b39 (commit)
  from  5d94f12a78d259d4453913f345b882067cf45333 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6aadc4a25a07856a81262946b514884df95f795f
commit 6aadc4a25a07856a81262946b514884df95f795f
Merge: 5d94f12 272779c
Author: Ben Boeckel 
AuthorDate: Fri Apr 1 13:17:39 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 13:17:39 2016 -0400

Merge topic 'ep-tls-verify-git' into next

272779ce ExternalProject: Allow TLS_VERIFY for git clones


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=272779ce6aa4dbf15e2791ca3f3f5cbf1ce57b39
commit 272779ce6aa4dbf15e2791ca3f3f5cbf1ce57b39
Author: Samir Benmendil 
AuthorDate: Fri Apr 1 11:49:16 2016 -0400
Commit: Ben Boeckel 
CommitDate: Fri Apr 1 11:49:16 2016 -0400

ExternalProject: Allow TLS_VERIFY for git clones

Use the git config `http.sslVerify=false` to disable strict ssl for git
commands.

diff --git a/Help/release/dev/ep-tls-verify-git.rst 
b/Help/release/dev/ep-tls-verify-git.rst
new file mode 100644
index 000..3c727de
--- /dev/null
+++ b/Help/release/dev/ep-tls-verify-git.rst
@@ -0,0 +1,5 @@
+ep-tls-verify-git
+-
+
+* The :module:`ExternalProject` module now uses ``TLS_VERIFY`` when fetching
+  from git repositories.
diff --git a/Modules/ExternalProject.cmake b/Modules/ExternalProject.cmake
index 1185a81..8d8382f 100644
--- a/Modules/ExternalProject.cmake
+++ b/Modules/ExternalProject.cmake
@@ -499,7 +499,7 @@ define_property(DIRECTORY PROPERTY "EP_UPDATE_DISCONNECTED" 
INHERITED
   "ExternalProject module."
   )
 
-function(_ep_write_gitclone_script script_filename source_dir git_EXECUTABLE 
git_repository git_tag git_remote_name git_submodules src_name work_dir 
gitclone_infofile gitclone_stampfile)
+function(_ep_write_gitclone_script script_filename source_dir git_EXECUTABLE 
git_repository git_tag git_remote_name git_submodules src_name work_dir 
gitclone_infofile gitclone_stampfile tls_verify)
   file(WRITE ${script_filename}
 "if(\"${git_tag}\" STREQUAL \"\")
   message(FATAL_ERROR \"Tag for git checkout should not be empty.\")
@@ -524,12 +524,18 @@ if(error_code)
   message(FATAL_ERROR \"Failed to remove directory: '${source_dir}'\")
 endif()
 
+set(git_options)
+if(NOT tls_verify)
+  list(APPEND git_options
+-c http.sslVerify=false)
+endif()
+
 # try the clone 3 times incase there is an odd git clone issue
 set(error_code 1)
 set(number_of_tries 0)
 while(error_code AND number_of_tries LESS 3)
   execute_process(
-COMMAND \"${git_EXECUTABLE}\" clone --origin \"${git_remote_name}\" 
\"${git_repository}\" \"${src_name}\"
+COMMAND \"${git_EXECUTABLE}\" \${git_options} clone --origin 
\"${git_remote_name}\" \"${git_repository}\" \"${src_name}\"
 WORKING_DIRECTORY \"${work_dir}\"
 RESULT_VARIABLE error_code
 )
@@ -544,7 +550,7 @@ if(error_code)
 endif()
 
 execute_process(
-  COMMAND \"${git_EXECUTABLE}\" checkout ${git_tag}
+  COMMAND \"${git_EXECUTABLE}\" \${git_options} checkout ${git_tag}
   WORKING_DIRECTORY \"${work_dir}/${src_name}\"
   RESULT_VARIABLE error_code
   )
@@ -553,7 +559,7 @@ if(error_code)
 endif()
 
 execute_process(
-  COMMAND \"${git_EXECUTABLE}\" submodule init ${git_submodules}
+  COMMAND \"${git_EXECUTABLE}\" \${git_options} submodule init 
${git_submodules}
   WORKING_DIRECTORY \"${work_dir}/${src_name}\"
   RESULT_VARIABLE error_code
   )
@@ -562,7 +568,7 @@ if(error_code)
 endif()
 
 execute_process(
-  COMMAND \"${git_EXECUTABLE}\" submodule update --recursive ${git_submodules}
+  COMMAND \"${git_EXECUTABLE}\" \${git_options} submodule update --recursive 
${git_submodules}
   WORKING_DIRECTORY \"${work_dir}/${src_name}\"
   RESULT_VARIABLE error_code
   )
@@ -1777,6 +1783,11 @@ function(_ep_add_download_command name)
   set(git_remote_name "origin")
 endif()
 
+get_property(tls_verify TARGET ${name} PROPERTY _EP_TLS_VERIFY)
+if(NOT tls_verify)
+  set(tls_verify OFF)
+endif()
+
 # For the download step, and the git clone operation, only the repository
 # should be recorded in a configured RepositoryInfo file. If the repo
 # changes, the clone script should be run again. But if only the tag
@@ -1801,7 +1812,7 @@ function(_ep_add_download_command name)
 #
 _ep_write_gitclone_script(${tmp_dir}/${name}-gitclone.cmake ${source_dir}
   ${GIT_EXECUTABLE}

Re: [cmake-developers] Fix for re-running FindPythonLibs with multiple configurations

2016-04-01 Thread Brad King

On 03/31/2016 10:31 PM, Richard Christie wrote:
> So I've attached an improved fix, which is much simpler:
> it determines whether PYTHON_LIBRARY is a list and extracts
> the optimized library out of it.

Thanks.  Please try this code instead:

# If we ran before and reported multiple configurations then PYTHON_LIBRARY
# is a list "optimized;PYTHON_LIBRARY;debug;PYTHON_LIBRARY_DEBUG".  Extract
# the original value so we can re-construct the list properly later.
if(";${PYTHON_LIBRARY};" MATCHES ";optimized;([^;]+);")
  set(PYTHON_LIBRARY "${CMAKE_MATCH_1}")
endif()

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 0016048]: Segfault on target_link_libraries() with aliased target from another subdirectory

2016-04-01 Thread Mantis Bug Tracker


The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16048 
== 
Reported By:arlbranch
Assigned To:
== 
Project:CMake
Issue ID:   16048
Category:   CMake
Reproducibility:always
Severity:   crash
Priority:   high
Status: new
== 
Date Submitted: 2016-04-01 15:22 EDT
Last Modified:  2016-04-01 15:22 EDT
== 
Summary:Segfault on target_link_libraries() with aliased
target from another subdirectory
Description: 
CMake crashes with a segfault when target_link_libraries is used to add a
dependency on an alias of a target that was added in a different subdirectory.

Complete Example

[branch@fortuna on /dev/pts/1] 1150 ~/repositories/test/cmake_segfault
$ cmake --version
cmake version 3.5.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).
[branch@fortuna on /dev/pts/1] 1151 ~/repositories/test/cmake_segfault
$ ls -lR
.:
total 12
drwxr-xr-x 2 branch atlsdd 4096 Apr  1 13:37 alib/
drwxr-xr-x 2 branch atlsdd 4096 Apr  1 14:14 blib/
-rw-r--r-- 1 branch atlsdd   98 Apr  1 13:18 CMakeLists.txt

./alib:
total 4
-rw-r--r-- 1 branch atlsdd 87 Apr  1 13:24 CMakeLists.txt

./blib:
total 4
-rw-r--r-- 1 branch atlsdd 162 Apr  1 13:38 CMakeLists.txt
[branch@fortuna on /dev/pts/1] 1152 ~/repositories/test/cmake_segfault
$ cat CMakeLists.txt
cmake_minimum_required(VERSION 2.8.11)
project(top)
add_subdirectory(alib)
add_subdirectory(blib)
[branch@fortuna on /dev/pts/1] 1153 ~/repositories/test/cmake_segfault
$ cat alib/CMakeLists.txt
add_library(alib alib.c)
set_source_files_properties(alib.c PROPERTIES GENERATED TRUE)
[branch@fortuna on /dev/pts/1] 1154 ~/repositories/test/cmake_segfault
$ cat blib/CMakeLists.txt
add_library(blib blib.c)
set_source_files_properties(blib.c PROPERTIES GENERATED TRUE)

add_library(alib::alib ALIAS alib)
target_link_libraries(blib alib::alib)
[branch@fortuna on /dev/pts/1] 1155 ~/repositories/test/cmake_segfault
$ mkdir build && cd build
[branch@fortuna on /dev/pts/1] 1156 ~/repositories/test/cmake_segfault/build
$ cmake ..
-- The C compiler identification is GNU 5.3.0
-- The CXX compiler identification is GNU 5.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
Segmentation fault (core dumped)


Steps to Reproduce: 
1) create the project in the Description
2) run cmake against it

Additional Information: 
Also seen on MacOS.

This is a regression, cmake 3.4 does not crash.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-01 15:22 arlbranch  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.5.1-793-g41abf18

2016-04-01 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  41abf1828417479588d428032d4639fae53efe53 (commit)
   via  c18d91add836f7ce426fcb59b2c65235898f3979 (commit)
   via  7f5607439ed0d1303265d3db0937e90683e698de (commit)
   via  06b310b5d5d8a38fb17df02fee8df750904cfcd0 (commit)
   via  56c1ea40c5e278155025f3823089e2d0fa34054a (commit)
  from  3b472a4ef95fa7441978a49e3d7684b165e94f99 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=41abf1828417479588d428032d4639fae53efe53
commit 41abf1828417479588d428032d4639fae53efe53
Merge: 3b472a4 c18d91a
Author: Brad King 
AuthorDate: Fri Apr 1 15:52:32 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 15:52:32 2016 -0400

Merge topic 'ctest-run-submodule-sync' into next

c18d91ad Help: add release notes for topic 'ctest-run-submodule-sync'
7f560743 cmCTestGIT: run `git submodule sync` before updating submodules
06b310b5 cmCTestGIT: add an option to initialize submodules on update
56c1ea40 cmCTestGIT: fix git version references


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c18d91add836f7ce426fcb59b2c65235898f3979
commit c18d91add836f7ce426fcb59b2c65235898f3979
Author: Ben Boeckel 
AuthorDate: Thu Mar 31 12:31:56 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 15:51:46 2016 -0400

Help: add release notes for topic 'ctest-run-submodule-sync'

diff --git a/Help/release/dev/ctest-run-submodule-sync.rst 
b/Help/release/dev/ctest-run-submodule-sync.rst
new file mode 100644
index 000..c41cc2f
--- /dev/null
+++ b/Help/release/dev/ctest-run-submodule-sync.rst
@@ -0,0 +1,9 @@
+ctest-run-submodule-sync
+
+
+* The :command:`ctest_update` command now looks at the
+  :variable:`CTEST_GIT_INIT_SUBMODULES` variable to determine whether
+  submodules should be updated or not before updating.
+* The :command:`ctest_update` command will now synchronize submodules on an
+  update. Updates which add submodules or change a submodule's URL will now be
+  pulled properly.

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7f5607439ed0d1303265d3db0937e90683e698de
commit 7f5607439ed0d1303265d3db0937e90683e698de
Author: Ben Boeckel 
AuthorDate: Thu Mar 31 12:30:42 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 15:50:31 2016 -0400

cmCTestGIT: run `git submodule sync` before updating submodules

If the URL of a submodule changes upstream, the commits referenced at
the old URL may not be available and will cause an update failure.

diff --git a/Source/CTest/cmCTestGIT.cxx b/Source/CTest/cmCTestGIT.cxx
index 9ee18e6..1d6bdce 100644
--- a/Source/CTest/cmCTestGIT.cxx
+++ b/Source/CTest/cmCTestGIT.cxx
@@ -273,6 +273,7 @@ bool cmCTestGIT::UpdateImpl()
   std::string top_dir = this->FindTopDir();
   const char* git = this->CommandLineTool.c_str();
   const char* recursive = "--recursive";
+  const char* sync_recursive = "--recursive";
 
   // Git < 1.6.5 did not support submodule --recursive
   if(this->GetGitVersion() < cmCTestGITVersion(1,6,5,0))
@@ -285,6 +286,17 @@ bool cmCTestGIT::UpdateImpl()
   }
 }
 
+  // Git < 1.8.1 did not support sync --recursive
+  if(this->GetGitVersion() < cmCTestGITVersion(1,8,1,0))
+{
+sync_recursive = 0;
+// No need to require >= 1.8.1 if there are no submodules.
+if(cmSystemTools::FileExists((top_dir + "/.gitmodules").c_str()))
+  {
+  this->Log << "Git < 1.8.1 cannot synchronize submodules recursively\n";
+  }
+}
+
   OutputLogger submodule_out(this->Log, "submodule-out> ");
   OutputLogger submodule_err(this->Log, "submodule-err> ");
 
@@ -304,6 +316,16 @@ bool cmCTestGIT::UpdateImpl()
   }
 }
 
+  char const* git_submodule_sync[] = {git, "submodule", "sync",
+  sync_recursive, 0};
+  ret = this->RunChild(git_submodule_sync, _out, _err,
+   top_dir.c_str());
+
+  if (!ret)
+{
+return false;
+}
+
   char const* git_submodule[] = {git, "submodule", "update", recursive, 0};
   return this->RunChild(git_submodule, _out, _err,
 top_dir.c_str());

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=06b310b5d5d8a38fb17df02fee8df750904cfcd0
commit 06b310b5d5d8a38fb17df02fee8df750904cfcd0
Author: Ben Boeckel 
AuthorDate: Thu Mar 31 12:28:46 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 15:50:31 2016 -0400

[Cmake-commits] CMake branch, next, updated. v3.5.1-788-g3b472a4

2016-04-01 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  3b472a4ef95fa7441978a49e3d7684b165e94f99 (commit)
   via  0e44f4894f23d5eccd8d360f3420c832f9433a20 (commit)
   via  bc30f8b5e66cb9c15fd224f5e51454c0bc66c67e (commit)
  from  be3969d6403df287ba6b2c3cb00861baa9e54aea (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3b472a4ef95fa7441978a49e3d7684b165e94f99
commit 3b472a4ef95fa7441978a49e3d7684b165e94f99
Merge: be3969d 0e44f48
Author: Brad King 
AuthorDate: Fri Apr 1 15:44:59 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 15:44:59 2016 -0400

Merge topic 'fix-target-alias-in-subdir' into next

0e44f489 Rename local target lookup methods to clarify purpose
bc30f8b5 Fix lookup of an ALIAS target outside aliased target's directory 
(#16044)


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0e44f4894f23d5eccd8d360f3420c832f9433a20
commit 0e44f4894f23d5eccd8d360f3420c832f9433a20
Author: Brad King 
AuthorDate: Fri Apr 1 10:26:08 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 15:44:16 2016 -0400

Rename local target lookup methods to clarify purpose

Rename methods:

* `cmMakefile::Find{ => LocalNonAlias}Target`
* `cmLocalGenerator::Find{ => LocalNonAlias}GeneratorTarget`

These names clarify that they are for directory-local target names
and do not consider alias targets.

diff --git a/Source/cmFLTKWrapUICommand.cxx b/Source/cmFLTKWrapUICommand.cxx
index d17d664..c64e813 100644
--- a/Source/cmFLTKWrapUICommand.cxx
+++ b/Source/cmFLTKWrapUICommand.cxx
@@ -117,7 +117,7 @@ void cmFLTKWrapUICommand::FinalPass()
   // people should add the srcs to the target themselves, but the old command
   // didn't support that, so check and see if they added the files in and if
   // they didn;t then print a warning and add then anyhow
-  cmTarget* target = this->Makefile->FindTarget(this->Target);
+  cmTarget* target = this->Makefile->FindLocalNonAliasTarget(this->Target);
   if(!target)
 {
 std::string msg =
diff --git a/Source/cmInstallCommand.cxx b/Source/cmInstallCommand.cxx
index 2d78a41..7e72a8a 100644
--- a/Source/cmInstallCommand.cxx
+++ b/Source/cmInstallCommand.cxx
@@ -381,7 +381,7 @@ bool 
cmInstallCommand::HandleTargetsMode(std::vector const& args)
   return false;
   }
 // Lookup this target in the current directory.
-if(cmTarget* target=this->Makefile->FindTarget(*targetIt))
+if(cmTarget* target=this->Makefile->FindLocalNonAliasTarget(*targetIt))
   {
   // Found the target.  Check its type.
   if(target->GetType() != cmState::EXECUTABLE &&
diff --git a/Source/cmInstallTargetGenerator.cxx 
b/Source/cmInstallTargetGenerator.cxx
index 5e88fa2..b93fb8d 100644
--- a/Source/cmInstallTargetGenerator.cxx
+++ b/Source/cmInstallTargetGenerator.cxx
@@ -446,7 +446,7 @@ 
cmInstallTargetGenerator::GetInstallFilename(cmGeneratorTarget const* target,
 
 void cmInstallTargetGenerator::Compute(cmLocalGenerator* lg)
 {
-  this->Target = lg->FindGeneratorTarget(this->TargetName);
+  this->Target = lg->FindLocalNonAliasGeneratorTarget(this->TargetName);
 }
 
 //
diff --git a/Source/cmLocalGenerator.cxx b/Source/cmLocalGenerator.cxx
index 6153fbd..586e4c6 100644
--- a/Source/cmLocalGenerator.cxx
+++ b/Source/cmLocalGenerator.cxx
@@ -485,7 +485,7 @@ private:
   std::string Name;
 };
 
-cmGeneratorTarget* cmLocalGenerator::FindGeneratorTarget(
+cmGeneratorTarget* cmLocalGenerator::FindLocalNonAliasGeneratorTarget(
 const std::string& name) const
 {
   std::vector::const_iterator ti =
@@ -1828,7 +1828,7 @@ cmLocalGenerator::FindGeneratorTargetToUse(const 
std::string& name) const
 return *imported;
 }
 
-  if(cmGeneratorTarget* t = this->FindGeneratorTarget(name))
+  if(cmGeneratorTarget* t = this->FindLocalNonAliasGeneratorTarget(name))
 {
 return t;
 }
diff --git a/Source/cmLocalGenerator.h b/Source/cmLocalGenerator.h
index 68e7667..b673a85 100644
--- a/Source/cmLocalGenerator.h
+++ b/Source/cmLocalGenerator.h
@@ -129,7 +129,8 @@ public:
   void AddImportedGeneratorTarget(cmGeneratorTarget* gt);
   void AddOwnedImportedGeneratorTarget(cmGeneratorTarget* gt);
 
-  cmGeneratorTarget* FindGeneratorTarget(const std::string& name) const;
+  cmGeneratorTarget*
+FindLocalNonAliasGeneratorTarget(const std::string& name) const;
   cmGeneratorTarget* FindGeneratorTargetToUse(const std::string& name)

[Cmake-commits] CMake branch, next, updated. v3.5.1-785-gbe3969d

2016-04-01 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  be3969d6403df287ba6b2c3cb00861baa9e54aea (commit)
   via  1b5e398c957c427fcf4b32a0d19818d557c5ed2f (commit)
  from  6aadc4a25a07856a81262946b514884df95f795f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=be3969d6403df287ba6b2c3cb00861baa9e54aea
commit be3969d6403df287ba6b2c3cb00861baa9e54aea
Merge: 6aadc4a 1b5e398
Author: Brad King 
AuthorDate: Fri Apr 1 15:44:10 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 15:44:10 2016 -0400

Merge topic 'fix-target-alias-in-subdir' into next

1b5e398c fixup! Fix lookup of an ALIAS target outside aliased target's 
directory


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1b5e398c957c427fcf4b32a0d19818d557c5ed2f
commit 1b5e398c957c427fcf4b32a0d19818d557c5ed2f
Author: Brad King 
AuthorDate: Fri Apr 1 15:37:06 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 15:40:38 2016 -0400

fixup! Fix lookup of an ALIAS target outside aliased target's directory

diff --git a/Tests/AliasTarget/subdir/CMakeLists.txt 
b/Tests/AliasTarget/subdir/CMakeLists.txt
index bf9e768..05a7d86 100644
--- a/Tests/AliasTarget/subdir/CMakeLists.txt
+++ b/Tests/AliasTarget/subdir/CMakeLists.txt
@@ -4,4 +4,5 @@ add_library(Sub::tgt ALIAS tgt)
 
 # foo comes from the top-level CMakeLists.txt
 add_library(Top::foo ALIAS foo)
-get_target_property(a_prop Top::foo INTERFACE_SYSTEM_INCLUDE_DIRECTORIES)
+get_target_property(some_prop Top::foo SOME_PROP)
+target_link_libraries(tgt Top::foo)

---

Summary of changes:
 Tests/AliasTarget/subdir/CMakeLists.txt |3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)


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

[cmake-developers] [CMake 0016044]: cmake crashed with SIGSEGV in cmTarget::GetProperty()

2016-04-01 Thread Mantis Bug Tracker


The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16044 
== 
Reported By:Gianfranco
Assigned To:
== 
Project:CMake
Issue ID:   16044
Category:   CMake
Reproducibility:have not tried
Severity:   crash
Priority:   high
Status: new
== 
Date Submitted: 2016-04-01 05:57 EDT
Last Modified:  2016-04-01 05:57 EDT
== 
Summary:cmake crashed with SIGSEGV in
cmTarget::GetProperty()
Description: 
https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1564741

As reported on the Ubuntu bug, the culprit seems to be commit
a67231ac114235f0af4673235c4c07fa896c8ab6.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-01 05:57 Gianfranco 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, master, updated. v3.5.1-373-g228801b

2016-04-01 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  228801b9c823b7d992964d11a272896c4718115c (commit)
  from  e0cc8bf5d7f82cf38ef5e1a643843e244a8f98d6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=228801b9c823b7d992964d11a272896c4718115c
commit 228801b9c823b7d992964d11a272896c4718115c
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Sat Apr 2 00:01:05 2016 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Sat Apr 2 00:01:05 2016 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 0214250..46f1433 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 5)
-set(CMake_VERSION_PATCH 20160401)
+set(CMake_VERSION_PATCH 20160402)
 #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.5.1-760-ge7f0fcf

2016-04-01 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  e7f0fcf2e12610731d1b0ac34db3c0007add1f62 (commit)
   via  275a7c26d2d84893d1cde946b12dfba5839a35ed (commit)
  from  e929420e7af7d60aab7306f1af3956b31c30737c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e7f0fcf2e12610731d1b0ac34db3c0007add1f62
commit e7f0fcf2e12610731d1b0ac34db3c0007add1f62
Merge: e929420 275a7c2
Author: Brad King 
AuthorDate: Fri Apr 1 09:42:06 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 09:42:06 2016 -0400

Merge topic 'fix-target-alias-in-subdir' into next

275a7c26 Fix lookup of an ALIAS target outside aliased target's directory 
(#16044)


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=275a7c26d2d84893d1cde946b12dfba5839a35ed
commit 275a7c26d2d84893d1cde946b12dfba5839a35ed
Author: Brad King 
AuthorDate: Fri Apr 1 09:13:16 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 09:21:51 2016 -0400

Fix lookup of an ALIAS target outside aliased target's directory (#16044)

Refactoring in commit v3.5.0-rc1~272^2~11 (cmTarget: Implement ALIAS in
terms of name mapping, 2015-10-25) accidentally introduced logic that
assumes ALIAS targets always reference targets in their own directory.
Fix this and add a test case.

The fix is simply that `cmMakefile::FindTarget` should not consider
aliases.  The purpose of this method is just to look up targets local to
a directory.  Since ALIAS and normal targets share a namespace we know a
locally defined target will never collide with an ALIAS target anyway.
The method has 3 call sites, and this change is safe for all of them:

* `cmInstallCommand::HandleTargetsMode`: Rejects aliases before the call.
* `cmFLTKWrapUICommand::FinalPass`: Should never have considered aliases.
* `cmMakefile::FindTargetToUse`: Falls back to a global lookup anyway.

Reported-by: Matteo Settenvini 

diff --git a/Source/cmMakefile.cxx b/Source/cmMakefile.cxx
index 600c985..598f8c4 100644
--- a/Source/cmMakefile.cxx
+++ b/Source/cmMakefile.cxx
@@ -4058,25 +4058,13 @@ std::vector cmMakefile::GetPropertyKeys() 
const
   return this->StateSnapshot.GetDirectory().GetPropertyKeys();
 }
 
-cmTarget* cmMakefile::FindTarget(const std::string& name,
- bool excludeAliases) const
+cmTarget* cmMakefile::FindTarget(const std::string& name) const
 {
-  if (!excludeAliases)
-{
-std::map::const_iterator i =
-this->AliasTargets.find(name);
-if (i != this->AliasTargets.end())
-  {
-  cmTargets::iterator ai = this->Targets.find(i->second);
-  return >second;
-  }
-}
   cmTargets::iterator i = this->Targets.find( name );
   if ( i != this->Targets.end() )
 {
 return >second;
 }
-
   return 0;
 }
 
@@ -4247,7 +4235,7 @@ cmTarget* cmMakefile::FindTargetToUse(const std::string& 
name,
 }
 
   // Look for a target built in this directory.
-  if(cmTarget* t = this->FindTarget(name, excludeAliases))
+  if(cmTarget* t = this->FindTarget(name))
 {
 return t;
 }
diff --git a/Source/cmMakefile.h b/Source/cmMakefile.h
index 362ea75..a69c705 100644
--- a/Source/cmMakefile.h
+++ b/Source/cmMakefile.h
@@ -388,8 +388,7 @@ public:
 }
   std::vector GetImportedTargets() const;
 
-  cmTarget* FindTarget(const std::string& name,
-   bool excludeAliases = false) const;
+  cmTarget* FindTarget(const std::string& name) const;
 
   /** Find a target to use in place of the given name.  The target
   returned may be imported or built within the project.  */
diff --git a/Tests/AliasTarget/subdir/CMakeLists.txt 
b/Tests/AliasTarget/subdir/CMakeLists.txt
index 8c84aea..bf9e768 100644
--- a/Tests/AliasTarget/subdir/CMakeLists.txt
+++ b/Tests/AliasTarget/subdir/CMakeLists.txt
@@ -1,3 +1,7 @@
 
 add_library(tgt STATIC empty.cpp)
 add_library(Sub::tgt ALIAS tgt)
+
+# foo comes from the top-level CMakeLists.txt
+add_library(Top::foo ALIAS foo)
+get_target_property(a_prop Top::foo INTERFACE_SYSTEM_INCLUDE_DIRECTORIES)

---

Summary of changes:
 Source/cmMakefile.cxx   |   16 ++--
 Source/cmMakefile.h |3 +--
 Tests/AliasTarget/subdir/CMakeLists.txt |4 
 3 files changed, 7 insertions(+), 16 deletions(-)


hooks/post-receive
-- 
CMake

[Cmake-commits] CMake branch, next, updated. v3.5.1-762-gefc7554

2016-04-01 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  efc7554589418158e24828252816f900fae861b8 (commit)
   via  e2ef106d0232e1f5be2df20e0829ad57f1259955 (commit)
  from  e7f0fcf2e12610731d1b0ac34db3c0007add1f62 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=efc7554589418158e24828252816f900fae861b8
commit efc7554589418158e24828252816f900fae861b8
Merge: e7f0fcf e2ef106
Author: Brad King 
AuthorDate: Fri Apr 1 09:51:59 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 09:51:59 2016 -0400

Merge topic 'cpack-rpm-external-symlink-handling' into next

e2ef106d fixup! CPack/RPM external symlink handling


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e2ef106d0232e1f5be2df20e0829ad57f1259955
commit e2ef106d0232e1f5be2df20e0829ad57f1259955
Author: Brad King 
AuthorDate: Fri Apr 1 09:48:11 2016 -0400
Commit: Brad King 
CommitDate: Fri Apr 1 09:48:11 2016 -0400

fixup! CPack/RPM external symlink handling

diff --git a/Help/release/dev/cpack-rpm-external-symlink-handling.rst 
b/Help/release/dev/cpack-rpm-external-symlink-handling.rst
index d9a3d8c..ff74e1d 100644
--- a/Help/release/dev/cpack-rpm-external-symlink-handling.rst
+++ b/Help/release/dev/cpack-rpm-external-symlink-handling.rst
@@ -1,5 +1,5 @@
 cpack-rpm-external-symlink-handling
-
+---
 
 * The "CPackRPM" module learned how to correctly handle symlinks
   that are pointing outside generated packages.

---

Summary of changes:
 Help/release/dev/cpack-rpm-external-symlink-handling.rst |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.5.1-764-g5b14667

2016-04-01 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  5b146672d69eb0fc001d468fb82699a89f73cf3c (commit)
   via  eae4eef0c48188027b5c25657054b12b6b301c85 (commit)
  from  efc7554589418158e24828252816f900fae861b8 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5b146672d69eb0fc001d468fb82699a89f73cf3c
commit 5b146672d69eb0fc001d468fb82699a89f73cf3c
Merge: efc7554 eae4eef
Author: Brad King 
AuthorDate: Fri Apr 1 09:52:17 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 09:52:17 2016 -0400

Merge topic 'cpack-rpm-external-symlink-handling' into next

eae4eef0 CPack/RPM external symlink handling


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=eae4eef0c48188027b5c25657054b12b6b301c85
commit eae4eef0c48188027b5c25657054b12b6b301c85
Author: Domen Vrankar 
AuthorDate: Thu Mar 31 07:48:38 2016 +0200
Commit: Brad King 
CommitDate: Fri Apr 1 09:52:04 2016 -0400

CPack/RPM external symlink handling

Symbolic links that point to external
location no longer cause cmake to fail
with string out of bounds error but
are instead packaged as non relocatable
symlinks and print out a warning message.

diff --git a/Help/release/dev/cpack-rpm-external-symlink-handling.rst 
b/Help/release/dev/cpack-rpm-external-symlink-handling.rst
new file mode 100644
index 000..ff74e1d
--- /dev/null
+++ b/Help/release/dev/cpack-rpm-external-symlink-handling.rst
@@ -0,0 +1,5 @@
+cpack-rpm-external-symlink-handling
+---
+
+* The "CPackRPM" module learned how to correctly handle symlinks
+  that are pointing outside generated packages.
diff --git a/Modules/CPackRPM.cmake b/Modules/CPackRPM.cmake
index ae51dc1..713b938 100644
--- a/Modules/CPackRPM.cmake
+++ b/Modules/CPackRPM.cmake
@@ -599,9 +599,10 @@
 # while determining if symlink should be either created or present in a
 # post install script - depending on relocation paths.
 #
-# Currenty there are a few limitations though:
+# Symbolic links that point to locations outside packaging path produce a
+# warning and are treated as non relocatable permanent symbolic links.
 #
-# * Only symbolic links with relative path can be packaged.
+# Currenty there are a few limitations though:
 #
 # * For component based packaging component interdependency is not checked
 #   when processing symbolic links. Symbolic links pointing to content of
@@ -1068,13 +1069,28 @@ function(cpack_rpm_prepare_install_files 
INSTALL_FILES_LIST WDIR PACKAGE_PREFIXE
   get_filename_component(SYMLINK_POINT_ 
"${SYMLINK_LOCATION_}/${SYMLINK_POINT_}" ABSOLUTE)
 endif()
 
-string(SUBSTRING "${SYMLINK_POINT_}" ${WDR_LEN_} -1 SYMLINK_POINT_WD_)
+# recalculate path length after conversion to canonical form
+string(LENGTH "${SYMLINK_POINT_}" SYMLINK_POINT_LENGTH_)
 
-cpack_rpm_symlink_get_relocation_prefixes("${F}" "${PACKAGE_PREFIXES}" 
"SYMLINK_RELOCATIONS")
-cpack_rpm_symlink_get_relocation_prefixes("${SYMLINK_POINT_WD_}" 
"${PACKAGE_PREFIXES}" "POINT_RELOCATIONS")
+if(SYMLINK_POINT_ MATCHES "${WDIR}/.*")
+  # only symlinks that are pointing inside the packaging structure 
should be checked for relocation
+  string(SUBSTRING "${SYMLINK_POINT_}" ${WDR_LEN_} -1 
SYMLINK_POINT_WD_)
+  cpack_rpm_symlink_get_relocation_prefixes("${F}" 
"${PACKAGE_PREFIXES}" "SYMLINK_RELOCATIONS")
+  cpack_rpm_symlink_get_relocation_prefixes("${SYMLINK_POINT_WD_}" 
"${PACKAGE_PREFIXES}" "POINT_RELOCATIONS")
 
-list(LENGTH SYMLINK_RELOCATIONS SYMLINK_RELOCATIONS_COUNT)
-list(LENGTH POINT_RELOCATIONS POINT_RELOCATIONS_COUNT)
+  list(LENGTH SYMLINK_RELOCATIONS SYMLINK_RELOCATIONS_COUNT)
+  list(LENGTH POINT_RELOCATIONS POINT_RELOCATIONS_COUNT)
+else()
+  # location pointed to is ouside WDR so it should be treated as a 
permanent symlink
+  set(SYMLINK_POINT_WD_ "${SYMLINK_POINT_}")
+
+  unset(SYMLINK_RELOCATIONS)
+  unset(POINT_RELOCATIONS)
+  unset(SYMLINK_RELOCATIONS_COUNT)
+  unset(POINT_RELOCATIONS_COUNT)
+
+  message(AUTHOR_WARNING "CPackRPM:Warning: Symbolic link '${F}' 
points to location that is outside packaging path! Link will possibly not be 
relocatable.")
+endif()
 
 if(SYMLINK_RELOCATIONS_COUNT AND POINT_RELOCATIONS_COUNT)
   # find matching
diff --git a/Tests/CPackComponentsForAll/CMakeLists.txt

[Cmake-commits] CMake branch, next, updated. v3.5.1-758-ge929420

2016-04-01 Thread Zack Galbreath

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  e929420e7af7d60aab7306f1af3956b31c30737c (commit)
   via  83c6183c1aabd0ac3309d87c8c10678b55c2e489 (commit)
   via  332272e29b33e334b01790fa16d2451d69749c5b (commit)
  from  58a4efca93fa9255a920a0bfa0890d3858acf656 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e929420e7af7d60aab7306f1af3956b31c30737c
commit e929420e7af7d60aab7306f1af3956b31c30737c
Merge: 58a4efc 83c6183
Author: Zack Galbreath 
AuthorDate: Fri Apr 1 08:43:51 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Fri Apr 1 08:43:51 2016 -0400

Merge topic 'branch_coverage_glob' into next

83c6183c CTestCoverageCollectGCOV: Improve documentation
332272e2 CTestCoverageCollectGCOV: Honor CTEST_EXTRA_COVERAGE_GLOB


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=83c6183c1aabd0ac3309d87c8c10678b55c2e489
commit 83c6183c1aabd0ac3309d87c8c10678b55c2e489
Author: Zack Galbreath 
AuthorDate: Thu Mar 31 14:17:03 2016 -0400
Commit: Zack Galbreath 
CommitDate: Thu Mar 31 14:17:03 2016 -0400

CTestCoverageCollectGCOV: Improve documentation

Clean up prose and mention support for CTEST_EXTRA_COVERAGE_GLOB.

diff --git a/Modules/CTestCoverageCollectGCOV.cmake 
b/Modules/CTestCoverageCollectGCOV.cmake
index 493c490..7d387a5 100644
--- a/Modules/CTestCoverageCollectGCOV.cmake
+++ b/Modules/CTestCoverageCollectGCOV.cmake
@@ -2,14 +2,19 @@
 # CTestCoverageCollectGCOV
 # 
 #
-# This module provides the function ``ctest_coverage_collect_gcov``.
-# The function will run gcov on the .gcda files in a binary tree and then
-# package all of the .gcov files into a tar file with a data.json that
-# contains the source and build directories for CDash to use in parsing
-# the coverage data. In addtion the Labels.json files for targets that
-# have coverage information are also put in the tar file for CDash to
-# asign the correct labels. This file can be sent to a CDash server for
-# display with the
+# This module provides the ``ctest_coverage_collect_gcov`` function.
+#
+# This function runs gcov on all .gcda files found in the binary tree
+# and packages the resulting .gcov files into a tar file.
+# This tarball also contains the following:
+#
+# * *data.json* defines the source and build directories for use by CDash.
+# * *Labels.json* indicates any :prop_sf:`LABELS` that have been set on the
+#   source files.
+# * The *uncovered* directory holds any uncovered files found by
+#   :variable:`CTEST_EXTRA_COVERAGE_GLOB`.
+#
+# After generating this tar file, it can be sent to CDash for display with the
 # :command:`ctest_submit(CDASH_UPLOAD)` command.
 #
 # .. command:: cdash_coverage_collect_gcov

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=332272e29b33e334b01790fa16d2451d69749c5b
commit 332272e29b33e334b01790fa16d2451d69749c5b
Author: Zack Galbreath 
AuthorDate: Wed Mar 30 10:31:25 2016 -0400
Commit: Zack Galbreath 
CommitDate: Wed Mar 30 10:54:49 2016 -0400

CTestCoverageCollectGCOV: Honor CTEST_EXTRA_COVERAGE_GLOB

Teach CTestCoverageCollectGCOV to honor the
CTEST_EXTRA_COVERAGE_GLOB variable.  When this variable is set,
this module will glob for matching source files that were not
covered and include them in the resulting tar file.

diff --git a/Modules/CTestCoverageCollectGCOV.cmake 
b/Modules/CTestCoverageCollectGCOV.cmake
index f31e432..493c490 100644
--- a/Modules/CTestCoverageCollectGCOV.cmake
+++ b/Modules/CTestCoverageCollectGCOV.cmake
@@ -172,6 +172,21 @@ function(ctest_coverage_collect_gcov)
   set(unfiltered_gcov_files)
   file(GLOB_RECURSE unfiltered_gcov_files RELATIVE ${binary_dir} 
"${coverage_dir}/*.gcov")
 
+  # if CTEST_EXTRA_COVERAGE_GLOB was specified we search for files
+  # that might be uncovered
+  if (DEFINED CTEST_EXTRA_COVERAGE_GLOB)
+set(uncovered_files)
+foreach(search_entry IN LISTS CTEST_EXTRA_COVERAGE_GLOB)
+  if(NOT GCOV_QUIET)
+message("Add coverage glob: ${search_entry}")
+  endif()
+  file(GLOB_RECURSE matching_files "${source_dir}/${search_entry}")
+  if (matching_files)
+list(APPEND uncovered_files "${matching_files}")
+  endif()
+endforeach()
+  endif()
+
   set(gcov_files)
   foreach(gcov_file ${unfiltered_gcov_files})
 file(STRINGS ${binary_dir}/${gcov_file} first_line LIMIT_COUNT 1 ENCODING 
UTF-8)
@@ -195,20 +210,45 @@

[cmake-developers] [PATCH] language detection in FindBLAS and FindLAPACK (#0016039)

2016-04-01 Thread Melven.Roehrig-Zoellner

Patch for a problem with find_package(BLAS/LAPACK) on Windows for pure Fortran 
projects reported by me in https://cmake.org/Bug/view.php?id=16039.

Regards,
Melven

--
Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR)
German Aerospace Center
Simulation and Software Technology | Linder Hoehe | 51147 Cologne | Germany

Melven Röhrig-Zöllner 
Telephone +492203 / 601 - 2574
www.DLR.de




0001-Fix-for-pure-Fortran-projects-with-BLAS-LAPACK-00160.patch
Description: 0001-Fix-for-pure-Fortran-projects-with-BLAS-LAPACK-00160.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

[cmake-developers] [CMake 0016046]: GHS Multi Generator: duplicate object file names

2016-04-01 Thread Mantis Bug Tracker


The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16046 
== 
Reported By:stw_sesa
Assigned To:
== 
Project:CMake
Issue ID:   16046
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-01 08:56 EDT
Last Modified:  2016-04-01 08:56 EDT
== 
Summary:GHS Multi Generator: duplicate object file names
Description: 
When a target contains multiple files with the same name (in different
(sub)folders) the generated object files will have the same names too. Normally
this isn't a problem at all, but for GHS MULTI it is as the duplicates are
ignored.

Steps to Reproduce: 
Create a project with a target containing at least two files with the same name
like this:
add_library(libdemo test.c subfolder/test.c )

Expected result:
The library contains both test.o and subfolder/test.o

Actual result:
Only one of these source files is compiled and archived in the library due to
their name equality.


A sample project is attached, that will build successfully using other C project
generators (e.g Makefile), but won't when using GHS MULTI toolchain.

Additional Information: 
This could also be either a bug in MULTI Project Manager or intended behaviour.
However, from the CMake perspective the results are unexpected.

A workaround for the generator would be to rename the generated object file by
emitting a unique object file name with the option "-o .o" in the
generated project files (.gpj).

Is there any CMake workaround? (which doesn't require changing CMake itself)
Maybe there is an project file option that changes that behaviour?

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-01 08:56 stw_sesa   New Issue
2016-04-01 08:56 stw_sesa   File Added: dup_objname_test.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

41 matches

Mail list logo