Re: [CMake] Update/Set _expectedTargets inside exports-release.cmake.

2016-01-12 Thread Stephen Kelly
Rashad Kanavath wrote: > I am having this when I build packages for debian where I split components > into separate packages project1-core, project1-gui etc.. I think you need to patch the buildsystems of the software you are packaging so that they support that kind of split by exporting to a di

[CMake] How to get generated dependencies

2016-01-12 Thread Tom Kacvinsky
Is there a way of invoking cmake to get the list of non-system header dependencies, like invoking gcc with -MMD? I need to find out the list of non-system header dependencies and I know cmake has a way of doing this, I just need to know if there is command I can put in the CMakeLists.txt file to g

[CMake] C standard and order of arguments

2016-01-12 Thread Magnus Therning
I'm trying to turn on a bit more warnings in a C project but I'm running into an ordering issue. I have #+BEGIN_SRC cmake set(CMAKE_C_STANDARD 11) set(CMAKE_C_FLAGS "-Wall -Wextra -Werror") #+END_SRC and I want to add ~-Wpedantic~. However if I do then I get a lot of warnings (that are turned i

[CMake] Update/Set _expectedTargets inside exports-release.cmake.

2016-01-12 Thread Rashad Kanavath
Hello all, Is it possible to update or set the "_expectedTargets" cmake variable inside the exports.cmake or exports-release.cmake file I know this file is autogenerated and it generates all so files and use cmake add_library IMPROTED option etc.. I have an issue with this method. Lets say, I h

Re: [CMake] FORTRAN name mangling

2016-01-12 Thread Arjen Markus
> Exactly, that is the whole point of the standardized `ISO_C_BINDING` module > and C interop being added to the Fortran 2003 standard. No more ugly guess > work, hackery, etc. > AFAIK, there is pretty good support for this among compiler vendors, so long > as you have a recent release. > Even