[CMake] Moving build artifacts to custom directory

Hi Everyone, How do I move the build artifacts(ELFs, Static libraries, custom intermediate files) to custom folder at the build of "cmake --build ." ? Also does "cmake --build . -- clean" takes care of cleaning these build artifacts from the directory to which they previously moved? Regards,

Re: [CMake] Moving build artifacts to custom directory

Have a look at variables ‘CMAKE_*_OUTPUT_DIRECTORY’ (Like CMAKE_ARCHIVE_OUTPUT_DIRECTORY. See  https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html) and target properties ‘*_OUTPUT_DIRECTORY’ (Like ARCHIVE_OUTPUT_DIRECTORY. See 

Re: [CMake] Combining two static libraries into one

I think there is no platform-independent way to solve this. Maybe you could create two OBJECT libraries that are "linked" together into one static lib. Best regards, Rainer On Tue, Jul 2, 2019 at 5:30 PM Cristian Adam wrote: > > > On Tue, Jul 2, 2019 at 5:14 PM vinay kumar Kotegowder >

Re: [CMake] Combining two static libraries into one

On Wed, 2019-07-03 at 18:55 +0530, vinay kumar Kotegowder wrote: >  I want to build lib2 static library with pre-built lib1 static > library. >  Does this work? > >  add_library(lib1 STATIC lib1.c) >  add_library(lib2 STATIC lib2.c) >  target_link_libraries(lib2 INTERFACE lib1) Yes, this will

Re: [CMake] compiling .cpp/.cxx with CUDA compiler

Thank. Yeah, I've seen BLT through it's use in RAJA. You're right, it'd work, but I'm reluctant to stray away from "vanilla" cmake too much, since other people will have to deal with this code, and cmake itself is already quite a step up from the regular Makefiles that they're used to. --Kai On

Re: [CMake] Combining two static libraries into one

I want to build lib2 static library with pre-built lib1 static library. Does this work? add_library(lib1 STATIC lib1.c) add_library(lib2 STATIC lib2.c) target_link_libraries(lib2 INTERFACE lib1) Also, Kyle said linking against lib2 will link against both lib1 and lib2. Is there a static

Re: [CMake] Combining two static libraries into one

I want to build lib2 static array with pre-built lib1 static array. Does this work? add_library(lib1 STATIC lib1.c) add_library(lib2 STATIC lib2.c) target_link_libraries(lib2 INTERFACE lib1) Also, Kyle said linking against lib2 will link against both lib1 and lib2. Is there a static way

Re: [CMake] getting compiler's include paths

I completely forgot that the Makefiles based generators in CMake have a separate heuristic for determining system headers. If you use the Ninja generator I see the expected behavior: ~/W/t/nbuild $ sudo touch /usr/include/c++/7/array ~/W/t/nbuild $ ninja -d explain -v ninja explain: output

[CMake] CMake APT Repository Signing Key

All, The new 2020 signing key for the APT repository (https://apt.kitware.com/) has been generated for 2020, with fingerprint A8E5EF3A02600268. The 2019 key, with fingerprint C1F34CDD40CD72DA, will remain in effect until the beginning of 2020, at which point the 2020 key will go into effect. The  

[CMake] Shared, static and header-only versions of library side by side.

Hello, The libraries I developing can be used as a shared libraries, static libraries or header-only libraries. I want to let the users to: - install all three variants side by side; - choice what variant of library to use for linkage. I see 2 options here: 1. use different config files.

[Cmake-commits] CMake branch, master, updated. v3.15.0-rc3-212-g8f93d76

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

[Cmake-commits] CMake branch, release, updated. v3.15.0-rc3-16-g581e011

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

[Cmake-commits] CMake branch, master, updated. v3.15.0-rc3-210-g1cc8f85

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

[cmake-developers] CMake APT Repository Signing Key

All, The new 2020 signing key for the APT repository (https://apt.kitware.com/) has been generated for 2020, with fingerprint A8E5EF3A02600268. The 2019 key, with fingerprint C1F34CDD40CD72DA, will remain in effect until the beginning of 2020, at which point the 2020 key will go into effect. The  

[Cmake-commits] CMake branch, master, updated. v3.15.0-rc3-216-g0bddcce

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

[Cmake-commits] CMake branch, release, updated. v3.15.0-rc3-18-g1f389b4

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

[Cmake-commits] CMake branch, master, updated. v3.15.0-rc3-217-gf889e03

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 7177393..6974b16 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 15) -set(CMake_VERSION_PATCH 20190703) +set(CMake_VER