Re: [CMake] CPack and PackageMaker

Hi, I have updated the patch I sent before and you can find some new code here: https://github.com/clintonstimpson/CMake/commits/productbuild To help, perhaps you can review and test it. Or help in other ways you think it needs. I have done minimal testing. This includes making sure CMake's

Re: [CMake] How to deal with generated source files (w/ dependency tracking) for globs

I haven't tested this myself, but instead of using a glob, you could have a build step that generates a CMake script file with the list of generated files in it (e.g. via execute_process to run another CMake script whose only job is to generate the CMake script inception-style) and just include the

[CMake] How to deal with generated source files (w/ dependency tracking) for globs

Hi, this is kind of a side problem that was asked of me. I'm not sure how many hoops I actually want to jump through to solve this. But, here's the situation. I have a really nice, traditional C based project in CMake. All my dependency tracking works really well for cross-platform and IDE integra

[CMake] Problem calling find_package(PythonLibs) consecutively on Windows with python debug

Hi all, The problem I’m compiling a project in which I have: - python bindings for C++ - VTK When issuing a find_package(VTK) inside a FindMyLib.cmake I got this error: CMake Error at D:/Work/Miniconda/envs/sci20/Library/share/cmake-3.4/Modules/FindPythonLibs.cmake:180 (get_filename_comp

Re: [CMake] VERSION and SOVERSION in a module

Thank you for your answer. It helped me a lot. 2016-04-04 12:07 GMT+02:00 Nils Gladitz : > On 04/04/2016 10:33 AM, Kristian wrote: >> >> Hey, >> >> I have a question. I have a project, which is compiled on two >> different build machines with ninja (trunk and branch). The >> CMakeLists.txt is the

Re: [CMake] VERSION and SOVERSION in a module

On 04/04/2016 10:33 AM, Kristian wrote: Hey, I have a question. I have a project, which is compiled on two different build machines with ninja (trunk and branch). The CMakeLists.txt is the same when it comes to a part, where the VERSION and SOVERSION part is set through the function 'set_target_

[CMake] VERSION and SOVERSION in a module

Hey, I have a question. I have a project, which is compiled on two different build machines with ninja (trunk and branch). The CMakeLists.txt is the same when it comes to a part, where the VERSION and SOVERSION part is set through the function 'set_target_properties'. But on the first build machi