Quite often the question comes up how to build a KDE application.
Now we have great tools such as kdesrc-build and buildtool and long wiki pages on techbase…
But many of these aim at building not just one application but the world. Or at least kdelibs and everything on top of it. To start development, it’s often easier to build just the application you care about. Lately for a quick patch, that’s what I’ve been using. So if you’re not yet hacking on the internals but just want to build let’s say Parley, here you go:
http://techbase.kde.org/Development/Tutorials/Building_An_Existing_Application
I bet there is much to add and improve, so please help make techbase nicer for new contributors, we all started at some point, right 😉 I wonder if this approach should be more mentioned as the default way of building an application – it just takes a couple of minutes and you’re good to start hacking.
This post was triggered by some great Parley patches I received from Christian Muschick, who also happened to ask how to best build the application without messing up his system.