[Cmake-commits] CMake branch, master, updated. v3.7.1-908-g4918cd8

2016-12-19 Thread Kitware Robot 
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  4918cd8c98938ab245d7fea74ba6e20f3ec8ef8b (commit)
  from  3657ac9fbb6bf6cd82bf9a0119fd989ab3f4f704 (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=4918cd8c98938ab245d7fea74ba6e20f3ec8ef8b
commit 4918cd8c98938ab245d7fea74ba6e20f3ec8ef8b
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Tue Dec 20 00:01:04 2016 -0500
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Tue Dec 20 00:01:04 2016 -0500

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 668765c..ad92a62 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 7)
-set(CMake_VERSION_PATCH 20161219)
+set(CMake_VERSION_PATCH 20161220)
 #set(CMake_VERSION_RC 1)

---

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


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

Re: [CMake] What are the missing features in Ninja that CMake needs?

2016-12-19 Thread Bill Hoffman 

On 12/18/2016 8:57 AM, David Cole via CMake wrote:

This "compare" view on GitHub shows the difference between the
regular/upstream ninja and the Kitware patched ninja:


https://github.com/ninja-build/ninja/compare/master...Kitware:features-for-fortran

The ReadMe explains the high-level view, and says it is gradually
being worked into upstream ninja.

It has to do with Fortran modules. These are sort of "include" files 
that are automatically generated by the Fortran compiler.  So, there is 
a specific order in which Fortran source files must be compiled so that 
files that include exist before they try to include them.


For some examples see this cmake test case:

https://gitlab.kitware.com/cmake/cmake/tree/master/Tests/FortranModules

It will not pass with upstream ninja.

-Bill

--

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] 'No known features for CXX compiler' warning with custom Clang

2016-12-19 Thread Robert Maynard 
Are you able to send me the CMakeError.log and CMakeOutput.log from
your build/CMakeFiles/ directory.

On Mon, Dec 19, 2016 at 4:51 AM, James Turner  wrote:
>
>> On 16 Dec 2016, at 22:59, Robert Maynard  wrote:
>>
>> That is odd. Inside your build/CMakeFiles should be a file called
>> feature_tests.cxx, and that file is how we determine what features the
>> clang compiler supports.
>>
>> I would use that to determine why feature detection is failing, since
>> currently it believes that none of the features listed in it are
>> valid.
>>
>> Now if the file is empty, that means we are looking at a CMake logic
>> bug somewhere before this.
>
> In my case there is no feature_tests.cxx generated at all.
>
> Kind regards,
> James
>
> --
> James Turner - Senior Software Developer
> KDAB - The Qt, C++ and OpenGL Experts
>
>
>
>
-- 

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 3.7.0-r2 Open Project sometimes picks wrong version of Visual Studio

2016-12-19 Thread John Drescher 
On Tue, Nov 8, 2016 at 10:28 AM,   wrote:
>
>
> - On Nov 8, 2016, at 8:13 AM, Taylor Braun-Jones tay...@braun-jones.org 
> wrote:
>
>> On Fri, Nov 4, 2016 at 2:55 PM, Brad King  wrote:
>>>
>>> On 11/03/2016 06:04 PM, John Drescher wrote:
>>> > I opened a project in cmake-gui using the open project button from a
>>> > vc 2010 build of a project. The open project opened the project in
>>> > Visual Studio 2010. Later I opened the same project but a different
>>> > build tree for Visual Studio 2013 CMake-gui had all of the correct
>>> > information for the Visual Studio 2013 build but open project tried to
>>> > open the Visual Studio 2013 solution in Visual Studio 2010 instead of
>>> > the expected Visual Studio 2013.
>
> I'm unable to reproduce this problem.  I have multiple Visual Studio 
> installations of different versions.
> I'm not sure whether it could be specific to a project, or specific to 
> installations of visual studio.
>
>>
>> I'm guessing you established MSVS2010 as the default application for
>> opening .sln files the first time you used the open project button.
>> What happens if you double click on that MSVS2013 .sln file?

Sorry for the delay. I went on vacation a few days after emailing
about this issue then forgot to check back when I returned.. If I
click on a .sln it picks the wrong version of Visual Studio as well so
this is not a CMake issue.

Thanks,
John
-- 

Powered by www.kitware.com

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

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

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

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

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1825-g934289d

2016-12-19 Thread Rolf Eike Beer 
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, next has been updated
   via  934289dd5dce80d4f8e53b5dfdb3c300e3dbf5b2 (commit)
   via  f3b3644c4fed7915bb6774929af5766ed1809054 (commit)
   via  3657ac9fbb6bf6cd82bf9a0119fd989ab3f4f704 (commit)
   via  77468c751f62c4dfa64fb60c5f4336a8534aec85 (commit)
  from  0fdba25baabb8f32141a6ebc854ad8cd9f4a646c (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=934289dd5dce80d4f8e53b5dfdb3c300e3dbf5b2
commit 934289dd5dce80d4f8e53b5dfdb3c300e3dbf5b2
Merge: 0fdba25 f3b3644
Author: Rolf Eike Beer 
AuthorDate: Mon Dec 19 08:47:33 2016 -0500
Commit: CMake Topic Stage 
CommitDate: Mon Dec 19 08:47:33 2016 -0500

Merge topic 'sparc-libatomic' into next

f3b3644c explicitely link against libatomic on Linux/sparc for 
__atomic_fetch_add_4()
3657ac9f CMake Nightly Date Stamp
77468c75 CMake Nightly Date Stamp


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f3b3644c4fed7915bb6774929af5766ed1809054
commit f3b3644c4fed7915bb6774929af5766ed1809054
Author: Rolf Eike Beer 
AuthorDate: Mon Dec 19 14:47:01 2016 +0100
Commit: Rolf Eike Beer 
CommitDate: Mon Dec 19 14:47:01 2016 +0100

explicitely link against libatomic on Linux/sparc for __atomic_fetch_add_4()

diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt
index d15fdbe..7342524 100644
--- a/Source/CMakeLists.txt
+++ b/Source/CMakeLists.txt
@@ -785,6 +785,15 @@ target_link_libraries(CMakeLib cmsys
   ${CMake_KWIML_LIBRARIES}
   )
 
+if(CMAKE_SYSTEM_NAME STREQUAL "Linux" AND CMAKE_SYSTEM_PROCESSOR STREQUAL 
"sparc")
+  # the atomic instructions are implemented using libatomic on some platforms,
+  # so linking to that may be required
+  check_library_exists(atomic __atomic_fetch_add_4 "" LIBATOMIC_NEEDED)
+  if(LIBATOMIC_NEEDED)
+target_link_libraries(CMakeLib atomic)
+  endif()
+endif()
+
 # On Apple we need CoreFoundation
 if(APPLE)
   target_link_libraries(CMakeLib "-framework CoreFoundation")

---

Summary of changes:
 Source/CMakeLists.txt |9 +
 Source/CMakeVersion.cmake |2 +-
 2 files changed, 10 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] 'No known features for CXX compiler' warning with custom Clang

2016-12-19 Thread James Turner 

> On 16 Dec 2016, at 22:59, Robert Maynard  wrote:
> 
> That is odd. Inside your build/CMakeFiles should be a file called
> feature_tests.cxx, and that file is how we determine what features the
> clang compiler supports.
> 
> I would use that to determine why feature detection is failing, since
> currently it believes that none of the features listed in it are
> valid.
> 
> Now if the file is empty, that means we are looking at a CMake logic
> bug somewhere before this.

In my case there is no feature_tests.cxx generated at all. 

Kind regards,
James

--
James Turner - Senior Software Developer
KDAB - The Qt, C++ and OpenGL Experts






smime.p7s
Description: S/MIME cryptographic signature
-- 

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] (no subject)

2016-12-19 Thread Bo Zhou 
Hi,

I'm using ExternalProject_Add to handle this situation with multiple
platforms/targets.

https://cmake.org/cmake/help/v3.7/module/ExternalProject.html

Hope this works for you.

On Mon, Dec 19, 2016 at 1:41 AM, Harshal Singhal  wrote:

> Hello,
>
> I have a VS2013 project with (many sub-projects)many targets (say a b c
> d) in different locations, which all are generated using CMake.  I am
> using one top-level CMakeLists with commadadd_subdirectoriesand a
> CMakeLists file in each of those sub directories. So, Each sub-directory
> has a single target.
>
>  Now, Problem is - I want to change "Platform Toolset" only in one
> (sub-directory) targets (say b) from v120 to v90.
>
> I have tried the following commands in my CMakeLists.txt for that
> particular target (say b) but none of them seem to work: Please help
>
> set(CMAKE_VS_PLATFORM_TOOLSET "v90")
> set(CMAKE_GENERATOR_TOOLSET "v90")
>
> or
>
> add_definitions (-DCMAKE_VS_PLATFORM_TOOLSET = "v90")
> add_definitions (-DMAKE_GENERATOR_TOOLSET = "v90")
>
> or
>
> set_target_properties (b PROPERTIES PLATFORM_TOOLSET "v90")
>
> After trying these command - VS2013 shows the "platform toolset " as
> "v120" for "b target". Maybe it is possible with command line with -T
> option but I want to change the toolset for only one target not for the
> whole project. Any ideas how to solve this problem? or please let me know
> if it is not clear..but please help
>
> --
> Regards
> Harshal Singhal
>
> --
>
> 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