Re: [CMake] set_target_properties ( INTERFACE_INCLUDE_DIRECTORIES ...)

On Thu, Sep 12, 2019 at 6:31 PM Craig Scott wrote: OPTION A: Put quotes around a semi-colon separated string if using > set_target_properties(): > Many thanks. I had tried quotes, and I had tried a semi-colon, and I thought that I had tried them together, but evidently I missed that

[Cmake-commits] CMake branch, master, updated. v3.15.3-1015-g729c928

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index fc86b56..e9cca30 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,7 +1,7 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 15) -set(CMake_VERSION_PATCH 20190912) +set(CMake_VER

Re: [CMake] set_target_properties ( INTERFACE_INCLUDE_DIRECTORIES ...)

On Fri, Sep 13, 2019 at 8:24 AM Theodore Hall wrote: > Greetings, > > set_target_properties(target PROPERTIES > IMPORTED_LOCATION location > IMPORTED_IMPLIB implib > INTERFACE_INCLUDE_DIRECTORIES directory+ > ) > > Is there a way to assign more than one directory to >

[CMake] set_target_properties ( INTERFACE_INCLUDE_DIRECTORIES ...)

Greetings, set_target_properties(target PROPERTIES IMPORTED_LOCATION location IMPORTED_IMPLIB implib INTERFACE_INCLUDE_DIRECTORIES directory+ ) Is there a way to assign more than one directory to INTERFACE_INCLUDE_DIRECTORIES ? The property name is plural, but every attempt I've

[CMake] compile_commands.json question

Hi all, this is more a question to the cmake developers. Older versions (3.15.0) of cmake produced short file names w/o spaces on windows, when the path of the compiler executable contained spaces. Now I have an issue [1] where compiler executable path contains spaces with cmake 3.15.2. Can

Re: [CMake] Setting RPATH lookup on macOS

I never suggested copying files into the build tree. The original question was about how to locate libraries at runtime. You don't necessarily have to use @rpath, @executable_path is also a valid option. Another valid option one is to strip out @rpath and use DYLD_LIBRARY_PATH or

Re: [CMake] Setting RPATH lookup on macOS

On macOS you really should _not_ have to copy the libraries into the build tree. I have never had to do that in 10 years of our product (Windows is a different story). The trick is setting the correct options to add in the paths to the libraries into the RPATH of the executable/library. (at

Re: [CMake] Setting RPATH lookup on macOS

The macOS install_name_tool can be used to change the RPATH of your binaries. It can also be used to set the path for each of the libraries to be loaded. For a python module I compile, I copy each of its dylib into the appropriate directory relative to my shared library. I then use the

[Cmake-commits] CMake branch, master, updated. v3.15.3-1014-g9602bcf

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 9602bcfc62d50d7bb302b02ae3b1f9afe941bae7 (commit) via

Re: [CMake] Packaging a directory with CPack RPM

Le jeu. 12 sept. 2019 à 02:27, Ashish Sadanandan < ashish.sadanan...@gmail.com> a écrit : > Hello, > I'm using CPack to create RPMs for an application. I have this working but > the CPack step is quite slow. While investigating this, I noticed that all > files in a directory I'm packaging, which

[CMake] can not import target external lib before being build

Hi, I am using this cmake snippet in order to build an external library # -- QGLViewer -- set(QGLVIEWER_FILES ${CMAKE_BINARY_DIR}/libQGLViewer-2.7.1/QGLViewer/qglviewer.h) get_target_property (QT_QMAKE_EXECUTABLE Qt5::qmake IMPORTED_LOCATION) add_custom_command(OUTPUT