[CMake] Add CXX dependency generation to custom command for Ninja?

Hi, We have a custom command for a third-party utility (genreflex, from the ROOT system) which has a directive: IMPLICIT_DEPENDS CXX ${CMAKE_CURRENT_SOURCE_DIR}/classes.h How would I, either as an extra COMMAND or as a separate custom command, manually invoke the configured CXX compiler

Re: [CMake] Platform-independent config package

You can temporarily unset CMAKE_SIZEOF_VOID_P before calling write_basic_package_version_file. See for instance https://bitbucket.org/eigen/eigen/src/ff6170e75ab07d74d8f7dd21af777a94799d168d/CMakeLists.txt?at=3.3&fileviewer=file-view-default#CMakeLists.txt-541:545 . On Tue, Jan 10, 2017 at 7:52 PM

[CMake] Custom command on cpack target

I would like to run a custom command on the zip file generated by cpack. The idea is that I want to calculate its sha256 checksum. Unfortunately it seems the zip file cannot be a target in a CMakeLists.txt file or I'm doing something wrong. Can someone give me a hand? -- Gonzalo Garramu

Re: [CMake] Platform-independent config package

Dear Ghis, the easiest long-term fix would be an own glmConfig.cmake file. The command write_basic_package_version_file uses a template with those pointer checks. The glm-developers could simply copy the template to their source directory, remove the unneeded lines and run the configure_file c

[CMake] Chocolatey? (Windows)

I was wondering if anyone was familiar with Chocolatey and whether there are plans to add support for it in cmake/cpack. For those that don't know, Chocolatey is a small Windows' utility similar to Debian's apt-get. It allows simple management of packages (binaries mainly). -- Powered by w

[CMake] Platform-independent config package

Dear all, I am currently hit by an issue with the CMake detection of a header-only library [1]. The library is built on a 64-bit machine and packaged for all other architectures supported by Debian. However, CMake detection fails on 32-bit platforms with the following error: ``` Any attempt to c

[CMake] Problems building a MODULE library (OpenFX plugin) with correct cuda object linking

Hello, after hours and hours of searching and trying to get it to work I hope someone here can help me as I'm now out of ideas. I'm trying to build an OpenFX plugin for DaVinci Resolve (a movie color grading software, https://www.blackmagicdesign.com/products) via CMake. Resolve is delivered

Re: [CMake] Find Vulkan on 32 bit builds

There's a couple of ways to fix this; for instance, on Windows I could use NO_DEFAULT_PATH on the find_library call and that would resolve the issue. The main reason why I haven't done this yet is because I think that's a packaging bug in the Vulkan SDK side which I was going to report there (I wa

Re: [CMake] Find Vulkan on 32 bit builds

That makes sense! Removing the variable from PATH does indeed fix the issue. It is not a blocking issue for me. I agree that this is a Vulkan packaging issue. However, since you are looking for $ENV{VULKAN_SDK} in the find module and assuming it exists, then it 'should' override the other path? I

Re: [CMake] Find Vulkan on 32 bit builds

Hi, the problem here is that the Vulkan SDK helpfully adds D:/VulkanSDK/1.0.37.0/Bin into PATH, while the Vulkan module dutifully searches Bin on x64 and Bin32 on x86. However, because /Bin is in the PATH, and because the libraries for both architectures are named the same, it will pick up the one

[CMake] Bundling for OS X

(Full source is available at https://github.com/rjhansen/sherpa ) I have a Qt 5.7 application which I'm trying to migrate from qmake to cmake 3.7. So far it almost works on OS X, except when it comes to making a proper app bundle. The relevant contents of my CMakeLists.txt are as follows: =