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

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 ar

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

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 FindOpenS

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

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 Cc: CMake Subject: Re: [CMake] How to se

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

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 my

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

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 passed

[CMake] How to set C++ standard?

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 se

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

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

[CMake] Prevent libraries from linking twice during LLVM build

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 link