[Cmake-commits] CMake branch, master, updated. v3.10.2-881-g1345bdf

[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  1345bdf1b6520a2f0c9891ad3c6fee00a6a5f18d (commit)
  from  9c52b587b6dfa54266bcebbe7e111d7dde437a75 (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=1345bdf1b6520a2f0c9891ad3c6fee00a6a5f18d
commit 1345bdf1b6520a2f0c9891ad3c6fee00a6a5f18d
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Wed Jan 24 00:02:43 2018 -0500
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Wed Jan 24 00:02:43 2018 -0500

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 2bd81d1..bab642b 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 10)
-set(CMake_VERSION_PATCH 20180123)
+set(CMake_VERSION_PATCH 20180124)
 #set(CMake_VERSION_RC 1)

---

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


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

[CMake] (no subject)

[Budi]

How to set up  environment to bulid along with CPPAN ( I want to build
tesseract)
-- 

Powered by www.kitware.com

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

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

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

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

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[CMake] Confusion with range-based FOREACH logic

[Robert Dailey]

I am doing the following:

```
set( CS_THIRD_PARTY_REFERENCES
Iconic.Zip ${CMAKE_CURRENT_SOURCE_DIR}/DotNetZip/Iconic.Zip.dll
)

if( CS_THIRD_PARTY_REFERENCES )
list( LENGTH CS_THIRD_PARTY_REFERENCES len )
message( STATUS "len: ${len}" )
foreach( i RANGE 0 ${len} 2 )
message( STATUS "i: ${i}" )
list( GET CS_THIRD_PARTY_REFERENCES ${i} assembly_name )
math( EXPR i "${i}+1" )
list( GET CS_THIRD_PARTY_REFERENCES ${i} assembly_path )
set_property( TARGET ${target_name} PROPERTY
VS_DOTNET_REFERENCE_${assembly_name} ${assembly_path}
)
message( STATUS "i: ${i}" )
message( STATUS "assembly_name: ${assembly_name}" )
message( STATUS "assembly_path: ${assembly_path}" )
endforeach()
endif()
```

I am finding that the foreach() loops 2 times when ${len} is 2. What I
expect during the 2nd iteration is that it does ${i}+STEP (0+2) which
would equal 2, and so long as 2<${len} (2<2), then it would continue
to iterate. In this case, it should stop after the first iteration.
I'm thinking that this should work like a C++ for loop. Is this not
the case? How should I be iterating over a list of 2 times at a time?
-- 

Powered by www.kitware.com

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

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

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

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

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] Server handshake with only build directory

[Rich Chiodo via cmake-developers]

Tobias, can you make sure it still supports passing the source directory too?

Otherwise we’ll have to have version dependent arguments that we pass to CMake 
server.

From: Isaiah Norton [mailto:isaiah.nor...@gmail.com]
Sent: Tuesday, January 23, 2018 7:16 AM
To: Brad King 
Cc: Tobias Hunger ; Rich Chiodo 
; CMake Developers 
Subject: Re: [cmake-developers] Server handshake with only build directory

> Any objections from the core team about enabling server-mode with a
> build directory only? I can send in a patch, it is simple to add this.

Fine with me.

Awesome, thanks. Please cc me (@ihnorton).

Isaiah

On Tue, Jan 23, 2018 at 6:40 AM, Brad King 
> wrote:
On 01/23/2018 04:55 AM, Tobias Hunger wrote:
> Any objections from the core team about enabling server-mode with a
> build directory only? I can send in a patch, it is simple to add this.

Fine with me.

This should be allowed only when the build tree already exists.

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:
https://cmake.org/mailman/listinfo/cmake-developers

-- 

Powered by www.kitware.com

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

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

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

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

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers

Re: [CMake] [cmake] [RFC] rewriting FindMKL

[Sik]

I made a PR based on your comment, is this what you were referring to?
https://github.com/openmeeg/findmkl_cmake/pull/8


On Tue, Jan 23, 2018 at 11:25 AM Luis Caro Campos 
wrote:

> As a comment, would it be possible to include imported targets that
> encapsulate include dirs, linker arguments and compile definitions? I would
> say the CMake community is trying to move away from the old-style find
> packages that define variables instead of targets.
>
> Regards,
> Luis
>
> On Mon, Jan 22, 2018 at 3:16 PM, Sik  wrote:
>
>> Hello CMake users and devs,
>>
>> In openmeeg we are reviewing our MKL package finder to make it more
>> maintainable for ourselves and others who had adopted our solution.
>> Therefore I'm writing you requesting comments and feedback so that is
>> useful for everyone.
>>
>> Here is the project we have set up in order to test it. It has a simple
>> example using MKL and CI for different scenarios.
>>
>> https://github.com/openmeeg/findmkl_cmake
>>
>> Thx
>>
>> --
>>
>> Powered by www.kitware.com
>>
>> Please keep messages on-topic and check the CMake FAQ at:
>> http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Kitware offers various services to support the CMake community. For more
>> information on each offering, please visit:
>>
>> CMake Support: http://cmake.org/cmake/help/support.html
>> CMake Consulting: http://cmake.org/cmake/help/consulting.html
>> CMake Training Courses: http://cmake.org/cmake/help/training.html
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Follow this link to subscribe/unsubscribe:
>> https://cmake.org/mailman/listinfo/cmake
>>
>> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
>
-- 

Powered by www.kitware.com

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

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

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

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

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] Server handshake with only build directory

[Isaiah Norton]

>
> > Any objections from the core team about enabling server-mode with a
> > build directory only? I can send in a patch, it is simple to add this.
>
> Fine with me.
>

Awesome, thanks. Please cc me (@ihnorton).

Isaiah

On Tue, Jan 23, 2018 at 6:40 AM, Brad King  wrote:

> On 01/23/2018 04:55 AM, Tobias Hunger wrote:
> > Any objections from the core team about enabling server-mode with a
> > build directory only? I can send in a patch, it is simple to add this.
>
> Fine with me.
>
> This should be allowed only when the build tree already exists.
>
> 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:
> https://cmake.org/mailman/listinfo/cmake-developers
>
-- 

Powered by www.kitware.com

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

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

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

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

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers

[Cmake-commits] CMake branch, master, updated. v3.10.2-880-g9c52b58

[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  9c52b587b6dfa54266bcebbe7e111d7dde437a75 (commit)
   via  ce863c17d08e6631c4a194fc3f9fb3f63ea65d11 (commit)
   via  5cbf3653ff25a42577e9473b447a4b9afb128875 (commit)
   via  51caac6958c9adb31dae4c2a61bd0bfce9e45a23 (commit)
  from  2c6f5baaa7e101cdd3e5769a3fd8d49d0501b8e6 (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=9c52b587b6dfa54266bcebbe7e111d7dde437a75
commit 9c52b587b6dfa54266bcebbe7e111d7dde437a75
Merge: ce863c1 5cbf365
Author: Brad King 
AuthorDate: Tue Jan 23 14:35:46 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 23 09:36:09 2018 -0500

Merge topic 'recognize-versioned-shared-libraries'

5cbf3653 cmComputeLinkInformation: Better RPATH detection for versioned 
libraries.

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ce863c17d08e6631c4a194fc3f9fb3f63ea65d11
commit ce863c17d08e6631c4a194fc3f9fb3f63ea65d11
Merge: 2c6f5ba 51caac6
Author: Brad King 
AuthorDate: Tue Jan 23 14:35:38 2018 +
Commit: Kitware Robot 
CommitDate: Tue Jan 23 09:35:43 2018 -0500

Merge topic 'feature-codelite-fortran'

51caac69 CodeLite: Better support for Fortran and Windows

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5cbf3653ff25a42577e9473b447a4b9afb128875
commit 5cbf3653ff25a42577e9473b447a4b9afb128875
Author: Byoungchan Lee 
AuthorDate: Tue Jan 23 01:22:15 2018 +0900
Commit: Byoungchan Lee 
CommitDate: Tue Jan 23 01:22:15 2018 +0900

cmComputeLinkInformation: Better RPATH detection for versioned libraries.

Some libraries uses the non-conventional SONAME scheme like
`libssl.so.1.1` or `libboost_system.so.1.64.0`, but CMake didn't count on
such versioned libraries. This commit modify regular expressions to match
relaxed format of shared library name for determining various linker 
options,
especially `RPATH`.
Note that support for one component has been available since v2.8.12.

Fixes: #15938

diff --git a/Source/cmComputeLinkInformation.cxx 
b/Source/cmComputeLinkInformation.cxx
index fb13a58..18cca5a 100644
--- a/Source/cmComputeLinkInformation.cxx
+++ b/Source/cmComputeLinkInformation.cxx
@@ -913,11 +913,9 @@ std::string cmComputeLinkInformation::CreateExtensionRegex(
   // Finish the list.
   libext += ")";
 
-  // Add an optional OpenBSD version component.
-  if (this->OpenBSD) {
-libext += "(\\.[0-9]+\\.[0-9]+)?";
-  } else if (type == LinkShared) {
-libext += "(\\.[0-9]+)?";
+  // Add an optional OpenBSD-style version or major.minor.version component.
+  if (this->OpenBSD || type == LinkShared) {
+libext += "(\\.[0-9]+)*";
   }
 
   libext += "$";

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=51caac6958c9adb31dae4c2a61bd0bfce9e45a23
commit 51caac6958c9adb31dae4c2a61bd0bfce9e45a23
Author: Tobias R. Henle 
AuthorDate: Fri Jan 19 22:41:54 2018 +0100
Commit: Tobias R. Henle 
CommitDate: Fri Jan 19 22:41:54 2018 +0100

CodeLite: Better support for Fortran and Windows

Fortran source files are added to the src folder of CodeLite projects and
the "Compile Single File" command uses "$(CurrentFileFullName)"
instead of "$(CurrentFileName)" with the correct filename extension
for object files on windows now.

diff --git a/Source/cmExtraCodeLiteGenerator.cxx 
b/Source/cmExtraCodeLiteGenerator.cxx
index 4958007..fad0723 100644
--- a/Source/cmExtraCodeLiteGenerator.cxx
+++ b/Source/cmExtraCodeLiteGenerator.cxx
@@ -198,8 +198,6 @@ std::string cmExtraCodeLiteGenerator::CollectSourceFiles(
   std::map& cFiles,
   std::set& otherFiles)
 {
-  auto cm = this->GlobalGenerator->GetCMakeInstance();
-
   std::string projectType;
   switch (gt->GetType()) {
 case cmStateEnums::EXECUTABLE: {
@@ -227,19 +225,18 @@ std::string cmExtraCodeLiteGenerator::CollectSourceFiles(
   gt->GetSourceFiles(sources,
  makefile->GetSafeDefinition("CMAKE_BUILD_TYPE"));
   for (cmSourceFile* s : sources) {
-// check whether it is a C/C++/CUDA implementation file
-bool isCFile = false;
-std::string lang = s->GetLanguage();
-if (lang == "C" || lang == "CXX" || lang == "CUDA") {
-  std::string const& 

Re: [cmake-developers] Server handshake with only build directory

[Brad King]

On 01/23/2018 04:55 AM, Tobias Hunger wrote:
> Any objections from the core team about enabling server-mode with a
> build directory only? I can send in a patch, it is simple to add this.

Fine with me.

This should be allowed only when the build tree already exists.

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:
https://cmake.org/mailman/listinfo/cmake-developers

Re: [CMake] [cmake] [RFC] rewriting FindMKL

[Luis Caro Campos]

As a comment, would it be possible to include imported targets that
encapsulate include dirs, linker arguments and compile definitions? I would
say the CMake community is trying to move away from the old-style find
packages that define variables instead of targets.

Regards,
Luis

On Mon, Jan 22, 2018 at 3:16 PM, Sik  wrote:

> Hello CMake users and devs,
>
> In openmeeg we are reviewing our MKL package finder to make it more
> maintainable for ourselves and others who had adopted our solution.
> Therefore I'm writing you requesting comments and feedback so that is
> useful for everyone.
>
> Here is the project we have set up in order to test it. It has a simple
> example using MKL and CI for different scenarios.
>
> https://github.com/openmeeg/findmkl_cmake
>
> Thx
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
>
>
-- 

Powered by www.kitware.com

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

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

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

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

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [cmake-developers] Server handshake with only build directory

[Tobias Hunger]

Hi Rich,

On Mon, Jan 22, 2018 at 5:48 PM, Rich Chiodo  wrote:
> If you have the build directory, can’t you just parse the CmakeCache.txt?
> CMAKE_HOME_DIRECTORY in the cache is the source folder. Seems easier than
> writing something to talk to CMake server.

Sure, but part of the reason to have server-mode is to get rid of
clutches like that.

If nobody objects, then I can make server-mode start with a build
directory only. I had that implemented at some point, but removed it
as part of the review process.

Any objections from the core team about enabling server-mode with a
build directory only? I can send in a patch, it is simple to add this.

Best Regards,
Tobias
-- 

Powered by www.kitware.com

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

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

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

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

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers

Re: [CMake] [cmake] [RFC] rewriting FindMKL

[Kai Wolf]

I've fixed some (mentioned) issues already and opened up a PR on
GitHub. You might want to check that out, otherwise I'll just delete
my PR.


2018-01-22 22:20 GMT+01:00 Alexander Neundorf :
> On 2018 M01 22, Mon 15:16:50 CET Sik wrote:
>> Hello CMake users and devs,
>>
>> In openmeeg we are reviewing our MKL package finder to make it more
>> maintainable for ourselves and others who had adopted our solution.
>> Therefore I'm writing you requesting comments and feedback so that is
>> useful for everyone.
>>
>> Here is the project we have set up in order to test it. It has a simple
>> example using MKL and CI for different scenarios.
>>
>> https://github.com/openmeeg/findmkl_cmake
>
> that's quite a lot of stuff, I'll try to test itin the next days.
>
> Just a few quick comments:
>
> The MESSAGE() in line 39 is ALL_UPPERCASE.
>
> MKL_ROOT_DIR from line 31 is put into the cache, reusing the same variable
> name in line 35 probably works, but the interaction between cache- and non-
> cache variables is somewhat complicated, so I would recommend to use different
> names.
>
> When searching mkl_cblas.h in line 31, in case the Intel compiler is used, the
> install directory of CMAKE_CXX_COMPILER could be used in some way as a hint to
> help finding MKL.
>
> I don't like the error message in line 39, I usually prefer using
> CMAKE_PREFIX_PATH.
>
> Lines 87 to 95 are not correctly indented, also lines 105 to 112.
>
> Is BLA_STATIC in line 117 correct, or is this a typo ?
>
> Alex
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

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

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

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

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

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake