Re: [CMake] Get find_package to choose INSTALLed libraries instead of libraries in the build folder

Hi, During install step, installed libraries and executables are relinked to generate binaries without absolute paths so installed artifacts are independent from your build tree. During build step, build binaries are used as well as absolute paths so produced binaries can be used during build

[Cmake-commits] CMake branch, master, updated. v3.10.1-800-gc4d7545

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

[Cmake-commits] CMake branch, master, updated. v3.10.1-799-g4cf08c9

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

[CMake] Get find_package to choose INSTALLed libraries instead of libraries in the build folder

Hi, I would like find_package(MyLib) to link find the libraries found in the INSTALL folder instead of the build folder. Currently, when I do a find_package(MyLib) and then target_link_libraries(target MyLib) the paths all point to MyLib's build folder and not the folder where MyLib's

Re: [CMake] test depending on code compilation

- Mail original - > De: "Mario Werner" > À: cmake@cmake.org > Envoyé: Jeudi 11 Janvier 2018 16:27:18 > Objet: Re: [CMake] test depending on code compilation > > On 2018-01-10 10:47, Franck Houssen wrote: > > [snip] > > > > The 2 unexpected problems I have

Re: [CMake] test depending on code compilation

On 2018-01-10 10:47, Franck Houssen wrote: > [snip] > > The 2 unexpected problems I have left are: > 1) mytestexe is compiled everytime I type "make" which is a solution but > is not really what I am looking for (also compiled when I type "make > check" which is expected). >     => is there a way

[Cmake-commits] CMake branch, master, updated. v3.10.1-784-gae7c7b6

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

[Cmake-commits] CMake branch, release, updated. v3.10.1-10-gecfc729

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

[Cmake-commits] CMake branch, master, updated. v3.10.1-778-g6633535

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

[Cmake-commits] CMake branch, master, updated. v3.10.1-760-g8f1666b

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