On Tue, Oct 13, 2015 at 02:50:09AM +0200, Krzysztof Kosiński wrote:
2015-10-13 0:36 GMT+02:00 Marc Jeanmougin <marc@...3062...>:
Hi all,
With su_v, we recently compiled some items left to do for CMake builds, so here it is.
[snip]
Windows : -> Add a variable to devlibs, and more generally get cmake to work as expected with "cmake .; make" on windows
Is CMake capable of modifying the shell's environment variables? Because otherwise this is impossible.
Best regards, Krzysztof
I am known for my loathing of cmake (reinventing a wheel), but recent versions seem to have become "good enough" for linux, as well as required for a few packages I need, so I looked at the cmake build of inkscape about six months ago, and I guess the original list of issues covers all the things I noticed (primarily, I wanted to build without some of the optional dependencies, and I also recall the missing man pages), except for this point : *every* other cmake package I have tried to build in the last 3+ years uses a separate build directory.
My guess is that using 'cmake .' is poorly tested. But I could not offer potential fixes for the inkscape cmake files, either for this or for the man pages issue - as we say in English "it's all greek to me" (except, I can read a very few words of greek, and use google translation). The only references I could find for moving from configure to cmake were for *very* basic projects.
Your project, your rules, so please disregard this comment if it will upset you.
ĸen