While searching some info on the net about porting projects from autotools to cmake i have found this: http://techbase.kde.org/Development/Tutorials/KDE4_Porting_Guide#CMake Apparentely they have script that converts automatically .am files to cmake files. I've run it on several not-yet-ported-to-cmake trinity components, and it generated nearly whole CMake files structure. Yet it doesn't generate config.h.cmake file which is needed (without it compilation simply don't happen). I've asked for help on kde-devel irc channel, but without any success (maybe I'll ask later). Whole point is, maybe we could adapt this to generate our cmake files, thus speeding whole porting to cmake?
On Friday 09 December 2011 20:31:02 L0ner sh4dou wrote:
While searching some info on the net about porting projects from autotools to cmake i have found this: http://techbase.kde.org/Development/Tutorials/KDE4_Porting_Guide#CMake Apparentely they have script that converts automatically .am files to cmake files. I've run it on several not-yet-ported-to-cmake trinity components, and it generated nearly whole CMake files structure. Yet it doesn't generate config.h.cmake file which is needed (without it compilation simply don't happen). I've asked for help on kde-devel irc channel, but without any success (maybe I'll ask later). Whole point is, maybe we could adapt this to generate our cmake files, thus speeding whole porting to cmake?
Actually writing cmake rules are realy simple, because I developed macros to simplify the process, is a simple copy/paste procedure. Most of time is consumed developing check procedures.
http://www.trinitydesktop.org/wiki/bin/view/Developers/CMakeConversionProces...
Manually porting is preffered, because resulted files are very clean, predictible and easily debugable, with no useless dependencies.
2011/12/9 Serghei Amelian serghei@thel.ro:
On Friday 09 December 2011 20:31:02 L0ner sh4dou wrote:
While searching some info on the net about porting projects from autotools to cmake i have found this: http://techbase.kde.org/Development/Tutorials/KDE4_Porting_Guide#CMake Apparentely they have script that converts automatically .am files to cmake files. I've run it on several not-yet-ported-to-cmake trinity components, and it generated nearly whole CMake files structure. Yet it doesn't generate config.h.cmake file which is needed (without it compilation simply don't happen). I've asked for help on kde-devel irc channel, but without any success (maybe I'll ask later). Whole point is, maybe we could adapt this to generate our cmake files, thus speeding whole porting to cmake?
Actually writing cmake rules are realy simple, because I developed macros to simplify the process, is a simple copy/paste procedure. Most of time is consumed developing check procedures.
http://www.trinitydesktop.org/wiki/bin/view/Developers/CMakeConversionProces...
Manually porting is preffered, because resulted files are very clean, predictible and easily debugable, with no useless dependencies.
-- Serghei
Ok, any pointers on which files I should look searching for dependencies to include in CMake files?
On 9 December 2011 14:35, Serghei Amelian serghei@thel.ro wrote:
On Friday 09 December 2011 21:30:29 L0ner sh4dou wrote: [...]
Ok, any pointers on which files I should look searching for dependencies to include in CMake files?
Usually Makefile.am and configure.in
And I suggest taking a look at kdegraphics, kdebase, etc. They all contain a ConfigureChecks.txt and a CMakeFiles.txt which should serve as a good example
-
Calvin Morrison -
L0ner sh4dou -
Serghei Amelian