[Cmake-commits] CMake branch, master, updated. v3.9.2-780-ga763cff

[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  a763cffd6b65bbe5572527e39969981bf31d5aca (commit)
  from  3ea87bce69d1b6120b227fed3838f1bc9ab45db1 (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=a763cffd6b65bbe5572527e39969981bf31d5aca
commit a763cffd6b65bbe5572527e39969981bf31d5aca
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Wed Sep 13 00:01:03 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Wed Sep 13 00:01:03 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 0dd1651..9c1da41 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 9)
-set(CMake_VERSION_PATCH 20170912)
+set(CMake_VERSION_PATCH 20170913)
 #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

Re: [CMake] cmake install

[Adam Getchell]

Thanks for the catch, sudo cmake --build . --target install &> install.log 
worked.

Yes, I plan to use a package manager like Conan or conda rather than the 
horrible tangle of scripts I have now for Travis and Appveyor, just have a few 
other things to do first. ;-)

-- 
Adam Getchell
https://keybase.io/adamgetchell

> On Sep 10, 2017, at 5:42 AM, Michael Jackson  
> wrote:
> 
> You should explicitly set the installation location of your package using 
> –DCMAKE_INSTALL_PREFIX=/xxx///xxx during the initial invocation of 
> cmake.
>  
> This should be set to a location you KNOW you have normal write access to. 
> Once this is set then you will no longer need to use “sudo” to run the 
> commands and all _should_ work correctly. This is what we do on our dashboard 
> builds.
>  
> -- 
> Mike Jackson  
>  
>  
> From: CMake  on behalf of Adam Getchell 
> 
> Date: Friday, September 8, 2017 at 9:20 PM
> To: Craig Scott 
> Cc: CMake 
> Subject: Re: [CMake] cmake install
>  
>  
>> On Sep 8, 2017, at 6:11 PM, Craig Scott > > wrote:
>>>  
>>> I tried:
>>>  
>>> # cmake -G Ninja .
>>> # cmake --build .
>>> # cmake --build . --target install
>>  
>> This should be correct. Did this not work for you?
>  
> No.
>  
> https://travis-ci.org/acgetchell/CDT-plusplus/jobs/273498700 
> 
>  
> Thanks for your help.
>  
>>  
>>  
>>> If its somewhere in the manual, I’d appreciate pointers.
>>  
>> Which part were you looking for? The use of --target is documented as part 
>> of the Build Tool Mode 
>> 
>>  section, but it seems you've already figured out that part. There's nothing 
>> technically special about the install target as far as I'm aware, you should 
>> be able to refer to it as a build target like you've done above.
>>  
>>  
>> Craig Scott
>> Melbourne, Australia
>> https://crascit.com  
> -- 
> Adam Getchell
> https://keybase.io/adamgetchell 
> 
> -- Powered by www.kitware.com  Please keep messages 
> on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ 
>  Kitware offers various services to 
> support the CMake community. For more information on each offering, please 
> visit: CMake Support: http://cmake.org/cmake/help/support.html 
>  CMake Consulting: 
> http://cmake.org/cmake/help/consulting.html 
>  CMake Training Courses: 
> http://cmake.org/cmake/help/training.html 
>  Visit other Kitware open-source 
> projects at http://www.kitware.com/opensource/opensource.html 
>  Follow this link to 
> subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake 
> 
-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] debugging CMAKE_PREFIX_PATH

[Patrick Welche]

On Tue, Sep 12, 2017 at 11:52:00PM +0100, Patrick Welche wrote:
> Problematic (scribus) CMakeLists.txt:
> 
>   set(CMAKE_PREFIX_PATH "${QT_PREFIX}/lib/cmake")
>   set(CMAKE_INCLUDE_CURRENT_DIR ON)
>   find_package(Qt5Core ${QT_MIN_VERSION} REQUIRED)
> 
> On Tue, Sep 12, 2017 at 04:37:08PM +0300, Konstantin Tokarev wrote:
> > What actually happens here: rogue CMake project overwrites
> > user-supplied CMAKE_PREFIX_PATH with its own value, so it is
> > disregarded.
> >
> > As a workaround (without changing project), you can pass
> > -DQt5Core_DIR=/usr/pkg/qt5/lib/cmake/Qt5Core
> 
> Thank you! I had found the workaround, but the list of Qt packages
> was becoming rather long. Getting rid of the CMAKE_PREFIX_PATH
> over-ride fixed things, but then revealed a further problem:
> 
>   set(CMAKE_MODULE_PATH "${CMAKE_SOURCE_DIR}/cmake/modules")
>   set(CAIRO_DIR ${CMAKE_MODULE_PATH})
>   find_package(CAIRO REQUIRED)
> 
>   $ ls -1 CMakeLists.txt cmake/modules/CAIROConfig.cmake
>   CMakeLists.txt
>   cmake/modules/CAIROConfig.cmake

Actually, there is more to this: the build system alters the above to:

set (CMAKE_MODULE_PATH 
"/usr/obj/pkgsrc/print/scribus5/work.x86_64/.buildlink/cmake-Modules" 
"${CMAKE_SOURCE_DIR}/cmake/modules")

AFAICT CMAKE_MODULE_PATH should end up as dir1;dir2, but the CMakeCache.txt
says:

CMAKE_MODULE_PATH:PATH=/usr/obj/pkgsrc/print/scribus5/work.x86_64/.buildlink/cmake-Modules

so only one argument to set() made it?

Cheers,

Patrick
-- 

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] debugging CMAKE_PREFIX_PATH

[Patrick Welche]

Problematic (scribus) CMakeLists.txt:

  set(CMAKE_PREFIX_PATH "${QT_PREFIX}/lib/cmake")
  set(CMAKE_INCLUDE_CURRENT_DIR ON)
  find_package(Qt5Core ${QT_MIN_VERSION} REQUIRED)

On Tue, Sep 12, 2017 at 04:37:08PM +0300, Konstantin Tokarev wrote:
> What actually happens here: rogue CMake project overwrites
> user-supplied CMAKE_PREFIX_PATH with its own value, so it is
> disregarded.
>
> As a workaround (without changing project), you can pass
> -DQt5Core_DIR=/usr/pkg/qt5/lib/cmake/Qt5Core

Thank you! I had found the workaround, but the list of Qt packages
was becoming rather long. Getting rid of the CMAKE_PREFIX_PATH
over-ride fixed things, but then revealed a further problem:

  set(CMAKE_MODULE_PATH "${CMAKE_SOURCE_DIR}/cmake/modules")
  set(CAIRO_DIR ${CMAKE_MODULE_PATH})
  find_package(CAIRO REQUIRED)

  $ ls -1 CMakeLists.txt cmake/modules/CAIROConfig.cmake
  CMakeLists.txt
  cmake/modules/CAIROConfig.cmake

Any thoughts on this variation on the theme?


Cheers,

Patrick
-- 

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] project() with ASM fails with MSVC 19

[Robert Dailey]

Also, I am using the "Visual Studio 15 2017" generator with no other
options (generating through cmake-gui on Windows)

On Tue, Sep 12, 2017 at 1:33 PM, Robert Dailey  wrote:
> Using CMake 3.9, I do this:
>
> cmake_minimum_required(VERSION 3.9)
> project(libpng VERSION 1.6.33 LANGUAGES ASM C)
>
> I get the following error:
>
> -- The ASM compiler identification is unknown
> -- Didn't find assembler
> -- The C compiler identification is MSVC 19.11.25507.1
> CMake Error at CMakeLists.txt:16 (project):
> No CMAKE_ASM_COMPILER could be found.
>
>
> Why doesn't this work?
-- 

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] project() with ASM fails with MSVC 19

[Robert Dailey]

Using CMake 3.9, I do this:

cmake_minimum_required(VERSION 3.9)
project(libpng VERSION 1.6.33 LANGUAGES ASM C)

I get the following error:

-- The ASM compiler identification is unknown
-- Didn't find assembler
-- The C compiler identification is MSVC 19.11.25507.1
CMake Error at CMakeLists.txt:16 (project):
No CMAKE_ASM_COMPILER could be found.


Why doesn't this work?
-- 

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] Adding compile and build type tests to CMake/CTest

[Robert Ramey]

On 9/4/17 6:40 AM, Edward Diener wrote:
Boost Build has tests for running an application successfully or not, 
for compiling one or more source files successfully or not, and for 
building one or more source files into an exe or not. These tests in 
Boost Build are the run/run-fail, compile/compile-fail, and 
link/link-fail rules.


CMake/CTest has the exact equivalent to the run/run-fail rule in its 
add_test framework, but there is not add_test equivalent to the other 
two sets of rules. It sure would be nice, when Boost transitions to 
using CMake/CTest instead of Boost Build, if CMake/CTest had the 
equivalent of the other two sets of types of test in its add_test 
framework.


Is there any consensus that these other two types of tests might be 
valuable for CMake/CTest, or any way to make this happen ?




I would like to second this suggestion.  The absence of this feature 
presents a huge obstacle to replicating the functionality of the boost 
build functionality with CMake.  It's amazing to me that after so many 
years CMake doesn't have this functionality already.  It certainly seems 
to me that this would be easy to implement.


I'm aware that suggestions using CMake macros have been proposed.  But 
to the inexperienced user they are not intuitive or easy to understand.


Could we get some response on Edward's suggestion here? It's a serious 
obstacle to implementing support of CMake in Boost libraries.


Robert Ramey

--

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-developers] CMake 3.10 feature freeze on 2017-10-02

[Brad King]

Hi Folks,

The feature freeze in 'master' for CMake 3.10 will be on Oct 2, 2017.
I may announce a freeze in 'stage' sometime in the preceding week so
that we can get any remaining dashboard trouble cleaned up.

Thanks,
-Brad
-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] [Windows] clang-cl.exe detected as MSVC?

[Mateusz Loskot]

On 12 September 2017 at 14:53, Konstantin Tokarev  wrote:
> 11.09.2017, 18:12, "Mateusz Loskot" :
>> On 11 September 2017 at 17:04, Konstantin Tokarev  wrote:
>>>  11.09.2017, 17:59, "Mateusz Loskot" :

  I'm building a project with CMake 3.9 using clang-cl.exe driver [1]
  from LLVM/clang 4.0 enabled with Visual Studio 2015 environment.

  CMake detects the compiler as Clang 4.0.0:

  -- The C compiler identification is Clang 4.0.0
  -- The CXX compiler identification is Clang 4.0.0
  -- Check for working C compiler: C:/Program Files/LLVM/bin/clang-cl.exe
  -- Check for working C compiler: C:/Program Files/LLVM/bin/clang-cl.exe 
 -- works

  and my project builds fine.

  In my CMakeLists.txt, there is this flags update:

  if(MSVC)
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /MP")
  endif()

  and in build log I see:

  clang-cl.exe: warning: argument unused during compilation: '/MP'

  I have double-checked and MSVC is defined and set True for clang-cl.exe.

  Is this correct?
>>>
>>>  Yes. clang-cl is mostly compatible with MSVC on the command line
>>
>> Mostly, or less or more, it's subjective and my experience show it is not
>> as compatible as one may expect.
>> Also, AFAIU, compatibility is only at driver level that is command
>> line interface.
>>
>>>  so it's natural that MSVC code in existing projects is applied to clang-cl 
>>> too.
>>
>> I'd rather expect CL.exe exclusively considered as CL.exe
>
> For fine-grained distinction you have CMAKE_CXX_COMPILER_ID


I'll switch over to that one. Thanks

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
-- 

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] Create Mac OS Bundle with VTK and Qt

[Romain LEGUAY]

Hello,

Sorry for this late answer!

After using DeployQt5.cmake script I succeed to resolve my problem. 

The icon problem was due to some mistake during the creation of my icns file.

Thanks again.

Romain

> Le 8 sept. 2017 à 21:42, Oleksii Vilchanskyi via CMake  a 
> écrit :
> 
> Hello,
> 
>> 1) I try to add an icon without success
>> When I launch my app, the default icon is used and not my icon.
> 
> Can you elaborate on this? You say that the .icns file is under
> Resources and the final Info.plist contains the proper key with the
> proper value and that a non-default icon is used when the application is
> launched. If you do actually see the icon on the application [for
> example] in Launchpad, then the bundle is correctly built and macOS can
> recognize the icon. If instead you see something like this[0], then the
> bundle is built incorrectly.
> 
> However, you also say "when I launch my app", which, if you mean
> application's runtime in particular, is unrelated to CMake or bundling.
> If the tray icon is broken etc. it's something your application is not
> doing (for example, we use RCC and /image for the icon).
> 
> So, if this is the former, then the bundling part is incorrect, if it's
> the latter, the program's behaviour is incorrect.
> 
> As a side note, I don't rely on MACOSX_PACKAGE_LOCATION property and
> install() the icon where it belongs.
> 
>> 2) For the libraries of VTK I tried to use macdeployqt (found using
> find_program) but it doesn’t found the libraries (installed in a custom
> directories)
>> Is there a simple way to copy all found libraries/framework?
> 
> I would recommend using DeployQt5.cmake module[1] instead of
> macdeployqt. Initially found on this list and later edited by Marcus D.
> Hanwell, the module (I believe) is distributed under BSD 3-clause.
> 
> Usage example[2], also under BSD 3-clause (I believe).
> 
> [0]:  >
> [1]:
>   
> >
> [2]:
>   
> >
> 
> Regards,
> Oleksii Vilchanskyi
> 
> On 8.9.2017 18:11, Romain LEGUAY wrote:
>> Hello everyone,
>> 
>> Since this morning, I try to create a Bundle Application using CMake (3.9.1).
>> 
>> My application use VTK (8.x) and Qt (5.x). The find_package of those two 
>> libraries works greats (no problem to build and run the application).
>> 
>> I have many problems:
>> 
>> 1) I try to add an icon without success.
>> 2) I don’t know how (and where) to copy VTK dynamic libraries.
>> ( Optional / not really related ) 3) When I try to use only some components 
>> of VTK, my application is linking to all VTK modules
>> 
>> I’m going to details each points:
>> 
>> 1) For the icon issue, I proceed this way:
>> 
>> 
>> set(ICON_NAME "appIcon.icns") # I try without the icns extension without 
>> success.
>> set(ICON_PATH "${CMAKE_CURRENT_SOURCE_DIR}/resources/icons/${ICON_NAME}")
>> set_source_files_properties("${ICON_PATH}" PROPERTIES 
>> MACOSX_PACKAGE_LOCATION Resources)
>> 
>> add_executable(MYAPP MACOSX_BUNDLE ${ICON_PATH} ${other_sources})
>> 
>> set_target_properties(CRAFPACK_GUI PROPERTIES
>>  MACOSX_BUNDLE_ICON_FILE ${ICON_NAME})
>> 
>> 
>> The icon is copied inside the Resources folder of my bundle and the 
>> Info.plist is well updated (the CFBundleIconFile key is set to 
>> "appIcon.icns").
>> 
>> When I launch my app, the default icon is used and not my icon.
>> 
>> 
>> 2) For the libraries of VTK I tried to use macdeployqt (found using 
>> find_program) but it doesn’t found the libraries (installed in a custom 
>> directories)
>> 
>> I tried to use BundleUtilities without any success (except to tell me that 
>> cmake doesn’t found the libraries).
>> 
>> I attach you my CMakeLists.
>> 
>> Is there a simple way to copy all found libraries/framework?
>> 
>> Thank you!
>> 
>> 
>> 
> -- 
> 
> Powered by www.kitware.com 
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ 
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html 
> 
> CMake Consulting: http://cmake.org/cmake/help/consulting.html 
> 
> CMake Training Courses: http://cmake.org/cmake/help/training.html 
> 
> 
> Visit other Kitware open-source projects at 
> 

Re: [CMake] Clang for Windows with CMake and Ninja (and Visual Studio)

[Nagy-Egri Máté Ferenc via CMake]

The link error is some error on my setup. The /nologo et al part still stands 
though. Can CMake invoke the Windows binary of Clang correctly?

Feladó: Nagy-Egri Máté Ferenc via CMake
Elküldve: 2017. szeptember 12., kedd 15:01
Címzett: Cmake Mailing List
Tárgy: [CMake] Clang for Windows with CMake and Ninja (and Visual Studio)

Hi!

I am trying to build using the Open Folder feature of VS (with CMake server 
mode integration) with the Windows binary release of Clang. However, when I try 
to build using clang++.exe, it argues about unknown compiler switches

clang++.exe: error: no such file or directory: '/nologo'

while if I use the clang-cl.exe front-end of Clang, it fails saying

LINK : fatal error LNK1104: cannot open file 'gdi32.lib'

Does this both inside VS and in a developer command prompt. My invocation is as 
follows:

cmake -G Ninja -DCMAKE_CXX_COMPILER=C:/Kellekek/LLVM/Clang/5.0/bin/clang++.exe 
C:\Users\Matty\Source\simplecpp\


My questions:

1. Why does CMake give MSVC params to Clang on Windows?
2. Is there a way to let the clang-cl front-end know how to link to system 
libraries?

Cheers,
Máté

-- 

Powered by www.kitware.com

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

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

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

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

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

[Cmake-commits] CMake branch, master, updated. v3.9.2-779-g3ea87bc

[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  3ea87bce69d1b6120b227fed3838f1bc9ab45db1 (commit)
   via  cb171502287db0e4911faa10d748c72f08e5a9dd (commit)
   via  3f8c6cab4bb4a9f68708c11a38e4487dad363e38 (commit)
   via  ea7177b94760d6abcb05649bf694143c53608766 (commit)
   via  8a4755ca57d5a0ef664b067f6ace737b417ef40d (commit)
   via  95b17c89be15a768178d66f42573d90852a1b986 (commit)
   via  a451995fc6485929bc606986572eee162d6fc4e4 (commit)
   via  1e6569c9f4614b3d915653bab2fd423c99d814d6 (commit)
   via  3e8b3e94dc6d3ea59dd437f1ea46786f9f0ec1d2 (commit)
  from  f06ddacafc68369150f3a6fa806e8e4af421dc7b (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=3ea87bce69d1b6120b227fed3838f1bc9ab45db1
commit 3ea87bce69d1b6120b227fed3838f1bc9ab45db1
Merge: cb17150 8a4755c
Author: Brad King 
AuthorDate: Tue Sep 12 13:38:28 2017 +
Commit: Kitware Robot 
CommitDate: Tue Sep 12 09:39:40 2017 -0400

Merge topic 'vs-clang-llvm-support'

8a4755ca VS: Update support for LLVM-vs* toolsets from LLVM 5.0

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=cb171502287db0e4911faa10d748c72f08e5a9dd
commit cb171502287db0e4911faa10d748c72f08e5a9dd
Merge: 3f8c6ca 95b17c8
Author: Brad King 
AuthorDate: Tue Sep 12 13:38:03 2017 +
Commit: Kitware Robot 
CommitDate: Tue Sep 12 09:38:24 2017 -0400

Merge topic 'get-or-create-source-group'

95b17c89 Use cmMakefile::GetOrCreateSourceGroup in 
cmQtAutogeneratorsInitializer
a451995f Use cmMakefile::GetOrCreateSourceGroup in cmSourceGroupCommand
1e6569c9 cmMakefile: Add GetOrCreateSourceGroup methods
3e8b3e94 cmMakefile: Collect source group methods in one place

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3f8c6cab4bb4a9f68708c11a38e4487dad363e38
commit 3f8c6cab4bb4a9f68708c11a38e4487dad363e38
Merge: f06ddac ea7177b
Author: Brad King 
AuthorDate: Tue Sep 12 13:35:55 2017 +
Commit: Kitware Robot 
CommitDate: Tue Sep 12 09:36:12 2017 -0400

Merge topic 'iwyu-update'

ea7177b9 cmCustomCommandGenerator: Fix include-what-you-use diagnostic

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ea7177b94760d6abcb05649bf694143c53608766
commit ea7177b94760d6abcb05649bf694143c53608766
Author: Brad King 
AuthorDate: Mon Sep 11 14:39:20 2017 -0400
Commit: Brad King 
CommitDate: Mon Sep 11 14:39:58 2017 -0400

cmCustomCommandGenerator: Fix include-what-you-use diagnostic

For `size_t` we should include `stddef.h`.

diff --git a/Source/cmCustomCommandGenerator.cxx 
b/Source/cmCustomCommandGenerator.cxx
index c6a2800..fa1c70e 100644
--- a/Source/cmCustomCommandGenerator.cxx
+++ b/Source/cmCustomCommandGenerator.cxx
@@ -13,6 +13,8 @@
 #include "cmSystemTools.h"
 #include "cm_auto_ptr.hxx"
 
+#include 
+
 cmCustomCommandGenerator::cmCustomCommandGenerator(cmCustomCommand const& cc,
const std::string& config,
cmLocalGenerator* lg)

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8a4755ca57d5a0ef664b067f6ace737b417ef40d
commit 8a4755ca57d5a0ef664b067f6ace737b417ef40d
Author: Konstantin Ivlev 
AuthorDate: Mon Sep 4 15:12:43 2017 +0700
Commit: Brad King 
CommitDate: Mon Sep 11 09:58:22 2017 -0400

VS: Update support for LLVM-vs* toolsets from LLVM 5.0

Revert commit v3.7.0-rc1~25^2 (VS: Recognize VS/LLVM toolset names as
Clang, 2016-09-28).  Since at least LLVM 5.0 the VS integration of the
LLVM toolchain now mimics cl and accepts MSVC-style command-line
arguments (unlike Microsoft Clang/C2).

Fixes: #17193, #17235

diff --git a/Modules/Platform/Windows-MSVC.cmake 
b/Modules/Platform/Windows-MSVC.cmake
index cfe6e1c..d9f213b 100644
--- a/Modules/Platform/Windows-MSVC.cmake
+++ b/Modules/Platform/Windows-MSVC.cmake
@@ -186,7 +186,7 @@ else()
   if(_MSVC_C_ARCHITECTURE_FAMILY STREQUAL "ARM" OR 
_MSVC_CXX_ARCHITECTURE_FAMILY STREQUAL "ARM")
 set(CMAKE_C_STANDARD_LIBRARIES_INIT "kernel32.lib user32.lib")
   elseif(MSVC_VERSION GREATER 1310)
-

Re: [CMake] debugging CMAKE_PREFIX_PATH

[Konstantin Tokarev]

12.09.2017, 16:31, "Zakrzewski, Jakub" :
> Hi,
>
>>  find_package(Qt5Core ${QT_MIN_VERSION} REQUIRED)
>
>>  I build with -DCMAKE_PREFIX_PATH set, and in CMakeCache.txt, I see:
>
>>  //No help, variable specified on the command line.
>>  CMAKE_PREFIX_PATH:PATH=/usr/pkg/qt5
>
>>  //The directory containing a CMake configuration file for Qt5Core.
>>  Qt5Core_DIR:PATH=Qt5Core_DIR-NOTFOUND
>
>>  # ls /usr/pkg/qt5/lib/cmake/Qt5Core/Qt5CoreConfig.cmake
>>  /usr/pkg/qt5/lib/cmake/Qt5Core/Qt5CoreConfig.cmake
>
>>  so AFAICT, Qt5CoreConfig.cmake should be found.
>
>>  What am I missing?
>
> according to the documentation: 
> https://cmake.org/cmake/help/v3.0/command/find_package.html
> you're using the find_package() in MODULE mode, so it tries to locate a 
> FindQt5Core.cmake.
>
> Use this:
> find_package(Qt5Core ${QT_MIN_VERSION} REQUIRED CONFIG)
>
> and it should do what you want.

This statement is wrong, when no MODULE or CONFIG are specified, CMake tries 
both, so find_package(Qt5Core ${QT_MIN_VERSION} REQUIRED) is a correct way.

What actually happens here: rogue CMake project overwrites user-supplied 
CMAKE_PREFIX_PATH with its own value, so it is disregarded.

As a workaround (without changing project), you can pass 
-DQt5Core_DIR=/usr/pkg/qt5/lib/cmake/Qt5Core

>
> --
> Grüsse,
> Jakub
> --
>
> 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

-- 
Regards,
Konstantin
-- 

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] debugging CMAKE_PREFIX_PATH

[Zakrzewski, Jakub]

Hi, 

> find_package(Qt5Core ${QT_MIN_VERSION} REQUIRED)

> I build with -DCMAKE_PREFIX_PATH set, and in CMakeCache.txt, I see:

> //No help, variable specified on the command line.
> CMAKE_PREFIX_PATH:PATH=/usr/pkg/qt5

> //The directory containing a CMake configuration file for Qt5Core.
> Qt5Core_DIR:PATH=Qt5Core_DIR-NOTFOUND

> # ls /usr/pkg/qt5/lib/cmake/Qt5Core/Qt5CoreConfig.cmake
> /usr/pkg/qt5/lib/cmake/Qt5Core/Qt5CoreConfig.cmake

> so AFAICT, Qt5CoreConfig.cmake should be found.

> What am I missing?

according to the documentation: 
https://cmake.org/cmake/help/v3.0/command/find_package.html
you're using the find_package() in MODULE mode, so it tries to locate a 
FindQt5Core.cmake.

Use this:
find_package(Qt5Core ${QT_MIN_VERSION} REQUIRED CONFIG)

and it should do what you want.

--
Grüsse,
Jakub
-- 

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] Clang for Windows with CMake and Ninja (and Visual Studio)

[Nagy-Egri Máté Ferenc via CMake]

Hi!

I am trying to build using the Open Folder feature of VS (with CMake server 
mode integration) with the Windows binary release of Clang. However, when I try 
to build using clang++.exe, it argues about unknown compiler switches

clang++.exe: error: no such file or directory: '/nologo'

while if I use the clang-cl.exe front-end of Clang, it fails saying

LINK : fatal error LNK1104: cannot open file 'gdi32.lib'

Does this both inside VS and in a developer command prompt. My invocation is as 
follows:

cmake -G Ninja -DCMAKE_CXX_COMPILER=C:/Kellekek/LLVM/Clang/5.0/bin/clang++.exe 
C:\Users\Matty\Source\simplecpp\


My questions:

1. Why does CMake give MSVC params to Clang on Windows?
2. Is there a way to let the clang-cl front-end know how to link to system 
libraries?

Cheers,
Máté
-- 

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] [Windows] clang-cl.exe detected as MSVC?

[Konstantin Tokarev]

11.09.2017, 18:12, "Mateusz Loskot" :
> On 11 September 2017 at 17:04, Konstantin Tokarev  wrote:
>>  11.09.2017, 17:59, "Mateusz Loskot" :
>>>  Hi,
>>>
>>>  I'm building a project with CMake 3.9 using clang-cl.exe driver [1]
>>>  from LLVM/clang 4.0 enabled with Visual Studio 2015 environment.
>>>
>>>  CMake detects the compiler as Clang 4.0.0:
>>>
>>>  -- The C compiler identification is Clang 4.0.0
>>>  -- The CXX compiler identification is Clang 4.0.0
>>>  -- Check for working C compiler: C:/Program Files/LLVM/bin/clang-cl.exe
>>>  -- Check for working C compiler: C:/Program Files/LLVM/bin/clang-cl.exe -- 
>>> works
>>>
>>>  and my project builds fine.
>>>
>>>  In my CMakeLists.txt, there is this flags update:
>>>
>>>  if(MSVC)
>>>    set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /MP")
>>>  endif()
>>>
>>>  and in build log I see:
>>>
>>>  clang-cl.exe: warning: argument unused during compilation: '/MP'
>>>
>>>  I have double-checked and MSVC is defined and set True for clang-cl.exe.
>>>
>>>  Is this correct?
>>
>>  Yes. clang-cl is mostly compatible with MSVC on the command line
>
> Mostly, or less or more, it's subjective and my experience show it is not
> as compatible as one may expect.
> Also, AFAIU, compatibility is only at driver level that is command
> line interface.
>
>>  so it's natural that MSVC code in existing projects is applied to clang-cl 
>> too.
>
> I'd rather expect CL.exe exclusively considered as CL.exe

For fine-grained distinction you have CMAKE_CXX_COMPILER_ID

>
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net

-- 
Regards,
Konstantin
-- 

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] debugging CMAKE_PREFIX_PATH

[Patrick Welche]

I am trying to build a package which has in its CMakeLists.txt:

set(CMAKE_PREFIX_PATH "${QT_PREFIX}/lib/cmake")
set(CMAKE_INCLUDE_CURRENT_DIR ON)
find_package(Qt5Core ${QT_MIN_VERSION} REQUIRED)

(It may be that QT_PREFIX is not set?)

I build with -DCMAKE_PREFIX_PATH set, and in CMakeCache.txt, I see:

//No help, variable specified on the command line.
CMAKE_PREFIX_PATH:PATH=/usr/pkg/qt5 

//The directory containing a CMake configuration file for Qt5Core.
Qt5Core_DIR:PATH=Qt5Core_DIR-NOTFOUND

# ls /usr/pkg/qt5/lib/cmake/Qt5Core/Qt5CoreConfig.cmake
/usr/pkg/qt5/lib/cmake/Qt5Core/Qt5CoreConfig.cmake

so AFAICT, Qt5CoreConfig.cmake should be found.

What am I missing?

Cheers,

Patrick
-- 

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] CTest model deviates from the requsted one

[Matějů Miroslav , Ing .]

Hi,

I would like to report the following problem. I experienced that CTest running 
a CTestScript with a manually specified model (e.g. CTEST_START(Experimental)) 
sometimes deviates from the selected model. For example, when the test model 
Nightly is requested, the test sometimes gets reported to CDash as Continuous; 
the Experimental model might get reported as Nightly or Continuous. I started 
to experience this problem massively when I started to run Continuous tests in 
addition to Nightly tests on my server.

I tried to add debug messages to the CTest and shell scripts which control the 
testing process in my environment. I found out that the wrong decision happens 
during the CTEST_START call.

The code:

IF (NOT BUILD_MODEL)
MESSAGE (FATAL_ERROR "Build model is not set")
ENDIF (NOT BUILD_MODEL)
CTEST_EMPTY_BINARY_DIRECTORY ("${CTEST_BINARY_DIRECTORY}")
MESSAGE(STATUS "Build model: ${BUILD_MODEL}")
CTEST_START (${BUILD_MODEL})
MESSAGE(STATUS "Build model: ${BUILD_MODEL}")

renders (using ctest -VV):

-- Build model: Experimental
SetCTestConfiguration:SourceDirectory:/home/ctest/trunk/tests/moduletests/cm
SetCTestConfiguration:BuildDirectory:/home/ctest/trunk/_build/moduletests/cm
Run dashboard with model Experimental
   Source directory: /home/ctest/trunk/tests/moduletests/cm
   Build directory: moduletests/cm
   Reading ctest configuration file: 
/home/ctest/trunk/tests/moduletests/cm/CTestConfig.cmake
SetCTestConfigurationFromCMakeVariable:NightlyStartTime:CTEST_NIGHTLY_START_TIME
SetCTestConfiguration:NightlyStartTime:01:00:00 UTC
SetCTestConfigurationFromCMakeVariable:Site:CTEST_SITE
SetCTestConfiguration:Site:MiM-testsrv-ubuntu
SetCTestConfigurationFromCMakeVariable:BuildName:CTEST_BUILD_NAME
SetCTestConfiguration:BuildName:cm
   Site: MiM-testsrv-ubuntu
   Build name: cm
   Use Continuous tag: 20170912-0800
-- Build model: Experimental

I tried to upgrade CMake from the distribution-provided version up to 3.9.1 but 
the problem persists.

I noticed that the problem appears after changing the model in the same build 
directory, despite it has been wiped using CTEST_EMPTY_BINARY_DIRECTORY. CTest 
seems to prefer the previously used model sometimes instead of the explicitly 
given one (using CTEST_START). So I am currently trying to work around it by 
using separate build directories for each model. Is it the correct way or would 
you recommend something else?

Best regards,

Ing. Miroslav Matějů
Programmer Analyst

AŽD Praha s.r.o.
Technology Division
Research and Development
Žirovnická 2/3146, 106 17  Prague
Czech Republic
Phone: +420 267 287 476
Web: www.azd.cz
-- 

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