[CMake] target_link_libraries not populating INCLUDE_DIRECTORIES?

2018-12-21 Thread Ciccio Pasticcio
Hi all, considering the following CMakeLists.txt: PROJECT(lib_foo) ADD_LIBRARY(lib_foo SHARED ) TARGET_INCLUDE_DIRECTORIES(PRIVATE private/ PUBLIC inc/) FIND_PACKAGE(Boost 1.55 REQUIRED COMPONENTS chrono system) TARGET_LINK_LIBRARIES(lib_foo PRIVATE Boost::chrono Boost::system)

[CMake] Handling real-time output from execute_process

2018-12-21 Thread Person Withhats
Hey there! I'm running a script that downloads some files and untars them. This takes a while but it outputs progress. Unfortunately I can't get the output to show up in real-time with CMake GUI or CLI. Current workaround to see output live, loses it in log though..

Re: [CMake] Get linker flags / include directories for a library target

2018-12-21 Thread Kai Wolf
You can ask a CMake build target for its properties using get_target_property(). For instance, to retrieve the linker flags for a given target foo, you’d write: get_target_prooperty(foo_linker_flags foo LINK_FLAGS) See [1] for a list of valid parameters. Greetings, Kai [1]

[CMake] cmake -gsplit-dwarf dwp and install step

2018-12-21 Thread David Jobet
Hello, in order to speed up our link step, I wanted to experiment with split dwarf. See http://www.productive-cpp.com/improving-cpp-builds-with-split-dwarf/ Adding the compilation flag is easy, but I'm stumbling on the installation step. In our current mode, we redirect the STRIP step to extract

Re: [CMake] target_link_libraries not populating INCLUDE_DIRECTORIES?

2018-12-21 Thread Mateusz Loskot
On Fri, 21 Dec 2018, 09:30 Ciccio Pasticcio TARGET_INCLUDE_DIRECTORIES(PRIVATE private/ PUBLIC inc/) > ... > The manpage of TARGET_LINK_LIBRARIES says: > PRIVATE and PUBLIC items will populate the INCLUDE_DIRECTORIES

Re: [CMake] target_link_libraries not populating INCLUDE_DIRECTORIES?

2018-12-21 Thread Marc CHEVRIER
Command target_link_libraries do not populate directly the properties of the target due to many constraints regarding the values given to the command (generator expressions, other targets, etc…). The full contents is taken into account at generation time not at the configuration time. This is

[CMake] set_property imported_location_release

2018-12-21 Thread Lars
Hello, Trying to import an external library but having some issue with setting imported_location_release property. Basically I have config file which does this; add_library(foo STATIC IMPORTED) set_property(target foo APPEND PROPERTY interface_include_directories "$" "$")

Re: [CMake] set_property imported_location_release

2018-12-21 Thread Marc CHEVRIER
Properties IMPORTED_LOCATION* do not support generator expressions. Generally speaking, if a property supports generator expression, it is explicitly specified in documentation. Le 21 déc. 2018 à 13:07 +0100, Lars , a écrit : > Hello, > > Trying to import an external library but having some

Re: [CMake] set_property imported_location_release

2018-12-21 Thread Lars
Marc, Appreciate the quick and helpful response. In a config file that supports multiple platforms, do I need to create import_location_path variable and populate it depending on platform and 32/64 etc? Any other options? Thanks. Kind regards, Lars Fra: Marc

Re: [CMake] Get linker flags / include directories for a library target

2018-12-21 Thread Unknown
Hello Kai, thanks for your suggestion. I tried the property, but I just got "foo_linker_flags-NOTFOUND" as a result (I am using cmake 3.13.1 btw). The same goes for LINK_OPTIONS, and INTERFACE_LINK_OPTIONS. I tried using the INTERFACE_LINK_LIBRARIES property instead. The resulting list contains

Re: [CMake] set_property imported_location_release

2018-12-21 Thread Marc CHEVRIER
Yes, the most efficient way is using conditional setting. For example: if (CMAKE_SIZEOF_VOID_P EQUAL 4)   set(import_path /to/lib32) else()   set(import_path /to/lib64) endif() set_property(TARGET foo PROPERTY IMPORT_LOCATION "${import_path}/lib.so") Le 21 déc. 2018 à 15:14 +0100, Lars , a

Re: [CMake] Handling real-time output from execute_process

2018-12-21 Thread frodak17
On Fri, Dec 21, 2018 at 8:30 PM Person Withhats wrote: > Hey there! > > I'm running a script that downloads some files and untars them. This takes > a while but it outputs progress. Unfortunately I can't get the output to > show up in real-time with CMake GUI or CLI. > > Current workaround to

Re: [CMake] Handling real-time output from execute_process

2018-12-21 Thread Person Withhats
1) I want output in real time on a Windows system(no tail), and piping output to a file then reading it is a very poor solution. 'just check the contents in note pad' 2) This is a general-purpose solution and not something I'm making just for myself, hacky fixes are not an option. On Fri, Dec

Re: [CMake] Handling real-time output from execute_process

2018-12-21 Thread frodak17
On Fri, Dec 21, 2018 at 11:16 PM Person Withhats wrote: > 1) I want output in real time on a Windows system(no tail), and piping > output to a file then reading it is a very poor solution. 'just check the > contents in note pad' > 2) This is a general-purpose solution and not something I'm

Re: [CMake] set_property imported_location_release

2018-12-21 Thread Lars
That is what I thought. Thank you. Fra: Marc CHEVRIER Sendt: fredag 21. desember 2018 15.46.18 Til: cmake@cmake.org; Lars Emne: Re: Sv: [CMake] set_property imported_location_release Yes, the most efficient way is using conditional setting. For example: if

[Cmake-commits] CMake branch, master, updated. v3.13.2-765-g91bcb88

2018-12-21 Thread Kitware Robot via Cmake-commits
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 91bcb88c3cbd9500563ccddb8dec721a04e3f7f6 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.13.2-761-g2aae1c1

2018-12-21 Thread Kitware Robot via Cmake-commits
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 2aae1c1dd26852a5186570ea25924c6103c28d79 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.13.2-763-g16262ed

2018-12-21 Thread Kitware Robot via Cmake-commits
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 16262ed7628cc6272178eb7ca1503b66b2380cf4 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.13.2-766-g87ddcad

2018-12-21 Thread Kitware Robot via Cmake-commits
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 6bc6c0b..70c0c7f 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 13) -set(CMake_VERSION_PATCH 20181221) +set(CMake_VER

Re: [cmake-developers] cmake-developers Digest, Vol 122, Issue 9

2018-12-21 Thread Ivam Pretti
happy birthday! Em ter, 11 de set de 2018 às 11:00, escreveu: > Send cmake-developers mailing list submissions to > cmake-developers@cmake.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://cmake.org/mailman/listinfo/cmake-developers > or, via email,