developing pidgin with Kdevelop

Gary Kramlich grim at
Tue Sep 2 02:59:47 EDT 2008

Sergey Rudchenko wrote:
> On Tue, 2008-09-02 at 13:50 +0800, jimmy_yuhai wrote:
>> can we import the pidgin source code into KDevelop IDE? and let it
>> generate the Makefile
>> how to do that ?
>> any ideas?  
> I suggest to use the CMake ( it can generate
> KDevelop projects, Makefiles, MSVS solutions, XCode project and else.
> It is very convenient to have single build script for all the platforms.
> --
> Best regards,
> Sergey Rudchenko

The problem with cmake is that last time i tried using it (over a year
ago at least), i found myself writing tons of dependency checking, due
to a lack of pre-existing checks for the stuff I needed.

I don't think anyone would argue that a single build system would make
things easier over all, the problem is when it comes to any
infactructure change that theres a lot that it affects.  In this case,
it'd be all of our build documentation (i think we have some of that
;)), our documentation for writing 3rd party plugins, as well as
distributions that will need to update they're build stuff and all of
the packages, and most importantly, the developers need to learn how to
use it.

My experiences with cmake is that it seems like a tool meant to hock
their book.  Don't get me wrong, there is documentation on the website,
but it's very brief.

At any rate, we would of course evaluate all of the available build
systems, that being autotools (ie should we switch), scons, jam, cmake,
and I'm sure I'm missing some other stuff.

To my knowledge, we have no interest in changing right now, both Ethan
and myself know autotools quite well, and the rest of the developers
know it well enough, if not better, to be able to do what they need to do.

Gary Kramlich <grim at>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the Devel mailing list