[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-125-g5a3f539cd5

2019-10-24 Thread Kitware Robot via Cmake-commits 
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  5a3f539cd50621298d15df639c29a9c09aace443 (commit)
  from  b2b79e7776584d4903721756f39ccfcec8e560e9 (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=5a3f539cd50621298d15df639c29a9c09aace443
commit 5a3f539cd50621298d15df639c29a9c09aace443
Author: Kitware Robot 
AuthorDate: Fri Oct 25 00:01:07 2019 -0400
Commit: Kitware Robot 
CommitDate: Fri Oct 25 00:01:07 2019 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 1c8e050c59..05137c83f6 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,7 +1,7 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 16)
-set(CMake_VERSION_PATCH 20191024)
+set(CMake_VERSION_PATCH 20191025)
 #set(CMake_VERSION_RC 0)
 set(CMake_VERSION_IS_DIRTY 0)
 

---

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

Re: [CMake] CHECK_CXX_COMPILER_FLAG doesn't give correct result for -fsanitize=address

2019-10-24 Thread Michael Ellery 
I’ve dealt with that using something like this:

  set (_saved_CRL ${CMAKE_REQUIRED_LIBRARIES})
  set (CMAKE_REQUIRED_LIBRARIES “-fsanitize=address;asan")
  check_cxx_compiler_flag (-fsanitize=address COMPILER_SUPPORTS_SAN)
  set (CMAKE_REQUIRED_LIBRARIES ${_saved_CRL})

the second item in CMAKE_REQUIRED_LIBRARIES is only needed when using gcc which 
also requires a -lasan when linking (clang does not need this)

> On Oct 24, 2019, at 12:47 PM, Turner, Adrian Keith via CMake 
>  wrote:
> 
> Hi CMake Mailing List,
> 
> I am using the CHECK_CXX_COMPILER_FLAG directive in a CMake file to detect 
> whether the compiler uses the "-fsanitize=address" compiler flag. I'm using 
> the g++ 7.3.0 compiler which supports this flag but the 
> CHECK_CXX_COMPILER_FLAG directive incorrectly determines that this flag is 
> not supported.
> 
> To test this I tried compiling the following program:
> int main() {};
> 
> This compiled with the following commands:
> > g++ -fsanitize=address -c test.cpp
> > g++ -fsanitize=address test.o -o test.exe
> 
> And fails with the same error message as CHECK_CXX_COMPILER_FLAG when I 
> compile with:
> > g++ -fsanitize=address -c test.cpp
> > g++ test.o -o test.exe
> 
> producing the following message:
> Undefined symbols for architecture x86_64:
>   "___asan_init", referenced from:
>   __GLOBAL__sub_I_00099_0_test.cpp in test.o
>   "___asan_version_mismatch_check_v8", referenced from:
>   __GLOBAL__sub_I_00099_0_test.cpp in test.o
> ld: symbol(s) not found for architecture x86_64
> collect2: error: ld returned 1 exit status
> 
> It seems that CHECK_CXX_COMPILER_FLAG doesn't add the flag to the linking 
> command when it tests compilation. Is this a bug with CHECK_CXX_COMPILER_FLAG 
> or is there something I'm missing?
> 
> Many thanks
> Adrian Turner
> 
> 
> -- 
> 
> 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

[CMake] CHECK_CXX_COMPILER_FLAG doesn't give correct result for -fsanitize=address

2019-10-24 Thread Turner, Adrian Keith via CMake 
Hi CMake Mailing List,


I am using the CHECK_CXX_COMPILER_FLAG directive in a CMake file to detect 
whether the compiler uses the "-fsanitize=address" compiler flag. I'm using the 
g++ 7.3.0 compiler which supports this flag but the CHECK_CXX_COMPILER_FLAG 
directive incorrectly determines that this flag is not supported.


To test this I tried compiling the following program:

int main() {};


This compiled with the following commands:

> g++ -fsanitize=address -c test.cpp
> g++ -fsanitize=address test.o -o test.exe

And fails with the same error message as CHECK_CXX_COMPILER_FLAG when I compile 
with:
> g++ -fsanitize=address -c test.cpp
> g++ test.o -o test.exe

producing the following message:

Undefined symbols for architecture x86_64:
  "___asan_init", referenced from:
  __GLOBAL__sub_I_00099_0_test.cpp in test.o
  "___asan_version_mismatch_check_v8", referenced from:
  __GLOBAL__sub_I_00099_0_test.cpp in test.o
ld: symbol(s) not found for architecture x86_64
collect2: error: ld returned 1 exit status

It seems that CHECK_CXX_COMPILER_FLAG doesn't add the flag to the linking 
command when it tests compilation. Is this a bug with CHECK_CXX_COMPILER_FLAG 
or is there something I'm missing?

Many thanks
Adrian Turner


-- 

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] VS2019 LLVM Toolset?

2019-10-24 Thread Mojca Miklavec 
On Thu, 24 Oct 2019 at 21:36, Osman Zakir wrote:
>
> Yes, I looked at this: 
> https://devblogs.microsoft.com/cppblog/clang-llvm-support-in-visual-studio/ 
> so I kind of get it.  VS2019 has built-in support for LLVM.  I of course do 
> have LLVM installed.  So for this, I have to put "ClangCL" as the argument to 
> -T?  Okay, thanks.  I'll try that.

The relevant part is only the first screenshot.


Please note that Visual Studio 2019 also has some kind of "native
support for CMake", so you don't even need to run CMake manually to
generate the project. You just open a folder with CMakeLists and
generate projects on the fly with whichever toolset you prefer. I was
playing with it a while back with a Preview version, but it kept
crashing too often to be useful. They have released a few updates
since, but I never tested again, so I'm not sure if it got better or
not (I hope it did), I simply keep using the traditional way for now.

Mojca
-- 

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] These two generator expressions should be equivalent, but one working while the other not working. Bug?

2019-10-24 Thread Alan W. Irwin 

On 2019-10-24 08:08-0400 Brad King wrote:


On 10/24/19 12:18 AM, Alan W. Irwin wrote:

 $

   Expression did not evaluate to a known generator expression


The `*_COMPILER_ID` generator expressions are a hard-coded set
corresponding to the languages supported by upstream CMake:

* C_COMPILER_ID
* CXX_COMPILER_ID
* CUDA_COMPILER_ID
* Fortran_COMPILER_ID
* OBJC_COMPILER_ID   (new in 3.16)
* OBJCXX_COMPILER_ID (new in 3.16)

This is because the language name is part of the expression name.

In the `$` case, the language name
is one of the parameters.


Thanks for that clear explanation of this current CMake hard-coded limitation.

To work around it, I will stick with the $
genex, but only bother with that -pthread mapping for cmake 3.15.0 and above
(since that is the first version of CMake to support 
$).

So that takes care of PLplot's needs.  However, on the general question of the
above CMake hard-coded language limitation I searched through

for "CXX" and found these genex's

$<"language"_COMPILER_ID:compiler_ids>
$<"language"_COMPILER_VERSION:version>
$<"language"_COMPILER_ID>
$<"language"_COMPILER_VERSION>

where I have substituted "language" for CXX to indicate these actually 
represent 4 different
classes of genex's where "language" is currently on a hard-coded list for the 
first, and
it appears from Source/cmGeneratorExpressionNode.cxx
that is true of the rest as well.

My C++ skills are limited and as a result I don't understand the CMake
code that well, and I don't have any idea how difficult this would be to
implement.  So I should ask would you entertain a feature request to remove that
hard-coded language limitation on the above 4 classes of genex so both
internally and externally supported languages would work for all of
them?

For example, you currently have

$<"language"_COMPILER_ID:compiler_ids> where compiler_ids is a comma-separated
list. 1 if the CMake’s compiler id of the "language" compiler matches any
one of the entries in compiler_ids, otherwise 0. See also the
CMAKE__COMPILER_ID variable

where "language" is restricted to the above hard-coded list.
Would it be straightforward to change the implementation of this
whole class of genexes so that "language" was simply determined from
the first part of the genex name with that "language" then checked
against the available language support?

If so, that approach would solve the above issue (i.e., drop this
artificial distinction between languages with internal and external
support) and also have the additional advantages that it would replace
what I presume are currently 6 different genex implementations and the
documentation of each of those with just one implementation and
corresponding piece of documentation with no introduced backwards
incompatibilities due to this change.

And similarly for

$<"language"_COMPILER_VERSION:version>
$<"language"_COMPILER_ID>
$<"language"_COMPILER_VERSION>

Alan
__
Alan W. Irwin

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

Linux-powered Science
__
--

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] VS2019 LLVM Toolset?

2019-10-24 Thread Osman Zakir 
Yes, I looked at this: 
https://devblogs.microsoft.com/cppblog/clang-llvm-support-in-visual-studio/ so 
I kind of get it.  VS2019 has built-in support for LLVM.  I of course do have 
LLVM installed.  So for this, I have to put "ClangCL" as the argument to -T?  
Okay, thanks.  I'll try that.
-- 

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] Alternative locations for boost in cmake

2019-10-24 Thread Mateusz Loskot 
On Thu, 24 Oct 2019 at 20:44, Mahmood Naderan  wrote:
>
> Thank you. I tried this command:
>
> cmake -DBoost_NO_SYSTEM_PATHS=ON 
> -DBOOST_INCLUDE_DIR=/storage/users/mnaderan/boost_1_65_1/build/include/ 
> -DBoost_LIBRARY_DIRS=/storage/users/mnaderan/boost_1_65_1/build/lib/ 
> -DBoost_ADDITIONAL_VERSIONS=1.65.1 ..
>
> The paths are correct as you can see below:
>
> $ ls /storage/users/mnaderan/boost_1_65_1/build/lib/
> libboost_atomic.a  libboost_math_tr1l.so.1.65.1
> libboost_atomic.so libboost_math_tr1.so

>
> However, the cmake command fails with the following error message
>
> -- Could NOT find Boost
> CMake Warning at 
> /storage/users/mnaderan/tools/cmake-3.9.0/share/cmake-3.9/Modules/FindBoost.cmake:769
>  (message):
>   Imported targets not available for Boost version

You are using very old CMake 3.9 which has no idea about Boost 1.65
https://github.com/Kitware/CMake/blob/v3.9.0/Modules/FindBoost.cmake#L769

Rule #1: Use latest version of CMake, ALWAYS!

There is absolutely no reason or excuse to not to use the latest as there are
- deb packages available https://apt.kitware.com/
- generic installer for any Linux and Windows

Updating CMake is easy-peasy for us lazy programmers with a bit of scripting:
https://github.com/mloskot/wsl-config/blob/master/scripts/install-cmake-latest.sh
https://github.com/mloskot/wsl-config/blob/master/scripts/install-cmake-latest.ps1

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

Re: [CMake] VS2019 LLVM Toolset?

2019-10-24 Thread Mojca Miklavec 
On Thu, 24 Oct 2019 at 20:28, Osman Zakir wrote:
>
> Hi.  I tried to specify the LLVM Toolset for VS2019 by doing "-T LLVM" and 
> also "-T llvm" but it failed both times.

For me "-T ClangCL" seems to have worked (provided that you install
Clang with VS 2019, of course).
(To figure out the potentially correct value I looked into the xml
project file generated when I manually changed the toolset and saved
the project.)

Under 2017 this was a separate "plugin" (or whatever it was called),
while VS 2019 provides it natively.


What I could not get working correctly under this CMake-generated
setup are the unit tests for CUDA (there must be some faulty compiler
flags).

Mojca
-- 

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] Alternative locations for boost in cmake

2019-10-24 Thread Mahmood Naderan via CMake 
Thank you. I tried this command:
cmake -DBoost_NO_SYSTEM_PATHS=ON 
-DBOOST_INCLUDE_DIR=/storage/users/mnaderan/boost_1_65_1/build/include/ 
-DBoost_LIBRARY_DIRS=/storage/users/mnaderan/boost_1_65_1/build/lib/ 
-DBoost_ADDITIONAL_VERSIONS=1.65.1 ..

The paths are correct as you can see below:

$ ls /storage/users/mnaderan/boost_1_65_1/build/lib/
libboost_atomic.a  libboost_math_tr1l.so.1.65.1
libboost_atomic.so libboost_math_tr1.so
...


$ ls /storage/users/mnaderan/boost_1_65_1/build/include/boost/
accumulators  geometry   preprocessor.hpp
algorithm geometry.hpp   process
align get_pointer.hpp    process.hpp
...


I didn't paste all files though.

However, the cmake command fails with the following error message
-- Could NOT find Boost
CMake Warning at 
/storage/users/mnaderan/tools/cmake-3.9.0/share/cmake-3.9/Modules/FindBoost.cmake:769
 (message):
  Imported targets not available for Boost version
Call Stack (most recent call first):
  
/storage/users/mnaderan/tools/cmake-3.9.0/share/cmake-3.9/Modules/FindBoost.cmake:873
 (_Boost_COMPONENT_DEPENDENCIES)
  
/storage/users/mnaderan/tools/cmake-3.9.0/share/cmake-3.9/Modules/FindBoost.cmake:1501
 (_Boost_MISSING_DEPENDENCIES)
  cmake/FindBoost.cmake:6 (FIND_PACKAGE)
  CMakeLists.txt:47 (include)


CMake Warning at 
/storage/users/mnaderan/tools/cmake-3.9.0/share/cmake-3.9/Modules/FindBoost.cmake:769
 (message):
  Imported targets not available for Boost version
Call Stack (most recent call first):
  
/storage/users/mnaderan/tools/cmake-3.9.0/share/cmake-3.9/Modules/FindBoost.cmake:873
 (_Boost_COMPONENT_DEPENDENCIES)
  
/storage/users/mnaderan/tools/cmake-3.9.0/share/cmake-3.9/Modules/FindBoost.cmake:1501
 (_Boost_MISSING_DEPENDENCIES)
  cmake/FindBoost.cmake:6 (FIND_PACKAGE)
  CMakeLists.txt:47 (include)


CMake Warning at 
/storage/users/mnaderan/tools/cmake-3.9.0/share/cmake-3.9/Modules/FindBoost.cmake:769
 (message):
  Imported targets not available for Boost version
Call Stack (most recent call first):
  
/storage/users/mnaderan/tools/cmake-3.9.0/share/cmake-3.9/Modules/FindBoost.cmake:873
 (_Boost_COMPONENT_DEPENDENCIES)
  
/storage/users/mnaderan/tools/cmake-3.9.0/share/cmake-3.9/Modules/FindBoost.cmake:1501
 (_Boost_MISSING_DEPENDENCIES)
  cmake/FindBoost.cmake:6 (FIND_PACKAGE)
  CMakeLists.txt:47 (include)




Regards,
Mahmood 

On Thursday, October 24, 2019, 9:01:53 PM GMT+3:30, Mateusz Loskot 
 wrote:  
When you read word `variables` in CMake documentation,
it means CMake variables (also known as cache entries).
Otherwise, it would be qualified using word `environment`.

The CMake variables can be set via command line option -D [1]

[1] https://cmake.org/cmake/help/latest/manual/cmake.1.html

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:
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

[CMake] VS2019 LLVM Toolset?

2019-10-24 Thread Osman Zakir 
Hi.  I tried to specify the LLVM Toolset for VS2019 by doing "-T LLVM" and also 
"-T llvm" but it failed both times.  What I get for the former is this:

"
cmake -G "Visual Studio 16 2019" -A x64 -T LLVM .. 
-DCMAKE_INSTALL_PREFIX="C:/Program Files/FLTK" -DCMAKE_BUILD_TYPE=Release
CMake Error at CMakeLists.txt:24 (project):​
  Failed to run MSBuild command:​
​
C:/Program Files (x86)/Microsoft Visual 
Studio/2019/Community/MSBuild/Current/Bin/MSBuild.exe​
​
  to get the value of VCTargetsPath:​
​
Microsoft (R) Build Engine version 16.3.2+e481bbf88 for .NET Framework​
Copyright (C) Microsoft Corporation. All rights reserved.​
​
Build started 10/24/2019 10:19:12 PM.​
Project "C:\fltk-1.3.5\build\CMakeFiles\3.15.4\VCTargetsPath.vcxproj" on 
node 1 (default targets).​
C:\Program Files (x86)\Microsoft Visual 
Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppBuild.targets(379,5):
 error MSB8020: The build tools for LLVM (Platform Toolset = 'LLVM') cannot be 
found. To build using the LLVM build tools, please install LLVM build tools.  
Alternatively, you may upgrade to the current Visual Studio tools by selecting 
the Project menu or right-click the solution, and then selecting "Retarget 
solution". [C:\fltk-1.3.5\build\CMakeFiles\3.15.4\VCTargetsPath.vcxproj]​
Done Building Project 
"C:\fltk-1.3.5\build\CMakeFiles\3.15.4\VCTargetsPath.vcxproj" (default targets) 
-- FAILED.​
​
Build FAILED.​
​
"C:\fltk-1.3.5\build\CMakeFiles\3.15.4\VCTargetsPath.vcxproj" (default 
target) (1) ->​
(PrepareForBuild target) ->​
  C:\Program Files (x86)\Microsoft Visual 
Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppBuild.targets(379,5):
 error MSB8020: The build tools for LLVM (Platform Toolset = 'LLVM') cannot be 
found. To build using the LLVM build tools, please install LLVM build tools.  
Alternatively, you may upgrade to the current Visual Studio tools by selecting 
the Project menu or right-click the solution, and then selecting "Retarget 
solution". [C:\fltk-1.3.5\build\CMakeFiles\3.15.4\VCTargetsPath.vcxproj]​
​
0 Warning(s)​
1 Error(s)​
​
Time Elapsed 00:00:00.21​
​
​
  Exit code: 1​
​
​
​
-- Configuring incomplete, errors occurred!​
See also "C:/fltk-1.3.5/build/CMakeFiles/CMakeOutput.log".
"
For the latter it's similar.  Just change "'LLVM'" in the error message to 
"'LLVM'".
-- 

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] Alternative locations for boost in cmake

2019-10-24 Thread Mateusz Loskot 
On Thu, 24 Oct 2019 at 19:05, Mahmood Naderan via CMake  wrote:
>
> I have read https://cmake.org/cmake/help/v3.0/module/FindBoost.html which 
> states some variables for boost library.
> I want to know where should I set these variables. For example, in the 
> terminal, I have written
>
> $ export Boost_NO_SYSTEM_PATHS=ON

When you read word `variables` in CMake documentation,
it means CMake variables (also known as cache entries).
Otherwise, it would be qualified using word `environment`.

The CMake variables can be set via command line option -D [1]

[1] https://cmake.org/cmake/help/latest/manual/cmake.1.html

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

[CMake] Alternative locations for boost in cmake

2019-10-24 Thread Mahmood Naderan via CMake 
Hi,
I have read https://cmake.org/cmake/help/v3.0/module/FindBoost.html which 
states some variables for boost library. I want to know where should I set 
these variables. For example, in the terminal, I have written
$ export Boost_NO_SYSTEM_PATHS=ON
However, after I run "cmake ..", I see:

-- Boost version: 1.63.0
-- Boost version: 1.63.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   timer
--   chrono



That is system boost and I don't want that.Any idea?

Regards,
Mahmood-- 

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] Don't list Up-to-date files during install

2019-10-24 Thread Ben Morgan 
Hi Jason,

See the CMAKE_INSTALL_MESSAGE variable:

https://cmake.org/cmake/help/v3.16/variable/CMAKE_INSTALL_MESSAGE.html 


setting this to “LAZY” should do what you want.

Cheers,

Ben.

> On 24 Oct 2019, at 16:44, Jason Beach  wrote:
> 
> When installing files, cmakes prints a list of all files that are to be 
> installed, even if some of those files are already installed and up-to-date 
> (i.e. installed from a previous build).  If the file is not installed or 
> out-of date, cmake prints "Installing: ..." and if a file was already 
> installed and didn't change it prints "Up-to-date: ..."
> 
> Is there a way to suppress listing all of the up-to-date files and only show 
> the files that are being installed because they changed?  Some of the 
> libraries we use install a ton of files and if we change only one it's 
> difficult to find and verify that one was installed among the sea of 
> up-to-date files.
> 
> Thanks,
> Jason
> -- 
> 
> 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

-- 
==
Dr. Ben Morgan
Senior Research Fellow
Department of Physics
University of Warwick
Coventry CV4 7AL
==

-- 

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] Don't list Up-to-date files during install

2019-10-24 Thread Jason Beach 
When installing files, cmakes prints a list of all files that are to be
installed, even if some of those files are already installed and up-to-date
(i.e. installed from a previous build).  If the file is not installed or
out-of date, cmake prints "Installing: ..." and if a file was already
installed and didn't change it prints "Up-to-date: ..."

Is there a way to suppress listing all of the up-to-date files and only
show the files that are being installed because they changed?  Some of the
libraries we use install a ton of files and if we change only one it's
difficult to find and verify that one was installed among the sea of
up-to-date files.

Thanks,
Jason
-- 

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-commits] CMake branch, master, updated. v3.16.0-rc2-124-gb2b79e7776

2019-10-24 Thread Kitware Robot via Cmake-commits 
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  b2b79e7776584d4903721756f39ccfcec8e560e9 (commit)
   via  2d1fd3f8188176e51cc30b64b471158a36916b65 (commit)
  from  11897b824cb18f40bcbcee03ab4cb106a10ee436 (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=b2b79e7776584d4903721756f39ccfcec8e560e9
commit b2b79e7776584d4903721756f39ccfcec8e560e9
Merge: 11897b824c 2d1fd3f818
Author: Brad King 
AuthorDate: Thu Oct 24 14:41:21 2019 +
Commit: Kitware Robot 
CommitDate: Thu Oct 24 10:41:30 2019 -0400

Merge topic 'doc-dev-note-ext'

2d1fd3f818 Help: Fix missed extension for `CMAKE_MESSAGE_CONTEXT` release 
note

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2d1fd3f8188176e51cc30b64b471158a36916b65
commit 2d1fd3f8188176e51cc30b64b471158a36916b65
Author: Alex Turbov 
AuthorDate: Thu Oct 24 13:07:51 2019 +0200
Commit: Alex Turbov 
CommitDate: Thu Oct 24 13:07:51 2019 +0200

Help: Fix missed extension for `CMAKE_MESSAGE_CONTEXT` release note

diff --git a/Help/release/dev/feature-CMAKE_MESSAGE_CONTEXT 
b/Help/release/dev/feature-CMAKE_MESSAGE_CONTEXT.rst
similarity index 100%
rename from Help/release/dev/feature-CMAKE_MESSAGE_CONTEXT
rename to Help/release/dev/feature-CMAKE_MESSAGE_CONTEXT.rst

---

Summary of changes:
 .../{feature-CMAKE_MESSAGE_CONTEXT => feature-CMAKE_MESSAGE_CONTEXT.rst}  | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename Help/release/dev/{feature-CMAKE_MESSAGE_CONTEXT => 
feature-CMAKE_MESSAGE_CONTEXT.rst} (100%)


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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc2-8-g81ded33c04

2019-10-24 Thread Kitware Robot via Cmake-commits 
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, release has been updated
   via  81ded33c04e0d7faff55b048877fcd795ce8afe0 (commit)
   via  fd867a49c4c9563c90bf9ebf66ba602dee072e35 (commit)
  from  fa1fe09dbbf8e18e02a67dc20adb3cb523418ef6 (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 -
---

Summary of changes:
 Help/policy/CMP0097.rst | 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

Re: [cmake-developers] These two generator expressions should be equivalent, but one working while the other not working. Bug?

2019-10-24 Thread Brad King via cmake-developers 
On 10/24/19 12:18 AM, Alan W. Irwin wrote:
>  $
> 
>Expression did not evaluate to a known generator expression

The `*_COMPILER_ID` generator expressions are a hard-coded set
corresponding to the languages supported by upstream CMake:

* C_COMPILER_ID
* CXX_COMPILER_ID
* CUDA_COMPILER_ID
* Fortran_COMPILER_ID
* OBJC_COMPILER_ID   (new in 3.16)
* OBJCXX_COMPILER_ID (new in 3.16)

This is because the language name is part of the expression name.

In the `$` case, the language name
is one of the parameters.

-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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-122-g11897b824c

2019-10-24 Thread Kitware Robot via Cmake-commits 
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  11897b824cb18f40bcbcee03ab4cb106a10ee436 (commit)
   via  920dd9d56bca8f855675ecf65c13059d111c3ec6 (commit)
   via  26a0f5d6d428f025f4bfb987d6dc24acb0707aec (commit)
   via  81ded33c04e0d7faff55b048877fcd795ce8afe0 (commit)
   via  fd867a49c4c9563c90bf9ebf66ba602dee072e35 (commit)
   via  39fbbd6feaec91bcb2d31ee01ec431d0791a2baf (commit)
  from  490da0bd337f33c51884d7fe3bd5ac042ac0b0c5 (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=11897b824cb18f40bcbcee03ab4cb106a10ee436
commit 11897b824cb18f40bcbcee03ab4cb106a10ee436
Merge: 920dd9d56b 81ded33c04
Author: Brad King 
AuthorDate: Thu Oct 24 08:03:40 2019 -0400
Commit: Brad King 
CommitDate: Thu Oct 24 08:03:40 2019 -0400

Merge branch 'release-3.16'


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=920dd9d56bca8f855675ecf65c13059d111c3ec6
commit 920dd9d56bca8f855675ecf65c13059d111c3ec6
Merge: 26a0f5d6d4 fd867a49c4
Author: Brad King 
AuthorDate: Thu Oct 24 12:02:23 2019 +
Commit: Kitware Robot 
CommitDate: Thu Oct 24 08:03:15 2019 -0400

Merge topic 'cmp0097-doc-fix'

fd867a49c4 Help: Fix capitalization in CMP0097 documentation

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=26a0f5d6d428f025f4bfb987d6dc24acb0707aec
commit 26a0f5d6d428f025f4bfb987d6dc24acb0707aec
Merge: 490da0bd33 39fbbd6fea
Author: Brad King 
AuthorDate: Thu Oct 24 12:02:13 2019 +
Commit: Kitware Robot 
CommitDate: Thu Oct 24 08:02:21 2019 -0400

Merge topic 'fortran-ext-F'

39fbbd6fea Fortran: Add .F extension to Source Files group

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=39fbbd6feaec91bcb2d31ee01ec431d0791a2baf
commit 39fbbd6feaec91bcb2d31ee01ec431d0791a2baf
Author: Johnny Jazeix 
AuthorDate: Wed Oct 23 14:47:45 2019 +0200
Commit: Brad King 
CommitDate: Wed Oct 23 09:20:25 2019 -0400

Fortran: Add .F extension to Source Files group

While at it, improve source layout of the regex string literal.

Fixes: #8768

diff --git a/Source/cmSourceFile.h b/Source/cmSourceFile.h
index 82a3625b8b..19a0d29136 100644
--- a/Source/cmSourceFile.h
+++ b/Source/cmSourceFile.h
@@ -154,9 +154,8 @@ private:
 #define CM_HEADER_REGEX "\\.(h|hh|h\\+\\+|hm|hpp|hxx|in|txx|inl)$"
 
 #define CM_SOURCE_REGEX   \
-  "\\.(C|M|c|c\\+\\+|cc|cpp|cxx|cu|f|f90|for|fpp|ftn|m|mm|rc|def|r|odl|idl|"  \
-  "hpj"   \
-  "|bat)$"
+  "\\.(C|F|M|c|c\\+\\+|cc|cpp|cxx|cu|f|f90|for|fpp|ftn|m|mm|" \
+  "rc|def|r|odl|idl|hpj|bat)$"
 
 #define CM_PCH_REGEX "cmake_pch\\.(h|hxx)$"
 

---

Summary of changes:
 Help/policy/CMP0097.rst | 2 +-
 Source/cmSourceFile.h   | 5 ++---
 2 files changed, 3 insertions(+), 4 deletions(-)


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