[Cmake-commits] CMake branch, master, updated. v3.11.1-819-ge81e024

VERSION_MINOR 11) -set(CMake_VERSION_PATCH 20180516) +set(CMake_VERSION_PATCH 20180517) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Install libraries defined in INTERFACE targets

BUILD_INTERFACE explicitly means that only consumers inside the same buildsystem should use these libraries. To specify the libraries that should be used when linking to an installed version of a library you need to use INSTALL_INTERFACE. The reason for BUILD and INSTALL interface is to make sure

[Cmake-commits] CMake branch, master, updated. v3.11.1-818-gacb9710

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

[Cmake-commits] CMake branch, master, updated. v3.11.1-814-g9d143ce

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 9d143ce38cca0f8631655f5c19c8d454359ebb6f (commit) via

Re: [CMake] include directories not found for object library

That is exactly how it will look. On Wed, May 16, 2018 at 4:19 AM Miklos Espak wrote: > That's awesome, thanks a lot! > > So, it would look like this in my case then: > > target_link_libraries(baseapp PUBLIC dcmjpeg mylib1 mylib2) > > And the object library has to be added to

Re: [CMake] Install libraries defined in INTERFACE targets

Hallo, I have created a simple project simulating the issue.    There is 'run.sh' script which first builds an executable using 'add_subdirectory()' CMake command. It works without issues, as expected (the libraries required by Module1 and Module2 are passed to the Module4 builder). Then, it

Re: [CMake] [CPack] Avoiding packaging (some) dependencies

2018-05-16 9:33 GMT+02:00 Drago Trusk : > Hi everyone, > > I have particular problem which I'm unable to solve. > > Lets say there are following components: > - Main: library/executable > - Ignorable: Main requires it to build, but not for packaging > > Main simply

Re: [CMake] include directories not found for object library

That's awesome, thanks a lot! So, it would look like this in my case then: target_link_libraries(baseapp PUBLIC dcmjpeg mylib1 mylib2) And the object library has to be added to the sources of the app1 and app2, like now. With other words, object libraries would be allowed on the left hand side

[CMake] [CPack] Avoiding packaging (some) dependencies

Hi everyone, I have particular problem which I'm unable to solve. Lets say there are following components: - Main: library/executable - Ignorable: Main requires it to build, but not for packaging Main simply defines: add_dependencies(Main Ignorable) FindIgnorable.cmake contains something