[Cmake-commits] CMake branch, master, updated. v3.9.0-rc2-46-gc3868cf

[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  c3868cf90ca39d86f52c9e9f6492c856034cd02f (commit)
  from  591557ba450f1f24610ea0eefcb4e1d7665fae25 (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=c3868cf90ca39d86f52c9e9f6492c856034cd02f
commit c3868cf90ca39d86f52c9e9f6492c856034cd02f
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Sat Jun 10 00:01:10 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Sat Jun 10 00:01:10 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 6630aa6..5837d5c 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 20170609)
+set(CMake_VERSION_PATCH 20170610)
 #set(CMake_VERSION_RC 1)

---

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


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

[CMake] Reentrant-safe includes

[Robert Dailey]

So I have a series of common CMake scripts I use:

pre-setup.cmake
post-setup.cmake

I include pre-setup.cmake at the beginning of the root CMakeLists.txt
and post-setup.cmake is included at the bottom. add_subdirectory() and
other target stuff is done inbetween.

One issue I run into is that these files are sometimes re-entered. For
example, sometimes I have a git submodule with a CMakeLists.txt that
is the root when CMake is run on the submodule by itself, and in
others the submodule's root CMakeLists.txt is just a normal script
included by the parent repository's scripts.

At the moment I'm doing some counting logic to make sure that
pre-setup.cmake and post-setup.cmake are not included multiple times,
if they are not at the root CMakeLists.txt.

Example:

At the top of pre-setup.cmake:

if( NOT DEFINED PRE_SETUP_DEPTH_COUNT )
set( PRE_SETUP_DEPTH_COUNT 0 )
endif()

math( EXPR PRE_SETUP_DEPTH_COUNT "${PRE_SETUP_DEPTH_COUNT}+1" )

if( PRE_SETUP_DEPTH_COUNT GREATER 1 )
return()
endif()

And at the top of post-setup.cmake:

math( EXPR PRE_SETUP_DEPTH_COUNT "${PRE_SETUP_DEPTH_COUNT}-1" )
if( PRE_SETUP_DEPTH_COUNT )
return()
endif()

This seems to work, but is there a simpler/better solution?
-- 

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] CMake problem with intel parallel studio 2017

[Mamales, Petros via CMake]

Thank you very much!
I saw it to be along these lines, by doing (quite) a few "greps" and reading 
the documentation. The last step is the one I was trying to pin down -;)
All the best,
Petros

-Original Message-
From: Brad King [mailto:brad.k...@kitware.com] 
Sent: Friday, June 09, 2017 12:45 PM
To: Mamales, Petros [CCC-OT NE]
Cc: CMake
Subject: Re: [CMake] CMake problem with intel parallel studio 2017

On 06/09/2017 11:51 AM, Mamales, Petros  wrote:
> how is the specification of the toolset (from command line) translates 
> to the modules folder in CMake?

The -T option specifies the CMAKE_GENERATOR_TOOLSET:

  
https://urldefense.proofpoint.com/v2/url?u=https-3A__cmake.org_cmake_help_v3.9_variable_CMAKE-5FGENERATOR-5FTOOLSET.html=DwIC-g=j-EkbjBYwkAB4f8ZbVn1Fw=6_wuzZXSt4ORpgK3tgk-CcUFf9XSS7xAF6v69MPzaXs=ndEV5F8r4x5YENtVn3zcQE4_UrdFQ64ciZs23R-67tc=kHqrsGxWzTErzhOGTW390ytAG-PjpuE7WW1uxM7hEoM=
 

That value tells the VS generator what to put in the PlatformToolset field of 
.vcxproj files.  This influences how the compiler identification source is 
compiled, and that uses preprocessor logic to detect the compiler id and 
version based on predefined macros.  The resulting compiler id is used to 
decide which compiler/platform information modules to load.

-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

Re: [CMake] Forcing CMake to find static library

[Michael Ellery]

if you know exactly where the library is (via the ENV), then I guess you want 
to specify the NO_DEFAULT_PATH option to find_library. Alternatively, see if 
you can use the standard find module included with cmake:

https://github.com/Kitware/CMake/blob/master/Modules/FindLAPACK.cmake

..and in that case you could set LAPACK_ROOT using your ENV value.

HTH,
Mike

> On Jun 9, 2017, at 10:39 AM, Matthias Redies  wrote:
> 
> Hello,
> 
> I am trying to force CMAKE to include a specific static lapack library,
> set through the environment variable $LAPACK_LIB:
> 
> > ls $LAPACK_LIB
> libblas_extra.a  libcblas.a  liblapack.a  liblapacke.a libtmglib.a
> 
> > echo $LAPACK_LIB
> /bgsys/local/lapack/3.7.0/lib
> 
> 
> This is how I am trying to do it in CMake:
> 
> cmake_minimum_required(VERSION 2.5)
> project(TEST)
> 
> file(GLOB_RECURSE sources  src/*.f90)
> 
> add_executable(cmake.x ${sources})
> find_library(MY_LAPACK liblapack.a HINTS $ENV{LAPACK_LIB}
> NO_CMAKE_LIBRARY_PATH)
> 
> MESSAGE(STATUS "Lapack location: ${MY_LAPACK}")
> 
> target_link_libraries(cmake.x ${MY_LAPACK} ${MY_ESSL})
> 
> enable_language(Fortran)
> 
> 
> If I run CMake this results in:
> 
> > cmake .
> -- Lapack location: /usr/lib64/liblapack.so
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /work/jias12/jias1217/lapack_test
> 
> 
> How can I force CMake to find the correct library file and not some
> random one laying around on the system?
> 
> 
> Kind regards
> 
> 
> Matthias
> 
> 
> 
> 
> 
> Forschungszentrum Juelich GmbH
> 52425 Juelich
> Sitz der Gesellschaft: Juelich
> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
> Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
> Prof. Dr. Sebastian M. Schmidt
> 
> 
> 
> -- 
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake

-- 

Powered by www.kitware.com

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

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

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

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

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

[CMake] Forcing CMake to find static library

[Matthias Redies]

Hello,

I am trying to force CMAKE to include a specific static lapack library,
set through the environment variable $LAPACK_LIB:

 > ls $LAPACK_LIB
libblas_extra.a  libcblas.a  liblapack.a  liblapacke.a libtmglib.a

 > echo $LAPACK_LIB
/bgsys/local/lapack/3.7.0/lib


This is how I am trying to do it in CMake:

cmake_minimum_required(VERSION 2.5)
project(TEST)

file(GLOB_RECURSE sources  src/*.f90)

add_executable(cmake.x ${sources})
find_library(MY_LAPACK liblapack.a HINTS $ENV{LAPACK_LIB}
NO_CMAKE_LIBRARY_PATH)

MESSAGE(STATUS "Lapack location: ${MY_LAPACK}")

target_link_libraries(cmake.x ${MY_LAPACK} ${MY_ESSL})

enable_language(Fortran)


If I run CMake this results in:

 > cmake .
-- Lapack location: /usr/lib64/liblapack.so
-- Configuring done
-- Generating done
-- Build files have been written to: /work/jias12/jias1217/lapack_test


How can I force CMake to find the correct library file and not some
random one laying around on the system?


Kind regards


Matthias





Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt



--

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] CMake problem with intel parallel studio 2017

[Brad King]

On 06/09/2017 11:51 AM, Mamales, Petros  wrote:
> how is the specification of the toolset (from command line) translates
> to the modules folder in CMake?

The -T option specifies the CMAKE_GENERATOR_TOOLSET:

  https://cmake.org/cmake/help/v3.9/variable/CMAKE_GENERATOR_TOOLSET.html

That value tells the VS generator what to put in the PlatformToolset
field of .vcxproj files.  This influences how the compiler identification
source is compiled, and that uses preprocessor logic to detect the compiler
id and version based on predefined macros.  The resulting compiler id is
used to decide which compiler/platform information modules to load.

-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

Re: [CMake] CMake problem with intel parallel studio 2017

[Mamales, Petros via CMake]

Hi Brad,
Thank you for the one-to-one answers! Much appreciated!
I was afraid of 3) as a reasonable answer. Unfortunately intel PSXE 
installation process has some desirables as a process, and 
things do not always work as intended, hence I was hoping for a workaround.
In case  you would like to oblige even more: how is the specification of the 
toolset (from command line) translates to the modules folder in CMake?
(only if it is not too much to ask).
At any rate, thank you very much again and have a very nice weekend!
Petros

-Original Message-
From: Brad King [mailto:brad.k...@kitware.com] 
Sent: Friday, June 09, 2017 11:01 AM
To: Mamales, Petros [CCC-OT NE]
Cc: CMake
Subject: Re: [CMake] CMake problem with intel parallel studio 2017

On 06/08/2017 03:02 PM, Mamales, Petros  via CMake wrote:
> I try to create Visual Studio 2015 (VS2015) solutions with the intel 
> c++ compiler from Intel Parallel Studio XE (iPSXE) 2017.
> a)  How does the identification of the toolset proceed? (I used the -T 
> command line option)

It works for me like this:

>cmake --version
cmake version 3.9.0-rc2

>cmake ..\src -G "Visual Studio 14 2015" -A x64 -T "Intel C++ Compiler 17.0"
-- The C compiler identification is Intel 17.0.0.20160721
-- Check for working C compiler: C:/Program Files 
(x86)/Intel/SWTools/compilers_and_libraries_2017/windows/bin/intel64/icl.exe
-- Check for working C compiler: C:/Program Files 
(x86)/Intel/SWTools/compilers_and_libraries_2017/windows/bin/intel64/icl.exe -- 
works

This does *not* need to be run at a command prompt with any special environment 
for the compiler.

> 1)  How are these tests really run?

It generates a .vcxproj file with the PlatformToolset field set and then runs 
MSBuild.

> 2)  How is the toolset endowed with the necessary include and link/lib 
> directories (within CMake).

MSBuild takes care of this when running the compiler inside its environment.

> 3)  How can I append more of these directories to "help" the compiler 
> identification and/or attributes discovery?

You shouldn't need to do this, and there isn't really a way to do it.

-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

Re: [CMake] CMake problem with intel parallel studio 2017

[Brad King]

On 06/08/2017 03:02 PM, Mamales, Petros  via CMake wrote:
> I try to create Visual Studio 2015 (VS2015) solutions with the
> intel c++ compiler from Intel Parallel Studio XE (iPSXE) 2017.
> a)  How does the identification of the toolset proceed? (I used the –T 
> command line option)

It works for me like this:

>cmake --version
cmake version 3.9.0-rc2

>cmake ..\src -G "Visual Studio 14 2015" -A x64 -T "Intel C++ Compiler 17.0"
-- The C compiler identification is Intel 17.0.0.20160721
-- Check for working C compiler: C:/Program Files 
(x86)/Intel/SWTools/compilers_and_libraries_2017/windows/bin/intel64/icl.exe
-- Check for working C compiler: C:/Program Files 
(x86)/Intel/SWTools/compilers_and_libraries_2017/windows/bin/intel64/icl.exe -- 
works

This does *not* need to be run at a command prompt with any special environment
for the compiler.

> 1)  How are these tests really run?

It generates a .vcxproj file with the PlatformToolset field set and then
runs MSBuild.

> 2)  How is the toolset endowed with the necessary include and link/lib 
> directories (within CMake).

MSBuild takes care of this when running the compiler inside its environment.

> 3)  How can I append more of these directories to “help” the compiler 
> identification and/or attributes discovery?

You shouldn't need to do this, and there isn't really a way to do it.

-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

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc2-45-g591557b

[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  591557ba450f1f24610ea0eefcb4e1d7665fae25 (commit)
   via  c41a7c7d90e1fca52896dfeb99b7efd717aa6262 (commit)
  from  20df0bcd7026b9209fb8c88052ad637e2559c74f (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=591557ba450f1f24610ea0eefcb4e1d7665fae25
commit 591557ba450f1f24610ea0eefcb4e1d7665fae25
Merge: 20df0bc c41a7c7
Author: Brad King 
AuthorDate: Fri Jun 9 14:36:23 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jun 9 10:36:30 2017 -0400

Merge topic 'file-generate-path-cleanup'

c41a7c7d file: Normalize GENERATE command input and output file paths

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c41a7c7d90e1fca52896dfeb99b7efd717aa6262
commit c41a7c7d90e1fca52896dfeb99b7efd717aa6262
Author: Brad King 
AuthorDate: Thu Jun 8 09:54:37 2017 -0400
Commit: Brad King 
CommitDate: Thu Jun 8 10:41:28 2017 -0400

file: Normalize GENERATE command input and output file paths

Normalize absolute paths so that no extra components like `../` or
`...//...` appear that later confuse relative path computation.
In particular, we expect paths sent to AddCMakeDependFile and
AddCMakeOutputFile to be normalized.

Do this only for paths that are already absolute because
we can't handle relative paths yet (see #16786).

Fixes: #16892

diff --git a/Source/cmGeneratorExpressionEvaluationFile.cxx 
b/Source/cmGeneratorExpressionEvaluationFile.cxx
index 1526454..c21e4f6 100644
--- a/Source/cmGeneratorExpressionEvaluationFile.cxx
+++ b/Source/cmGeneratorExpressionEvaluationFile.cxx
@@ -51,11 +51,15 @@ void cmGeneratorExpressionEvaluationFile::Generate(
 }
   }
 
-  const std::string outputFileName = this->OutputFileExpr->Evaluate(
+  std::string outputFileName = this->OutputFileExpr->Evaluate(
 lg, config, false, CM_NULLPTR, CM_NULLPTR, CM_NULLPTR, lang);
   const std::string outputContent = inputExpression->Evaluate(
 lg, config, false, CM_NULLPTR, CM_NULLPTR, CM_NULLPTR, lang);
 
+  if (cmSystemTools::FileIsFullPath(outputFileName)) {
+outputFileName = cmSystemTools::CollapseFullPath(outputFileName);
+  }
+
   std::map::iterator it =
 outputFiles.find(outputFileName);
 
@@ -111,12 +115,16 @@ void 
cmGeneratorExpressionEvaluationFile::Generate(cmLocalGenerator* lg)
   if (this->InputIsContent) {
 inputContent = this->Input;
   } else {
-lg->GetMakefile()->AddCMakeDependFile(this->Input);
-cmSystemTools::GetPermissions(this->Input.c_str(), perm);
-cmsys::ifstream fin(this->Input.c_str());
+std::string inputFileName = this->Input;
+if (cmSystemTools::FileIsFullPath(inputFileName)) {
+  inputFileName = cmSystemTools::CollapseFullPath(inputFileName);
+}
+lg->GetMakefile()->AddCMakeDependFile(inputFileName);
+cmSystemTools::GetPermissions(inputFileName.c_str(), perm);
+cmsys::ifstream fin(inputFileName.c_str());
 if (!fin) {
   std::ostringstream e;
-  e << "Evaluation file \"" << this->Input << "\" cannot be read.";
+  e << "Evaluation file \"" << inputFileName << "\" cannot be read.";
   lg->IssueMessage(cmake::FATAL_ERROR, e.str());
   return;
 }

---

Summary of changes:
 Source/cmGeneratorExpressionEvaluationFile.cxx |   18 +-
 1 file changed, 13 insertions(+), 5 deletions(-)


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

Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 Win64

[Mamales, Petros via CMake]

Generator:  Visual Studio 14 2015 Win64
Toolset:Intel C++ Compiler 17.0

-Original Message-
From: Robert Maynard [mailto:robert.mayn...@kitware.com] 
Sent: Friday, June 09, 2017 10:26 AM
To: Mamales, Petros [CCC-OT NE]
Cc: Valmiki Rampersad; cmake@cmake.org
Subject: Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 Win64

So to clarify when using the intel compiler what is the exact generator and 
toolset you are specifying to CMake?

On Fri, Jun 9, 2017 at 10:05 AM, Mamales, Petros  
wrote:
> Hi Robert,
> Thank you for your response.
> However, this mail was superseded by another one - actually this being my 
> first email to the mailing list I received notification that it would not get 
> published as I was not yet a member.
> As it turns out, it does find the toolset (I am very curious as to how, 
> actually, as I spent considerable time to second-guess it). However the 
> compiler fails to generate code due to missing libraries when it tries to 
> perform its tests.
> Any idea on how I can provide with extra include/lib directories through 
> CMake to the "tester"(MSBuild?)? (all these happen upon declaration of a 
> project as a c++ one).
> Here is the ouput I get in the error log (copying from my follow-up email):
> Compiling the CXX compiler identification source file 
> "CMakeCXXCompilerId.cpp" failed.
> Compiler:
> Build flags:
> Id flags:
>
> The output was:
> 1
> Microsoft (R) Build Engine version 14.0.25420.1 Copyright (C) 
> Microsoft Corporation. All rights reserved.
>
> Build started 6/8/2017 12:09:12 PM.
> Project 
> "C:\_petros\_dev\math_dev\_build_trees\x64\vc14-intel-17_0_0\CMakeFiles\3.9.0-rc2\CompilerIdCXX\CompilerIdCXX.vcxproj"
>  on node 1 (default targets).
> PrepareForBuild:
>   Creating directory "Debug\".
>   Creating directory "Debug\CompilerIdCXX.tlog\".
> InitializeBuildStatus:
>   Creating "Debug\CompilerIdCXX.tlog\unsuccessfulbuild" because 
> "AlwaysCreate" was specified.
> MessageBuildingWithCompiler:
>   Building with Intel(R) C++ Compiler 17.0
> ClCompile:
>   * ClCompile (x64 - Intel C++)
>   C:\Program Files 
> (x86)\IntelSWTools\compilers_and_libraries_2017.0.109\windows\bin\intel64\icl.exe
>  /c /Qm64 /nologo /W0 /Od /D __INTEL_COMPILER=1700 /D _MBCS /EHsc /RTC1 /MDd 
> /GS /Zc:wchar_t /Zc:forScope /Fo"Debug\\" /Fd"Debug\vc140.pdb" /TP 
> CMakeCXXCompilerId.cpp
>   CMakeCXXCompilerId.cpp
> Link:
>   C:\Program Files 
> (x86)\IntelSWTools\compilers_and_libraries_2017.0.109\windows\bin\inte
> l64\xilink.exe -qm64 /OUT:".\CompilerIdCXX.exe" /INCREMENTAL:NO 
> /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
> advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib 
> odbccp32.lib /MANIFEST /manifest:embed /MANIFESTUAC:"level='asInvoker' 
> uiAccess='false'" /PDB:".\CompilerIdCXX.pdb" /SUBSYSTEM:CONSOLE 
> /TLBID:1 /DYNAMICBASE /NXCOMPAT /IMPLIB:".\CompilerIdCXX.lib" 
> /MACHINE:X64 Debug\CMakeCXXCompilerId.obj LINK : : error LNK1104: 
> cannot open file 'libmmdd.lib' 
> [C:\_petros\_dev\math_dev\_build_trees\x64\vc14-intel-17_0_0\CMakeFile
> s\3.9.0-rc2\CompilerIdCXX\CompilerIdCXX.vcxproj]
> Done Building Project 
> "C:\_petros\_dev\math_dev\_build_trees\x64\vc14-intel-17_0_0\CMakeFiles\3.9.0-rc2\CompilerIdCXX\CompilerIdCXX.vcxproj"
>  (default targets) -- FAILED.
>
> Build FAILED.
>
> Thank you for trying to help,
> Petros
>
> PS: the follow-up email has title:
> CMake problem with intel parallel studio 2017
>
>
>
>
>
> -Original Message-
> From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Robert 
> Maynard
> Sent: Friday, June 09, 2017 8:57 AM
> To: Valmiki Rampersad
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 
> Win64
>
> Hi,
>
> Can you provide the contents of the build directory file 
> CMakeFiles/CMakeError.log . That might help us figure out why the 
> toolset is not found
>
> On Tue, May 30, 2017 at 10:44 PM, Valmiki Rampersad 
>  wrote:
>> I have Visual Studio 2017 Community, with toolsets v141 and v140, installed.
>>
>>
>> If I run 'cmake -G "Visual Studio 15 2017 Win64" -T v141', it 
>> correctly configures and generates the project.
>>
>>
>> However, if I run 'cmake -G "Visual Studio 15 2017 Win64" -T v140' it 
>> returns with the errors "No CMAKE_C_COMPILER could be found" and "No 
>> CMAKE_CXX_COMPILER could be found".
>>
>>
>> I am using CMake 3.8.1. Any help in solving this would be greatly 
>> appreciated!
>>
>>
>> --
>>
>> Powered by
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com
>> =
>> DwICAg=j-EkbjBYwkAB4f8ZbVn1Fw=6_wuzZXSt4ORpgK3tgk-CcUFf9XSS7xAF6v
>> 6
>> 9MPzaXs=3P1PLWvluZuxCLJLeuyiWC2Faruz7Sk2b0TYJMRijCo=3UW1rsfR6g_UG
>> 5
>> 3Giev2lxbJ-pjnyHBWRl3QcozFUvs=
>>
>> Please keep messages on-topic and check the CMake FAQ at:
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cmake.org_Wik
>> i 
>> 

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc2-43-g20df0bc

[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  20df0bcd7026b9209fb8c88052ad637e2559c74f (commit)
   via  b90330f5746aca43c3698c4761bf6c0060afa63e (commit)
   via  7e6e37fdf1bf24194edad6fa8640b7fa8e92e393 (commit)
   via  d4d24c30f0648e45e43835fa104debacae0b4a7f (commit)
   via  994beddb9342423c5b71b45c91bdffc7b0791bf2 (commit)
   via  a0436a2f618b7421e6582cb8f6d3f20a39b1f957 (commit)
   via  dcf559d060fcce32b3a946eecf51d32a3e2cc953 (commit)
   via  5b02bcf682d8ed851f4733c5af61c471cf00296b (commit)
   via  2d1c05c1669efa9eeba6f8606c47f92a3b880920 (commit)
   via  62eec34c291572a684cdbc00d2b296295f589f32 (commit)
  from  9dd1d351fe2cb90e3adbe5cb191f6a3727f78979 (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=20df0bcd7026b9209fb8c88052ad637e2559c74f
commit 20df0bcd7026b9209fb8c88052ad637e2559c74f
Merge: b90330f a0436a2
Author: Brad King 
AuthorDate: Fri Jun 9 14:34:39 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jun 9 10:34:42 2017 -0400

Merge topic 'sdcc-simplify-link-flags'

a0436a2f SDCC: Remove superfluous whitespace from link line
dcf559d0 SDCC: Do not explicitly ask linker to generate Intel Hex files

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b90330f5746aca43c3698c4761bf6c0060afa63e
commit b90330f5746aca43c3698c4761bf6c0060afa63e
Merge: 7e6e37f 994bedd
Author: Brad King 
AuthorDate: Fri Jun 9 14:33:58 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jun 9 10:34:06 2017 -0400

Merge topic 'qt-pass-point-by-value'

994beddb CMakeSetupDialog: Pass QPoint by value

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7e6e37fdf1bf24194edad6fa8640b7fa8e92e393
commit 7e6e37fdf1bf24194edad6fa8640b7fa8e92e393
Merge: d4d24c3 5b02bcf
Author: Brad King 
AuthorDate: Fri Jun 9 14:33:25 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jun 9 10:33:47 2017 -0400

Merge topic 'no-return-void-expression'

5b02bcf6 QtDialog/FirstConfigure: remove 'return' from void expression
2d1c05c1 cmGlobalGenerator: remove 'return' from void expression

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d4d24c30f0648e45e43835fa104debacae0b4a7f
commit d4d24c30f0648e45e43835fa104debacae0b4a7f
Merge: 9dd1d35 62eec34
Author: Brad King 
AuthorDate: Fri Jun 9 14:32:49 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jun 9 10:33:18 2017 -0400

Merge topic 'cpack-destructor-overrides'

62eec34c Add CM_OVERRIDE to CPack generator destructors

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=994beddb9342423c5b71b45c91bdffc7b0791bf2
commit 994beddb9342423c5b71b45c91bdffc7b0791bf2
Author: Daniel Pfeifer 
AuthorDate: Thu Jun 8 22:15:21 2017 +0200
Commit: Daniel Pfeifer 
CommitDate: Thu Jun 8 22:15:21 2017 +0200

CMakeSetupDialog: Pass QPoint by value

diff --git a/Source/QtDialog/CMakeSetupDialog.cxx 
b/Source/QtDialog/CMakeSetupDialog.cxx
index 57f8e10..5290afe 100644
--- a/Source/QtDialog/CMakeSetupDialog.cxx
+++ b/Source/QtDialog/CMakeSetupDialog.cxx
@@ -1195,7 +1195,7 @@ void CMakeSetupDialog::setSearchFilter(const QString& str)
   this->CacheValues->setSearchFilter(str);
 }
 
-void CMakeSetupDialog::doOutputContextMenu(const QPoint& pt)
+void CMakeSetupDialog::doOutputContextMenu(QPoint pt)
 {
   QMenu* menu = this->Output->createStandardContextMenu();
 
diff --git a/Source/QtDialog/CMakeSetupDialog.h 
b/Source/QtDialog/CMakeSetupDialog.h
index 1abdb46..0da28d8 100644
--- a/Source/QtDialog/CMakeSetupDialog.h
+++ b/Source/QtDialog/CMakeSetupDialog.h
@@ -70,7 +70,7 @@ protected slots:
   bool doConfigureInternal();
   bool doGenerateInternal();
   void exitLoop(int);
-  void doOutputContextMenu(const QPoint&);
+  void doOutputContextMenu(QPoint pt);
   void doOutputFindDialog();
   void doOutputFindNext(bool directionForward = true);
   void doOutputFindPrev();

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a0436a2f618b7421e6582cb8f6d3f20a39b1f957
commit a0436a2f618b7421e6582cb8f6d3f20a39b1f957
Author: Reto Schneider 

Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 Win64

[Robert Maynard]

So to clarify when using the intel compiler what is the exact
generator and toolset you are specifying to CMake?

On Fri, Jun 9, 2017 at 10:05 AM, Mamales, Petros
 wrote:
> Hi Robert,
> Thank you for your response.
> However, this mail was superseded by another one - actually this being my 
> first email to the mailing list I received notification that it would not get 
> published as I was not yet a member.
> As it turns out, it does find the toolset (I am very curious as to how, 
> actually, as I spent considerable time to second-guess it). However the 
> compiler fails to generate code due to missing libraries when it tries to 
> perform its tests.
> Any idea on how I can provide with extra include/lib directories through 
> CMake to the "tester"(MSBuild?)? (all these happen upon declaration of a 
> project as a c++ one).
> Here is the ouput I get in the error log (copying from my follow-up email):
> Compiling the CXX compiler identification source file 
> "CMakeCXXCompilerId.cpp" failed.
> Compiler:
> Build flags:
> Id flags:
>
> The output was:
> 1
> Microsoft (R) Build Engine version 14.0.25420.1
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> Build started 6/8/2017 12:09:12 PM.
> Project 
> "C:\_petros\_dev\math_dev\_build_trees\x64\vc14-intel-17_0_0\CMakeFiles\3.9.0-rc2\CompilerIdCXX\CompilerIdCXX.vcxproj"
>  on node 1 (default targets).
> PrepareForBuild:
>   Creating directory "Debug\".
>   Creating directory "Debug\CompilerIdCXX.tlog\".
> InitializeBuildStatus:
>   Creating "Debug\CompilerIdCXX.tlog\unsuccessfulbuild" because 
> "AlwaysCreate" was specified.
> MessageBuildingWithCompiler:
>   Building with Intel(R) C++ Compiler 17.0
> ClCompile:
>   * ClCompile (x64 - Intel C++)
>   C:\Program Files 
> (x86)\IntelSWTools\compilers_and_libraries_2017.0.109\windows\bin\intel64\icl.exe
>  /c /Qm64 /nologo /W0 /Od /D __INTEL_COMPILER=1700 /D _MBCS /EHsc /RTC1 /MDd 
> /GS /Zc:wchar_t /Zc:forScope /Fo"Debug\\" /Fd"Debug\vc140.pdb" /TP 
> CMakeCXXCompilerId.cpp
>   CMakeCXXCompilerId.cpp
> Link:
>   C:\Program Files 
> (x86)\IntelSWTools\compilers_and_libraries_2017.0.109\windows\bin\intel64\xilink.exe
>  -qm64 /OUT:".\CompilerIdCXX.exe" /INCREMENTAL:NO /NOLOGO kernel32.lib 
> user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib 
> ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /MANIFEST 
> /manifest:embed /MANIFESTUAC:"level='asInvoker' uiAccess='false'" 
> /PDB:".\CompilerIdCXX.pdb" /SUBSYSTEM:CONSOLE /TLBID:1 /DYNAMICBASE /NXCOMPAT 
> /IMPLIB:".\CompilerIdCXX.lib" /MACHINE:X64 Debug\CMakeCXXCompilerId.obj
> LINK : : error LNK1104: cannot open file 'libmmdd.lib' 
> [C:\_petros\_dev\math_dev\_build_trees\x64\vc14-intel-17_0_0\CMakeFiles\3.9.0-rc2\CompilerIdCXX\CompilerIdCXX.vcxproj]
> Done Building Project 
> "C:\_petros\_dev\math_dev\_build_trees\x64\vc14-intel-17_0_0\CMakeFiles\3.9.0-rc2\CompilerIdCXX\CompilerIdCXX.vcxproj"
>  (default targets) -- FAILED.
>
> Build FAILED.
>
> Thank you for trying to help,
> Petros
>
> PS: the follow-up email has title:
> CMake problem with intel parallel studio 2017
>
>
>
>
>
> -Original Message-
> From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Robert Maynard
> Sent: Friday, June 09, 2017 8:57 AM
> To: Valmiki Rampersad
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 Win64
>
> Hi,
>
> Can you provide the contents of the build directory file 
> CMakeFiles/CMakeError.log . That might help us figure out why the toolset is 
> not found
>
> On Tue, May 30, 2017 at 10:44 PM, Valmiki Rampersad 
>  wrote:
>> I have Visual Studio 2017 Community, with toolsets v141 and v140, installed.
>>
>>
>> If I run 'cmake -G "Visual Studio 15 2017 Win64" -T v141', it
>> correctly configures and generates the project.
>>
>>
>> However, if I run 'cmake -G "Visual Studio 15 2017 Win64" -T v140' it
>> returns with the errors "No CMAKE_C_COMPILER could be found" and "No
>> CMAKE_CXX_COMPILER could be found".
>>
>>
>> I am using CMake 3.8.1. Any help in solving this would be greatly
>> appreciated!
>>
>>
>> --
>>
>> Powered by
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com=
>> DwICAg=j-EkbjBYwkAB4f8ZbVn1Fw=6_wuzZXSt4ORpgK3tgk-CcUFf9XSS7xAF6v6
>> 9MPzaXs=3P1PLWvluZuxCLJLeuyiWC2Faruz7Sk2b0TYJMRijCo=3UW1rsfR6g_UG5
>> 3Giev2lxbJ-pjnyHBWRl3QcozFUvs=
>>
>> Please keep messages on-topic and check the CMake FAQ at:
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cmake.org_Wiki
>> _CMake-5FFAQ=DwICAg=j-EkbjBYwkAB4f8ZbVn1Fw=6_wuzZXSt4ORpgK3tgk-C
>> cUFf9XSS7xAF6v69MPzaXs=3P1PLWvluZuxCLJLeuyiWC2Faruz7Sk2b0TYJMRijCo
>> =glBhkytNpCUWymoiA2Qm3kGf9KUR51IIk53Rsqu_O3c=
>>
>> Kitware offers various services to support the CMake community. For
>> more information on each offering, please visit:
>>
>> CMake Support:
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__cmake.org_cmake_he
>> 

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc2-33-g9dd1d35

[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  9dd1d351fe2cb90e3adbe5cb191f6a3727f78979 (commit)
   via  7150082aa86223a441575a95e4a50107e22e9a0d (commit)
   via  c8a866b8c47f25ffd5e63e82bf4e501344bf7740 (commit)
   via  ae22079808d708d630dacf3bcd368a123e6bcedf (commit)
   via  522c92d752753089f4bd50552955883a6f005570 (commit)
   via  83784ed18bc2b6edcfb9400c350562356ef554f2 (commit)
   via  43dae6459797ccebc53956050ac058a933b60078 (commit)
  from  55d752b10855f22642dc69fd99a79af6d085831b (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=9dd1d351fe2cb90e3adbe5cb191f6a3727f78979
commit 9dd1d351fe2cb90e3adbe5cb191f6a3727f78979
Merge: 7150082 ae22079
Author: Brad King 
AuthorDate: Fri Jun 9 10:09:22 2017 -0400
Commit: Brad King 
CommitDate: Fri Jun 9 10:09:22 2017 -0400

Merge branch 'release-3.9'


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7150082aa86223a441575a95e4a50107e22e9a0d
commit 7150082aa86223a441575a95e4a50107e22e9a0d
Merge: c8a866b 83784ed
Author: Brad King 
AuthorDate: Fri Jun 9 14:08:22 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jun 9 10:08:26 2017 -0400

Merge topic 'bootstrap-cleanup'

83784ed1 bootstrap: remove leftover empty variable dereference

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c8a866b8c47f25ffd5e63e82bf4e501344bf7740
commit c8a866b8c47f25ffd5e63e82bf4e501344bf7740
Merge: 55d752b 522c92d
Author: Brad King 
AuthorDate: Fri Jun 9 14:06:58 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jun 9 10:07:16 2017 -0400

Merge topic 'FindDoxygen-imported-target-once'

522c92d7 FindDoxygen: Create imported targets at most once in a given scope

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=83784ed18bc2b6edcfb9400c350562356ef554f2
commit 83784ed18bc2b6edcfb9400c350562356ef554f2
Author: Rolf Eike Beer 
AuthorDate: Thu Jun 8 21:19:25 2017 +0200
Commit: Rolf Eike Beer 
CommitDate: Thu Jun 8 21:19:25 2017 +0200

bootstrap: remove leftover empty variable dereference

This was missed in 9c0d1e7531edbebc7943d5b981353b17631ed632 when the for 
loop
that used this as loop variable was removed.

diff --git a/bootstrap b/bootstrap
index 2cf7847..ba2a5f3 100755
--- a/bootstrap
+++ b/bootstrap
@@ -10,7 +10,7 @@ die() {
 cmake_extract_standard_flags()
 {
   sed -n "s/ *set *( *CMAKE_${2}${3}_EXTENSION_COMPILE_OPTION 
*\"\{0,1\}\([^\")]*\).*/\1/p" \
-"${file}" "${cmake_source_dir}/Modules/Compiler/"${1:-*}-${2}.cmake 
2>/dev/null | tr ';' ' '
+"${cmake_source_dir}/Modules/Compiler/"${1:-*}-${2}.cmake 2>/dev/null | tr 
';' ' '
 }
 
 # Version number extraction function.

---

Summary of changes:
 Modules/FindDoxygen.cmake |   40 
 bootstrap |2 +-
 2 files changed, 25 insertions(+), 17 deletions(-)


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

[Cmake-commits] CMake branch, release, updated. v3.9.0-rc2-4-gae22079

[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, release has been updated
   via  ae22079808d708d630dacf3bcd368a123e6bcedf (commit)
   via  522c92d752753089f4bd50552955883a6f005570 (commit)
   via  43dae6459797ccebc53956050ac058a933b60078 (commit)
   via  f44d9bcc8f09c3a135fa0feb82e9d71c475eb196 (commit)
  from  010b50fda71feaff3abec4d13910f4a4bd1f13b0 (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:
 Modules/FindDoxygen.cmake   |   40 +--
 Source/Checks/cm_cxx_features.cmake |4 +++-
 2 files changed, 27 insertions(+), 17 deletions(-)


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

Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 Win64

[Mamales, Petros via CMake]

Hi Robert,
Thank you for your response.
However, this mail was superseded by another one - actually this being my first 
email to the mailing list I received notification that it would not get 
published as I was not yet a member.
As it turns out, it does find the toolset (I am very curious as to how, 
actually, as I spent considerable time to second-guess it). However the 
compiler fails to generate code due to missing libraries when it tries to 
perform its tests.
Any idea on how I can provide with extra include/lib directories through CMake 
to the "tester"(MSBuild?)? (all these happen upon declaration of a project as a 
c++ one).
Here is the ouput I get in the error log (copying from my follow-up email):
Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" 
failed.
Compiler:  
Build flags: 
Id flags:  

The output was:
1
Microsoft (R) Build Engine version 14.0.25420.1
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 6/8/2017 12:09:12 PM.
Project 
"C:\_petros\_dev\math_dev\_build_trees\x64\vc14-intel-17_0_0\CMakeFiles\3.9.0-rc2\CompilerIdCXX\CompilerIdCXX.vcxproj"
 on node 1 (default targets).
PrepareForBuild:
  Creating directory "Debug\".
  Creating directory "Debug\CompilerIdCXX.tlog\".
InitializeBuildStatus:
  Creating "Debug\CompilerIdCXX.tlog\unsuccessfulbuild" because "AlwaysCreate" 
was specified.
MessageBuildingWithCompiler:
  Building with Intel(R) C++ Compiler 17.0
ClCompile:
  * ClCompile (x64 - Intel C++)
  C:\Program Files 
(x86)\IntelSWTools\compilers_and_libraries_2017.0.109\windows\bin\intel64\icl.exe
 /c /Qm64 /nologo /W0 /Od /D __INTEL_COMPILER=1700 /D _MBCS /EHsc /RTC1 /MDd 
/GS /Zc:wchar_t /Zc:forScope /Fo"Debug\\" /Fd"Debug\vc140.pdb" /TP 
CMakeCXXCompilerId.cpp
  CMakeCXXCompilerId.cpp
Link:
  C:\Program Files 
(x86)\IntelSWTools\compilers_and_libraries_2017.0.109\windows\bin\intel64\xilink.exe
 -qm64 /OUT:".\CompilerIdCXX.exe" /INCREMENTAL:NO /NOLOGO kernel32.lib 
user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib 
ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /MANIFEST 
/manifest:embed /MANIFESTUAC:"level='asInvoker' uiAccess='false'" 
/PDB:".\CompilerIdCXX.pdb" /SUBSYSTEM:CONSOLE /TLBID:1 /DYNAMICBASE /NXCOMPAT 
/IMPLIB:".\CompilerIdCXX.lib" /MACHINE:X64 Debug\CMakeCXXCompilerId.obj
LINK : : error LNK1104: cannot open file 'libmmdd.lib' 
[C:\_petros\_dev\math_dev\_build_trees\x64\vc14-intel-17_0_0\CMakeFiles\3.9.0-rc2\CompilerIdCXX\CompilerIdCXX.vcxproj]
Done Building Project 
"C:\_petros\_dev\math_dev\_build_trees\x64\vc14-intel-17_0_0\CMakeFiles\3.9.0-rc2\CompilerIdCXX\CompilerIdCXX.vcxproj"
 (default targets) -- FAILED.

Build FAILED.

Thank you for trying to help,
Petros

PS: the follow-up email has title:
CMake problem with intel parallel studio 2017





-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Robert Maynard
Sent: Friday, June 09, 2017 8:57 AM
To: Valmiki Rampersad
Cc: cmake@cmake.org
Subject: Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 Win64

Hi,

Can you provide the contents of the build directory file 
CMakeFiles/CMakeError.log . That might help us figure out why the toolset is 
not found

On Tue, May 30, 2017 at 10:44 PM, Valmiki Rampersad 
 wrote:
> I have Visual Studio 2017 Community, with toolsets v141 and v140, installed.
>
>
> If I run 'cmake -G "Visual Studio 15 2017 Win64" -T v141', it 
> correctly configures and generates the project.
>
>
> However, if I run 'cmake -G "Visual Studio 15 2017 Win64" -T v140' it 
> returns with the errors "No CMAKE_C_COMPILER could be found" and "No 
> CMAKE_CXX_COMPILER could be found".
>
>
> I am using CMake 3.8.1. Any help in solving this would be greatly 
> appreciated!
>
>
> --
>
> Powered by 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com=
> DwICAg=j-EkbjBYwkAB4f8ZbVn1Fw=6_wuzZXSt4ORpgK3tgk-CcUFf9XSS7xAF6v6
> 9MPzaXs=3P1PLWvluZuxCLJLeuyiWC2Faruz7Sk2b0TYJMRijCo=3UW1rsfR6g_UG5
> 3Giev2lxbJ-pjnyHBWRl3QcozFUvs=
>
> Please keep messages on-topic and check the CMake FAQ at:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cmake.org_Wiki
> _CMake-5FFAQ=DwICAg=j-EkbjBYwkAB4f8ZbVn1Fw=6_wuzZXSt4ORpgK3tgk-C
> cUFf9XSS7xAF6v69MPzaXs=3P1PLWvluZuxCLJLeuyiWC2Faruz7Sk2b0TYJMRijCo
> =glBhkytNpCUWymoiA2Qm3kGf9KUR51IIk53Rsqu_O3c=
>
> Kitware offers various services to support the CMake community. For 
> more information on each offering, please visit:
>
> CMake Support: 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__cmake.org_cmake_he
> lp_support.html=DwICAg=j-EkbjBYwkAB4f8ZbVn1Fw=6_wuzZXSt4ORpgK3tg
> k-CcUFf9XSS7xAF6v69MPzaXs=3P1PLWvluZuxCLJLeuyiWC2Faruz7Sk2b0TYJMRijC
> o=XJtd19WQD61RumQLmDdm3016goUhr-1paAzj8h47_5A=
> CMake Consulting: 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__cmake.org_cmake_he
> lp_consulting.html=DwICAg=j-EkbjBYwkAB4f8ZbVn1Fw=6_wuzZXSt4ORpgK
> 

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc2-26-g55d752b

[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  55d752b10855f22642dc69fd99a79af6d085831b (commit)
   via  f44d9bcc8f09c3a135fa0feb82e9d71c475eb196 (commit)
  from  51e1e23cf477e3918e7b98b7ae14a7041d0734f8 (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=55d752b10855f22642dc69fd99a79af6d085831b
commit 55d752b10855f22642dc69fd99a79af6d085831b
Merge: 51e1e23 f44d9bc
Author: Brad King 
AuthorDate: Fri Jun 9 14:00:41 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jun 9 10:00:57 2017 -0400

Merge topic 'improve-msvc-feature-checks'

f44d9bcc C++ feature checks: Improve exclusion of "0 Warning(s)"

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f44d9bcc8f09c3a135fa0feb82e9d71c475eb196
commit f44d9bcc8f09c3a135fa0feb82e9d71c475eb196
Author: Brad King 
AuthorDate: Thu Jun 8 09:21:21 2017 -0400
Commit: Brad King 
CommitDate: Thu Jun 8 09:22:09 2017 -0400

C++ feature checks: Improve exclusion of "0 Warning(s)"

Simply matching "0 Warning" may match "10 Warning(s)".  Instead remove
the entire `0 Warning(s)` content from the MSBuild output before
searching it for warnings.

Issue: #16942

diff --git a/Source/Checks/cm_cxx_features.cmake 
b/Source/Checks/cm_cxx_features.cmake
index c9a19af..3b08025 100644
--- a/Source/Checks/cm_cxx_features.cmake
+++ b/Source/Checks/cm_cxx_features.cmake
@@ -14,8 +14,10 @@ function(cm_check_cxx_feature name)
   CMAKE_FLAGS ${maybe_cxx_standard}
   OUTPUT_VARIABLE OUTPUT
   )
+# Filter out MSBuild output that looks like a warning.
+string(REGEX REPLACE " +0 Warning\\(s\\)" "" check_output "${OUTPUT}")
 # If using the feature causes warnings, treat it as broken/unavailable.
-if(OUTPUT MATCHES "[Ww]arning" AND NOT OUTPUT MATCHES "0 Warning")
+if(check_output MATCHES "[Ww]arning")
   set(CMake_HAVE_CXX_${FEATURE} OFF CACHE INTERNAL "TRY_COMPILE" FORCE)
 endif()
 if(CMake_HAVE_CXX_${FEATURE})

---

Summary of changes:
 Source/Checks/cm_cxx_features.cmake |4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)


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

Re: [cmake-developers] looking for linkls

[Brad King]

On 06/08/2017 04:34 PM, Bob Burton wrote:
> I'm trying to write autopkg recipes for some of the OS X apps we
> use in our classes.  Any chance you could add dev, latest, and
> previous links to https://cmake.org/files/, corresponding to the
> "Release Candidate", "Latest Release", and "Previous Release"
> links on https://cmake.org/download/?

In order to make the proposal more concrete, please list example
URLs that you would like to see made to work and explain to what
they would link currently.

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] Choosing Toolset v140 for Generator VS 15 2017 Win64

[Robert Maynard]

Hi,

Can you provide the contents of the build directory file
CMakeFiles/CMakeError.log . That might help us figure out why the
toolset is not found

On Tue, May 30, 2017 at 10:44 PM, Valmiki Rampersad
 wrote:
> I have Visual Studio 2017 Community, with toolsets v141 and v140, installed.
>
>
> If I run 'cmake -G "Visual Studio 15 2017 Win64" -T v141', it correctly
> configures and generates the project.
>
>
> However, if I run 'cmake -G "Visual Studio 15 2017 Win64" -T v140' it
> returns with the errors "No CMAKE_C_COMPILER could be found" and "No
> CMAKE_CXX_COMPILER could be found".
>
>
> I am using CMake 3.8.1. Any help in solving this would be greatly
> appreciated!
>
>
> --
>
> 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] my first experiences

[Andrew Bell]

Sounds like you had a bad day.  Hope you have a better one tomorrow.

On Fri, Jun 9, 2017 at 2:40 AM, Xen  wrote:

> I just want to tell you what terrible software CMake is.
>
> The newest version won't compile on my system. The bootstrapping just
> won't complete.
>
> It hangs on 100% CPU while trying to link cmake. Maybe that is a deficit
> of this system.
>
> I take an older version but it needs ncurses. I have ncurses on the system
> but not the headers.
>
> The ncurses source package likes to install headers in a ncurses
> subdirectory. Fine.
>
> But Cmake can't find it.
>
> I specify --prefix=/opt/local.
>
> The headers are in /opt/local/include/ncurses.
>
> At first I find a reference to CURSES_INCLUDE_PATH but setting it as an
> environment variable doesn't do a thing.
>
> There is no help that I can find in the directory structure.
>
> The bootstrap command does not have any help builtin.
>
> I add CURSES_INCLUDE_PATH to Modules/FindCurse.cmake and it finds the
> header but now offset from /ncurses. This causes the header file itself to
> not find its other header files.
>
> The only directory it needs for that is /opt/local/include.
>
> I try to add CMAKE_INCLUDE_PATH on the command line.
> I try to add CMAKE_C_FLAGS on the command line.
>
> But the build system does not tell me what it's doing.
>
> So I am just endlessly waiting several minutes before it errors out again
> and I still don't know why or what would have helped, because it does not
> show me any command lines or directories it has seen fit to use.
>
> This goes on for hours.
>
> This is the first time I have come into contact with Cmake and apparently
> you need to be able to use CMake as a programmer for your own projects,
> before you can get started with cmake.
>
> Then again it errs out:
>
> /store/dev/cmake/Source/CursesDialog/form/form.h:40:20: error: curses.h:
> No such file or directory
>
> Oh, I added a colon as path separator and now it doesn't do anything
> anymore.
>
> So my mistake was to add ncurses at the end of the path but it's not like
> it should have failed using CMAKE_INCLUDE_PATH or CMAKE_C_FLAGS.
>
> Or even that it should not look in that location by default based on
> --prefix.
>
> At first I couldn't compile ncurses; apparently a bug in the system. I
> supplied the fix in CFLAGS but the Makefile of course did not pass it on to
> the file for which it mattered, so I had to even repeat that manually.
>
> Luckily GNU make shows you the command line.
>
> It took me 3 hours to compile version 2.4.0. The latest release candidate
> had been working all night and not proceeding.
>
> Then when I am finally done, it tells me it needs a newer version...
>
> Of course, it doesn't say so in the README.rst...
>
> I wish this endless waste of time would end.
> --
>
> 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/opensou
> rce/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
>



-- 
Andrew Bell
andrew.bell...@gmail.com
-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] my first experiences

[Bo Zhou]

I always compile CMake on Linux but never meet any issues, please make sure
you had installed a complete working Linux development environment, with
g++, libstdc++-devel etc.

The only special thing is just about enabling  GUI with Qt, but that's so
easy, just install the Qt development libraries though apt-get or yum, then
input the parameter from configure, that's all.

On Fri, Jun 9, 2017 at 5:43 PM, Eric Noulard  wrote:

> Hi xen,
>
> Sorry to hear you lost so much time.
> Could you provide us with the version of your system and compiler?
> Did you try any source of precompiled version of CMake either from
> cmake.org or from your favorite system repo? If no why?
> Average CMake user don't ever compile CMake itself.
>
>
>
> Le 9 juin 2017 09:46, "Xen"  a écrit :
>
> I just want to tell you what terrible software CMake is.
>
> The newest version won't compile on my system. The bootstrapping just
> won't complete.
>
> It hangs on 100% CPU while trying to link cmake. Maybe that is a deficit
> of this system.
>
> I take an older version but it needs ncurses. I have ncurses on the system
> but not the headers.
>
> The ncurses source package likes to install headers in a ncurses
> subdirectory. Fine.
>
> But Cmake can't find it.
>
> I specify --prefix=/opt/local.
>
> The headers are in /opt/local/include/ncurses.
>
> At first I find a reference to CURSES_INCLUDE_PATH but setting it as an
> environment variable doesn't do a thing.
>
> There is no help that I can find in the directory structure.
>
> The bootstrap command does not have any help builtin.
>
> I add CURSES_INCLUDE_PATH to Modules/FindCurse.cmake and it finds the
> header but now offset from /ncurses. This causes the header file itself to
> not find its other header files.
>
> The only directory it needs for that is /opt/local/include.
>
> I try to add CMAKE_INCLUDE_PATH on the command line.
> I try to add CMAKE_C_FLAGS on the command line.
>
> But the build system does not tell me what it's doing.
>
> So I am just endlessly waiting several minutes before it errors out again
> and I still don't know why or what would have helped, because it does not
> show me any command lines or directories it has seen fit to use.
>
> This goes on for hours.
>
> This is the first time I have come into contact with Cmake and apparently
> you need to be able to use CMake as a programmer for your own projects,
> before you can get started with cmake.
>
> Then again it errs out:
>
> /store/dev/cmake/Source/CursesDialog/form/form.h:40:20: error: curses.h:
> No such file or directory
>
> Oh, I added a colon as path separator and now it doesn't do anything
> anymore.
>
> So my mistake was to add ncurses at the end of the path but it's not like
> it should have failed using CMAKE_INCLUDE_PATH or CMAKE_C_FLAGS.
>
> Or even that it should not look in that location by default based on
> --prefix.
>
> At first I couldn't compile ncurses; apparently a bug in the system. I
> supplied the fix in CFLAGS but the Makefile of course did not pass it on to
> the file for which it mattered, so I had to even repeat that manually.
>
> Luckily GNU make shows you the command line.
>
> It took me 3 hours to compile version 2.4.0. The latest release candidate
> had been working all night and not proceeding.
>
> Then when I am finally done, it tells me it needs a newer version...
>
> Of course, it doesn't say so in the README.rst...
>
> I wish this endless waste of time would end.
> --
>
> 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/opensou
> rce/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
>
-- 

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 

Re: [CMake] my first experiences

[Eric Noulard]

Hi xen,

Sorry to hear you lost so much time.
Could you provide us with the version of your system and compiler?
Did you try any source of precompiled version of CMake either from cmake.org
or from your favorite system repo? If no why?
Average CMake user don't ever compile CMake itself.



Le 9 juin 2017 09:46, "Xen"  a écrit :

I just want to tell you what terrible software CMake is.

The newest version won't compile on my system. The bootstrapping just won't
complete.

It hangs on 100% CPU while trying to link cmake. Maybe that is a deficit of
this system.

I take an older version but it needs ncurses. I have ncurses on the system
but not the headers.

The ncurses source package likes to install headers in a ncurses
subdirectory. Fine.

But Cmake can't find it.

I specify --prefix=/opt/local.

The headers are in /opt/local/include/ncurses.

At first I find a reference to CURSES_INCLUDE_PATH but setting it as an
environment variable doesn't do a thing.

There is no help that I can find in the directory structure.

The bootstrap command does not have any help builtin.

I add CURSES_INCLUDE_PATH to Modules/FindCurse.cmake and it finds the
header but now offset from /ncurses. This causes the header file itself to
not find its other header files.

The only directory it needs for that is /opt/local/include.

I try to add CMAKE_INCLUDE_PATH on the command line.
I try to add CMAKE_C_FLAGS on the command line.

But the build system does not tell me what it's doing.

So I am just endlessly waiting several minutes before it errors out again
and I still don't know why or what would have helped, because it does not
show me any command lines or directories it has seen fit to use.

This goes on for hours.

This is the first time I have come into contact with Cmake and apparently
you need to be able to use CMake as a programmer for your own projects,
before you can get started with cmake.

Then again it errs out:

/store/dev/cmake/Source/CursesDialog/form/form.h:40:20: error: curses.h: No
such file or directory

Oh, I added a colon as path separator and now it doesn't do anything
anymore.

So my mistake was to add ncurses at the end of the path but it's not like
it should have failed using CMAKE_INCLUDE_PATH or CMAKE_C_FLAGS.

Or even that it should not look in that location by default based on
--prefix.

At first I couldn't compile ncurses; apparently a bug in the system. I
supplied the fix in CFLAGS but the Makefile of course did not pass it on to
the file for which it mattered, so I had to even repeat that manually.

Luckily GNU make shows you the command line.

It took me 3 hours to compile version 2.4.0. The latest release candidate
had been working all night and not proceeding.

Then when I am finally done, it tells me it needs a newer version...

Of course, it doesn't say so in the README.rst...

I wish this endless waste of time would end.
-- 

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/opensou
rce/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] my first experiences

[Raymond Wan]

Hi Xen,


On Fri, Jun 9, 2017 at 3:40 PM, Xen  wrote:
> I just want to tell you what terrible software CMake is.
>
> The newest version won't compile on my system. The bootstrapping just won't
> complete.


Just out of curiosity but is there any reason why you need the "latest
version"?  I usually use the default version for my OS (3.6.3 on
Ubuntu, currently) and it is usually good enough for my needs.


> It took me 3 hours to compile version 2.4.0. The latest release candidate
> had been working all night and not proceeding.


The latest version of CMake is 3.9.0-rc2...

Perhaps others on this mailing list can help you with your specific
problems but I've used CMake off and on for many years and never
compiled it myself.  I've always relied on the Ubuntu package.  It's
older but usually good enough since the features I need are fairly
basic...

Good luck with it and sorry to hear you're having problems!

Ray
-- 

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] my first experiences

[Xen]

I just want to tell you what terrible software CMake is.

The newest version won't compile on my system. The bootstrapping just 
won't complete.


It hangs on 100% CPU while trying to link cmake. Maybe that is a deficit 
of this system.


I take an older version but it needs ncurses. I have ncurses on the 
system but not the headers.


The ncurses source package likes to install headers in a ncurses 
subdirectory. Fine.


But Cmake can't find it.

I specify --prefix=/opt/local.

The headers are in /opt/local/include/ncurses.

At first I find a reference to CURSES_INCLUDE_PATH but setting it as an 
environment variable doesn't do a thing.


There is no help that I can find in the directory structure.

The bootstrap command does not have any help builtin.

I add CURSES_INCLUDE_PATH to Modules/FindCurse.cmake and it finds the 
header but now offset from /ncurses. This causes the header file itself 
to not find its other header files.


The only directory it needs for that is /opt/local/include.

I try to add CMAKE_INCLUDE_PATH on the command line.
I try to add CMAKE_C_FLAGS on the command line.

But the build system does not tell me what it's doing.

So I am just endlessly waiting several minutes before it errors out 
again and I still don't know why or what would have helped, because it 
does not show me any command lines or directories it has seen fit to 
use.


This goes on for hours.

This is the first time I have come into contact with Cmake and 
apparently you need to be able to use CMake as a programmer for your own 
projects, before you can get started with cmake.


Then again it errs out:

/store/dev/cmake/Source/CursesDialog/form/form.h:40:20: error: curses.h: 
No such file or directory


Oh, I added a colon as path separator and now it doesn't do anything 
anymore.


So my mistake was to add ncurses at the end of the path but it's not 
like it should have failed using CMAKE_INCLUDE_PATH or CMAKE_C_FLAGS.


Or even that it should not look in that location by default based on 
--prefix.


At first I couldn't compile ncurses; apparently a bug in the system. I 
supplied the fix in CFLAGS but the Makefile of course did not pass it on 
to the file for which it mattered, so I had to even repeat that 
manually.


Luckily GNU make shows you the command line.

It took me 3 hours to compile version 2.4.0. The latest release 
candidate had been working all night and not proceeding.


Then when I am finally done, it tells me it needs a newer version...

Of course, it doesn't say so in the README.rst...

I wish this endless waste of time would end.
--

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] [ANN] CMake Training Course - October 9

[Julien Jomier]

Kitware will be holding a CMake training course on October 9, 2017 in 
Lyon, France. This one-day course will cover CMake, CTest, CPack and CDash.


Please visit our website for more information and registration details:

https://training.kitware.fr/browse/153

Note that the course will be taught in English. If you have any
questions, please contact us at training at kitware.fr or email me directly.

We are looking forward to seeing you in Lyon,
Julien
--
Kitware SAS
26 rue Louis Guérin
69100 Villeurbanne, France
http://www.kitware.eu
--

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