Well, the Chicken Scheme-to-C compiler is not oriented towards KDE4 in any way, but it does currently feature a unified CMake and Autoconf build. Much as I'm trying to get people to dump the Autoconf build, they're scared to let go of it. So, you can see a lot of non-trivial Autoconf and CMake stuff side by side, and strategies for supporting both at once while maintaining stability. My CMake build is heavily commented, it's supposed to serve as a tutorial for new CMakers to some degree.
<a href="http://www.call-with-current-continuation.org">http://www.call-with-current-continuation.org</a><br><br>Cheers,<br>Brandon Van Every<br><br><br><div><span class="gmail_quote">On 5/10/07, <b class="gmail_sendername">
Andreas Pakulat</b> <<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<br>I need some help converting an autotools project to cmake. I ran an<br>am2cmake script (from KDE4) which created somewhat usable<br>CMakeLists.txt. What it didn't do is convert the <a href="http://config.h.in">config.h.in
</a> to a<br>config.h.cmake and I don't really have an idea what to do with that<br>file.<br><br>Looking at some kde4 stuff I tried replacing all #undef foo with<br>#cmakedefine foo 1. But all that I get is commented out #undef foo 1.
<br><br>What do I have to do to get this to work? A pointer to a simple<br>cmake using project that I can learn from is perfectly fine.<br><br>Andreas<br><br>--<br>Don't hate yourself in the morning -- sleep till noon.
<br>_______________________________________________<br>CMake mailing list<br><a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br><a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake
</a><br></blockquote></div><br>