Hey there all you Krita lovin' kids!

I just finished putting up a wiki page at https://wiki.ubuntu.com/CompilingKoffice2 to guide you step by step through building / compiling Koffice2 (including Krita) on your (K)Ubuntu machine.

It's adapted straight from the very excellent:
http://wiki.koffice.org/index.php?title ... ng_KOffice

I've just simplified what's there by:
a) Only making it need to fit one distro (Kubuntu)
b) Using some default paths throughout
c) Stripping away some developer only stuff (KDE developer account etc)

and a few other bits and pieces.

Now you can enjoy the latest Koffice before it comes out (remembering that it *will* likely be unstable). Just remember to file bugs when you find them!

How about using ccache?

Amarok devs recomend it when frequently building from sources.

SeaJey wrote:How about using ccache?

Amarok devs recomend it when frequently building from sources.

ccache is useful only when you often rebuild so that you remove the build directory.
It caches the compilation. It is useful for amarok devs as they claim that they remove build dir quite often, but that is not so often for KOffice development.

So ccache + KOffice usually useful.

http://wiki.koffice.org/index.php?title ... ng_KOffice

most of it still applies to kubuntu

m4v wrote:http://wiki.koffice.org/index.php?title=Building/Building_KOffice

most of it still applies to kubuntu

Absolutely. That's where all the base information comes from... *however* as someone new to compiling, it took me a loooong time going through that and figuring out how to apply it to my specific circumstances. I had to read a lot of stuff just to figure out it didn't apply to me (the hard list of dependencies... instead of just "apt-get build-dep koffice-kde4", the KDE developer bits, the OpenSuse bits) The guide at Koffice works for pretty much any distro. Mine is written to make things as easy as possible, with as little distractions as possible, for Kubuntu (and maybe Ubuntu) users.

Anyway, I guess what I'm saying is that the original guide is important to have, but this is the guide that would have helped me personally the most when I started, so I'm sharing in the hopes it helps someone else.