[Cmake-commits] CMake branch, master, updated. v3.8.0-829-g1b0c7bc

2017-04-20 Thread Kitware Robot
_VERSION_MINOR 8) -set(CMake_VERSION_PATCH 20170420) +set(CMake_VERSION_PATCH 20170421) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Overriding the include path, library path of OpenSSL, Zlib and libcurl

2017-04-20 Thread Michael Ellery
It doesn’t look like that find module directly supports HINTS or PATHS, so you can try setting CMAKE_LIBRARY_PATH and CMAKE_INCLUDE_PATH (https://cmake.org/cmake/help/v3.7/variable/CMAKE_LIBRARY_PATH.html) before calling the curl finder. I think you can add to those variables whatever paths

[CMake] Overriding the include path, library path of OpenSSL, Zlib and libcurl

2017-04-20 Thread Alex Chen
The source code I want to compile on Linux uses ‘FindOpenSSL’, ‘FindZLIB’, and ‘FindCURL’ to resolve the paths of these libraries. However, I have newer version of these libraries in different locations.  How to I override these to use my paths? I am able to use OPENSSL_ROOT_DIR, from

Re: [CMake] How to set C++ standard?

2017-04-20 Thread Alex Chen
Thanks.  I find the problem in the source code where it uses CPP_STANDARD as suffix in –std=c++, therefore I should set CPP_STANDARD instead of the other one. Alex Chen From: Craig Scott Date: Thursday, April 20, 2017 at 4:41 PM To: Alex Chen

[CMake] dependency on external libraries (and Visual Studio)

2017-04-20 Thread Kris Thielemans
Hi I have a project with a shared library that depends on some external static libraries. Those are CMake imported targets. It appears that my shared library does not get rebuild when the external libraries are updated. (It would need to be relinked). Is this expected? A bit more info on

Re: [CMake] How to set C++ standard?

2017-04-20 Thread Craig Scott
You generally shouldn't set CMAKE_CXX_STANDARD on its own, you should also be explicitly setting CMAKE_CXX_STANDARD_REQUIRED and CMAKE_CXX_EXTENSIONS to ensure you are getting the behaviour you want. These would also typically be set by the project's own CMakeLists.txt file rather than being

[CMake] How to set C++ standard?

2017-04-20 Thread Alex Chen
I tried to set the compiler flag –std=c++14 via cmake command line on Linux with –DCMAKE_CXX_STANDARD=14.  The message from ‘make’ shows   -std=c++11 –std=gnu++14 If I do not set that flag, I get -std=c++11.  This seem to imply the CMAKE_CXX_STANDARD flag sets gnu++ instead of c++.  How do I

Re: [cmake-developers] Proposal to disable link depends inference.

2017-04-20 Thread Matthew Hanna (BLOOMBERG/ 731 LEX)
After checking several approaches, it looks as though the number of edges in the inference algorithm is the bottleneck, regardless of the number of cycles inferred. In our particular case, the number of external dependencies far outnumbers the known, internal libraries. Also, since we are using

Re: [cmake-developers] Support for unified headers in Android NDK

2017-04-20 Thread Florent Castelli
I just came back from some holidays now, I'll try to update the MR with the latest changes soon next week! /Florent On Apr 20, 2017 10:10 PM, "Robert Dailey" wrote: > I may pick this up, because right now it's impossible to use libc++ > (LLVM) with an API less than 21

Re: [cmake-developers] Support for unified headers in Android NDK

2017-04-20 Thread Robert Dailey
I may pick this up, because right now it's impossible to use libc++ (LLVM) with an API less than 21 since that's when clang was introduced. libc is missing too many symbols that are required by libc++ below API 21. On Thu, Apr 20, 2017 at 2:52 PM, Ben Boeckel wrote: > On

Re: [cmake-developers] Support for unified headers in Android NDK

2017-04-20 Thread Ben Boeckel
On Thu, Apr 20, 2017 at 14:31:58 -0500, Robert Dailey wrote: > Google is supporting unified headers for sysroot as of NDK r14: > > https://android.googlesource.com/platform/ndk/+/master/docs/UnifiedHeaders.md > > Is there a plan to add support for this natively into CMake? There is a merge

Re: [cmake-developers] Support for unified headers in Android NDK

2017-04-20 Thread Brad King
On 04/20/2017 03:31 PM, Robert Dailey wrote: > Google is supporting unified headers for sysroot as of NDK r14: > > https://android.googlesource.com/platform/ndk/+/master/docs/UnifiedHeaders.md > > Is there a plan to add support for this natively into CMake? See issue here:

[cmake-developers] Support for unified headers in Android NDK

2017-04-20 Thread Robert Dailey
Google is supporting unified headers for sysroot as of NDK r14: https://android.googlesource.com/platform/ndk/+/master/docs/UnifiedHeaders.md Is there a plan to add support for this natively into CMake? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] Prevent libraries from linking twice during LLVM build

2017-04-20 Thread Michael Kruse
The cmake mailing list may not have sufficient context, so let me add some details. Polly is an extension library for LLVM. Both can be configured in multiple configurations: LLVM can be - A bunch of libLLVM*.a files - A bunch of libLLVM*.so files - A single libLLVM.so file Polly can be -

[CMake] Prevent libraries from linking twice during LLVM build

2017-04-20 Thread Sanjay Srivallabh Singapuram
Hello, I'm proposing a patch to the Polly/LLVM project that involves linking libPolly.a or libPolly.so to NVPTX back-end libraries. I'm currently using, target_link_libraries(Polly LLVMNVPTXCodeGen LLVMNVPTXInfo LLVMNVPTXDesc LLVMNVPTXAsmPrinter ) The opt binary

[Cmake-commits] CMake branch, release, updated. v3.8.0-4-gb99fbf3

2017-04-20 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, release has been updated via b99fbf3b16449a6027e90ed7f01f240761157332 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-828-gb4d3cdc

2017-04-20 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 b4d3cdc8c504ddc5d2618203a831c950f8d0102a (commit) via