[CMake] [Config-file Package] The best practice of finding package dependencies?

Hello community! I want to give a little discussion :) If I export a package containing several targets. And these target are publicly linked to the targets imported from another package. Where is the best place to look for package dependencies? I assume the following options: - In the

Re: [CMake] Missing _EXPORTS definition in CUDA host compilation

Hi Robert, Thanks for taking the time to look into this. Strange that it isn't reproducing for you! I've made a minimal test case that reproduces the bug, and put it on github: https://github.com/jameshancox/cmake_example_16993 I am using: Visual Studio Professional 2013 Update 5 CUDA

[CMake] CPack and user .spec file

Hello all, I'm fairly new to CPack and, while I was able to successfully package (RPM) standalone applications that use CMake, I'm having difficulties with packaging an application using a custom .spec file. I have an application repository that is built with CMake, but requires

[CMake] Install shared libraries only if required

Hi all, I've got a cmake project that builds multiple executables and shared libraries. There are option() settings that determine which of these executables are built. What I'd like to be able to do is prevent the building and installation of shared libraries that are not required. So what

Re: [CMake] CPack and user .spec file

> > I have an application repository that is built with CMake, but > requires additional/custom handling when packaging -- hence the need > for a custom .spec file. Can this not be done from CMakeLists.txt by setting some additional CPACK_* variables depending on the build environment? > After

Re: [CMake] Missing _EXPORTS definition in CUDA host compilation

On 06/20/2017 10:10 AM, Hancox, James wrote: > I swapped out CUDA 8.0.44 for CUDA 8.0.61, and my problem magically > went away. Great! Thanks for testing and reporting back. > It might be worth adding a warning/diagnostic to let people know > that 8.0.44 has bugs in the VS integration? Yes,

Re: [CMake] CPack and user .spec file

2017-06-20 8:43 GMT-04:00 Domen Vrankar : > Can this not be done from CMakeLists.txt by setting some additional CPACK_* > variables depending on the build environment? The custom bits could be done with CPACK_*, I think, but I haven't spent too much time investigating

Re: [CMake] Missing _EXPORTS definition in CUDA host compilation

On 06/20/2017 06:03 AM, Hancox, James wrote: > https://github.com/jameshancox/cmake_example_16993 Thanks for the example. Also, thanks for trying the release candidate! > Visual Studio Professional 2013 Update 5 > CUDA 8.0.44 > cmake 3.9.0.rc3 I'm not able to reproduce it using VS 2013 Update

Re: [CMake] Missing _EXPORTS definition in CUDA host compilation

Hi Brad, I swapped out CUDA 8.0.44 for CUDA 8.0.61, and my problem magically went away. Thanks a lot for the help, I never would have made that connection! I checked the .vcxproj file before regenerating, and the _EXPORTS define was right where it should be, so it definitely seems like a bug

[Cmake-commits] CMake branch, master, updated. v3.9.0-rc3-134-g782c1e2

_VERSION_MINOR 9) -set(CMake_VERSION_PATCH 20170620) +set(CMake_VERSION_PATCH 20170621) #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.9.0-rc3-133-g8308803

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