date:20170315

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-494-gf1e9873

2017-03-15 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, next has been updated
  discards  925b2149727b556f0df6873c1b60dafe466dcf59 (commit)
  discards  af21531a8fa644afa2e7da0a27a90f16598597a3 (commit)
  discards  8f5ab42a983169de44fcadc5272e059a512bdf8d (commit)
   via  f1e9873dc41d23956ae3b01526172e16cb64ed38 (commit)
   via  62e8eb5fd0c53a5b997c8ab274ad408e85326016 (commit)
   via  69f8e7bf82d93eff2610ab8dc14d22dd8f77b2c4 (commit)
   via  e781223c8887fa2602b40744c67cdc77f972a93b (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (925b2149727b556f0df6873c1b60dafe466dcf59)
\
 N -- N -- N (f1e9873dc41d23956ae3b01526172e16cb64ed38)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

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=f1e9873dc41d23956ae3b01526172e16cb64ed38
commit f1e9873dc41d23956ae3b01526172e16cb64ed38
Merge: 62e8eb5 16d114e
Author: Ben Boeckel 
AuthorDate: Wed Mar 15 13:09:45 2017 +
Commit: Kitware Robot 
CommitDate: Thu Mar 16 00:01:26 2017 -0400

Stage topic 'geh-visibility-flag'

Topic-id: 17427
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/36


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=62e8eb5fd0c53a5b997c8ab274ad408e85326016
commit 62e8eb5fd0c53a5b997c8ab274ad408e85326016
Merge: 69f8e7b 4b49c9a
Author: Daniel Pfeifer 
AuthorDate: Tue Mar 14 22:25:55 2017 +
Commit: Kitware Robot 
CommitDate: Thu Mar 16 00:01:26 2017 -0400

Stage topic 'windows-include-order'

Topic-id: 23061
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/584


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=69f8e7bf82d93eff2610ab8dc14d22dd8f77b2c4
commit 69f8e7bf82d93eff2610ab8dc14d22dd8f77b2c4
Merge: e781223 598400a
Author: do-m-en 
AuthorDate: Tue Mar 14 06:52:24 2017 +
Commit: Kitware Robot 
CommitDate: Thu Mar 16 00:01:26 2017 -0400

Stage topic 'cpack-rpm-extra-slash-in-path'

Topic-id: 23038
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/583


---

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-commits] CMake branch, master, updated. v3.8.0-rc2-488-ge781223

2017-03-15 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  e781223c8887fa2602b40744c67cdc77f972a93b (commit)
  from  b557f3e106274cfb4a08a48d2dd3b6d4f3f67bb7 (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:
 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-commits] CMake branch, nightly-master, updated. v3.8.0-rc2-487-gb557f3e

2017-03-15 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, nightly-master has been updated
   via  b557f3e106274cfb4a08a48d2dd3b6d4f3f67bb7 (commit)
  from  4d3f120c5fec71b12e8d1cab1e509e2545012475 (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:
 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-commits] CMake branch, nightly, updated. v3.8.0-rc2-493-g925b214

2017-03-15 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, nightly has been updated
  discards  63a718a5b0780c7e71974a75cd944956b694f280 (commit)
  discards  c553e117d5c0d8111e3f4e75ebf6706a0fa0e04d (commit)
   via  925b2149727b556f0df6873c1b60dafe466dcf59 (commit)
   via  af21531a8fa644afa2e7da0a27a90f16598597a3 (commit)
   via  8f5ab42a983169de44fcadc5272e059a512bdf8d (commit)
   via  b557f3e106274cfb4a08a48d2dd3b6d4f3f67bb7 (commit)
   via  16d114e3126fcf06d33e734d074dcd4f5542e074 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (63a718a5b0780c7e71974a75cd944956b694f280)
\
 N -- N -- N (925b2149727b556f0df6873c1b60dafe466dcf59)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

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/GenerateExportHeader.cmake |8 ++--
 Source/CMakeVersion.cmake  |2 +-
 Tests/RunCMake/GenerateExportHeader/GEH.cmake  |4 +-
 .../UNIX_DeprecatedOnly/libshared_export.h |   42 
 .../UNIX_DeprecatedOnly/libstatic_export.h |   42 
 5 files changed, 6 insertions(+), 92 deletions(-)
 delete mode 100644 
Tests/RunCMake/GenerateExportHeader/reference/UNIX_DeprecatedOnly/libshared_export.h
 delete mode 100644 
Tests/RunCMake/GenerateExportHeader/reference/UNIX_DeprecatedOnly/libstatic_export.h


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

[CMake] Question regarding CUDA support in CMake 3.8.0-rc2

2017-03-15 Thread Nick Henderson

Hello!

I am testing out the CUDA support in CMake 3.8.0-rc2.

When running `make VERBOSE=1` in the build directory, I get a warning
generated related to the GPU architecture flags for nvcc:

```
[ 80%] Linking CUDA device code
/home/nwh/git/foobar/build/exec/CMakeFiles/exec.dir/cmake_device_link.o
cd /home/nwh/git/foobar/build/exec && /usr/local/bin/cmake -E
cmake_link_script CMakeFiles/exec.dir/dlink.txt --verbose=1
/usr/local/cuda/bin/nvcc   -Xcompiler=-fPIC -shared -dlink
CMakeFiles/exec.dir/exec.cc.o -o CMakeFiles/exec.dir/cmake_device_link.o
../libfoobar.a 
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are
deprecated, and may be removed in a future release (Use
-Wno-deprecated-gpu-targets to suppress warning).
```

I don't get the warning when the executable source is being compiled because
an up-to-date architecture is specified:

```
[ 60%] Building CUDA object exec/CMakeFiles/exec.dir/exec.cc.o
cd /home/nwh/git/foobar/build/exec && /usr/local/cuda/bin/nvcc  
-I/home/nwh/git/foobar  -arch compute_30 -std=c++11 -x cu -c
/home/nwh/git/foobar/exec/exec.cc -o CMakeFiles/exec.dir/exec.cc.o
```

Link to sample project: https://github.com/nwh/foobar

Questions:

* Is this a problem?
* What is the purpose of cmake_device_link.o?

Thanks,
Nick



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/Question-regarding-CUDA-support-in-CMake-3-8-0-rc2-tp7595171.html
Sent from the CMake mailing list archive at Nabble.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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-493-g925b214

2017-03-15 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, next has been updated
   via  925b2149727b556f0df6873c1b60dafe466dcf59 (commit)
   via  16d114e3126fcf06d33e734d074dcd4f5542e074 (commit)
  from  af21531a8fa644afa2e7da0a27a90f16598597a3 (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=925b2149727b556f0df6873c1b60dafe466dcf59
commit 925b2149727b556f0df6873c1b60dafe466dcf59
Merge: af21531 16d114e
Author: Ben Boeckel 
AuthorDate: Wed Mar 15 13:09:45 2017 +
Commit: Kitware Robot 
CommitDate: Wed Mar 15 09:09:50 2017 -0400

Stage topic 'geh-visibility-flag'

Topic-id: 17427
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/36


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=16d114e3126fcf06d33e734d074dcd4f5542e074
commit 16d114e3126fcf06d33e734d074dcd4f5542e074
Author: Ben Boeckel 
AuthorDate: Mon Jul 11 14:52:05 2016 -0400
Commit: Ben Boeckel 
CommitDate: Tue Mar 14 12:08:37 2017 -0400

GenerateExportHeader: always fill in _EXPORT macros

The `_EXPORT` and `_NO_EXPORT` macros should always be made properly
because the `_VISIBILITY_PRESET` properties are controlled
independently of this module.

One case where this breaks compatibility is where a project was setting
`USE_COMPILER_HIDDEN_VISIBILITY=OFF` and then marking a symbol used
outside of the library with `_NO_EXPORT` which is a contridiction.

diff --git a/Modules/GenerateExportHeader.cmake 
b/Modules/GenerateExportHeader.cmake
index 6d1b4ed..4573c2e 100644
--- a/Modules/GenerateExportHeader.cmake
+++ b/Modules/GenerateExportHeader.cmake
@@ -215,9 +215,6 @@ macro(_test_compiler_hidden_visibility)
 check_cxx_compiler_flag(-fvisibility=hidden COMPILER_HAS_HIDDEN_VISIBILITY)
 check_cxx_compiler_flag(-fvisibility-inlines-hidden
   COMPILER_HAS_HIDDEN_INLINE_VISIBILITY)
-option(USE_COMPILER_HIDDEN_VISIBILITY
-  "Use HIDDEN visibility support if available." ON)
-mark_as_advanced(USE_COMPILER_HIDDEN_VISIBILITY)
   endif()
 endmacro()
 
@@ -267,7 +264,7 @@ macro(_DO_SET_MACRO_VALUES TARGET_LIBRARY)
 if(WIN32 OR CYGWIN)
   set(DEFINE_EXPORT "__declspec(dllexport)")
   set(DEFINE_IMPORT "__declspec(dllimport)")
-elseif(COMPILER_HAS_HIDDEN_VISIBILITY AND USE_COMPILER_HIDDEN_VISIBILITY)
+elseif(COMPILER_HAS_HIDDEN_VISIBILITY)
   set(DEFINE_EXPORT "__attribute__((visibility(\"default\")))")
   set(DEFINE_IMPORT "__attribute__((visibility(\"default\")))")
   set(DEFINE_NO_EXPORT "__attribute__((visibility(\"hidden\")))")
@@ -388,6 +385,9 @@ function(add_compiler_export_flags)
   _test_compiler_hidden_visibility()
   _test_compiler_has_deprecated()
 
+  option(USE_COMPILER_HIDDEN_VISIBILITY
+"Use HIDDEN visibility support if available." ON)
+  mark_as_advanced(USE_COMPILER_HIDDEN_VISIBILITY)
   if(NOT (USE_COMPILER_HIDDEN_VISIBILITY AND COMPILER_HAS_HIDDEN_VISIBILITY))
 # Just return if there are no flags to add.
 return()
diff --git a/Tests/RunCMake/GenerateExportHeader/GEH.cmake 
b/Tests/RunCMake/GenerateExportHeader/GEH.cmake
index cddba29..4d5059d 100644
--- a/Tests/RunCMake/GenerateExportHeader/GEH.cmake
+++ b/Tests/RunCMake/GenerateExportHeader/GEH.cmake
@@ -110,10 +110,8 @@ if (WIN32 OR CYGWIN)
   else()
 set(_platform WinEmpty)
   endif()
-elseif(COMPILER_HAS_HIDDEN_VISIBILITY AND USE_COMPILER_HIDDEN_VISIBILITY)
+elseif(COMPILER_HAS_HIDDEN_VISIBILITY)
   set(_platform UNIX)
-elseif(COMPILER_HAS_DEPRECATED)
-  set(_platform UNIX_DeprecatedOnly)
 else()
   set(_platform Empty)
 endif()
diff --git 
a/Tests/RunCMake/GenerateExportHeader/reference/UNIX_DeprecatedOnly/libshared_export.h
 
b/Tests/RunCMake/GenerateExportHeader/reference/UNIX_DeprecatedOnly/libshared_export.h
deleted file mode 100644
index 808ff01..000
--- 
a/Tests/RunCMake/GenerateExportHeader/reference/UNIX_DeprecatedOnly/libshared_export.h
+++ /dev/null
@@ -1,42 +0,0 @@
-
-#ifndef LIBSHARED_EXPORT_H
-#define LIBSHARED_EXPORT_H
-
-#ifdef LIBSHARED_STATIC_DEFINE
-#  define LIBSHARED_EXPORT
-#  define LIBSHARED_NO_EXPORT
-#else
-#  ifndef LIBSHARED_EXPORT
-#ifdef libshared_EXPORTS
-/* We are building this library */
-#  define LIBSHARED_EXPORT
-#else
-/* We are using this library */
-#  define LIBSHARED_EXPORT
-#endif
-#  endif
-
-#  ifndef LIBSHARED_NO_EXPORT
-#define LIBSHARED_NO_EXPORT
-#  endif
-#endif
-
-#ifndef LIBSHARED_DEPRECATED
-#  define LIBSHARED_DEPRECATED __attribute__ ((__deprecated__))
-#endif
-
-#ifndef

Re: [CMake] CHECK_INCLUDE_FILE_CXX with built from source compiler

2017-03-15 Thread houssen


For the record, the solution is (try_compile needs this option):
SET(CMAKE_REQUIRED_FLAGS "-std=c++11")

Is there a way to get this flag whatever the compiler to do this ? 
[SET_TARGET_PROPERTIES(myTarget PROPERTIES CXX_STANDARD 11) seems to be 
relevant only for target - flags are not available]


Franck

Le 2017-03-13 19:36, houssen a écrit :

Forgot to mention:

~> cmake --version
cmake version 3.5.0


Le 2017-03-13 19:33, houssen a écrit :

Hello,

I do NOT use /usr/bin/g++ that is installed in the system (long 
story

- don't ask why).
I compiled gcc from source and installed it in 
/my/path/local/bin/g++.


Now I need to check for tuple with CHECK_INCLUDE_FILE_CXX : it fails 
!


Still failing if:
1. I export CPLUS_INCLUDE_PATH to point at
/my/path/local/include/c++/x.y.z (I checked: tuple is here)
2. set this before calling CHECK_INCLUDE_FILE_CXX :
  SET ( CMAKE_REQUIRED_FLAGS "-I$ENV{CPLUS_INCLUDE_PATH}" )
  SET ( CMAKE_REQUIRED_INCLUDES "$ENV{CPLUS_INCLUDE_PATH}" )

What is wrong ?

Franck


--

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] Is it possible to patch a make project with CMakeLists.txt, through external_project_add?

2017-03-15 Thread mike lojkovic

So, I'm trying to get my project to work on Windows, as well as Linux.
Currently, everything compiles fine on Linux. I've gotten it to
compile in the past on Windows, but since then have reinstalled
Windows, and forgotten the precise steps needed to manually setup Lua,
so CMake can find it. So, I assume just add Lua to my project with
ExternalProject_Add, but they use make and the makefil is configured
for Linux.

The two options I have are either patch their makefile to build
correctly through cygwin, (I'm just worried this might lead to issues
with producing a binary requiring cygwin) or add a CMakeLists.txt file
and patch it in after the download ends. How would I go about adding
custom CMakeLists.txt file to their project after the download
finishes?
-- 

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.8.0-rc2-494-gf1e9873

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-488-ge781223

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc2-487-gb557f3e

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc2-493-g925b214

[CMake] Question regarding CUDA support in CMake 3.8.0-rc2

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-493-g925b214

Re: [CMake] CHECK_INCLUDE_FILE_CXX with built from source compiler

[CMake] Is it possible to patch a make project with CMakeLists.txt, through external_project_add?

8 matches

Site Navigation

Mail list logo

Footer information