RKWard Extras Files

--- What's this? ---
The folder "k" contains the root directory of my build of KDE 4.10 on Windows using emerge (http://techbase.kde.org/Getting_Started/Build/Windows/emerge).

Packed using 7zip (http://http://www.7-zip.org/). Size of the extracted archive is around 7 GB.

--- Intended audience ---
The intended audience includes:
- Developers wishing to work with the KDE platform on Windows
- Users who have been told to try this archive, explicitly, and by a trusted person (e.g. to check if a bug is still present)
- Users who are really curious *and* aware that curiousity killed the cat.

If you do not belong to any of these categories, then this archive is not for you.

--- Why shouldn't I just build my own tree using emerge? ---
If you want to do that, by all means, do! That's still the canonical way to get a build environment of KDE on Windows. And the
more people are going this way, the sooner any problems on the path will be recognized and fixed.

This archive is targetted at those who would like a shortcut. I know I would have liked to have one, for various reasons.

--- Compiler and platform ---
I compiled for i386 (32bit) and using MinGW4. If you plan on using a different compiler, or compiling for a different architecture, then this archive
will not be of any use to you. I compiled on a WinXP (virtual) box, which is the lowest version of Windows to be supported by the KDE on Windows project.
You should be fine with any desktop version of Windows starting at Windows XP or later.

--- What's included? ---
RKWard and all it's dependencies, and then a bit. That includes (among others):
- kate / kwrite
- kde-runtime
- kdepimlibs
- kdelibs
- gcc (MinGW)
RKWard is a development snapshot between 0.6.1 and 0.6.2. R is at 3.0.0. The KDE components are a snapshot at (roughly) 4.10.2. Qt is at 4.8.4.

You should find all sources included. In theory, you should be able to rebuild everything, without the need to download any additions (using the "--offline"
option of emerge). I have not tried this, though. If you find anything missing, please drop me a note.

Do heed all copyright notices!

--- What's not included? ---
Importantly: Python. You will have to install that yourself, and point the config to that installation. If you want to use emerge at all, that is.

I have cleaned all build working directories to free up a large amount of space, and also the python cache files and the build logs.

--- Config and paths ---
My KDE was rooted at K:\k . The runtime should work fine, even if you extract the archive to a different path. However, absolute path references
are all over the build system. So if you want to compile anything, you probably have to make sure to use the same root path I did. Hint: Try using

   subst K: C:\Where\you\actually\extracted\this\archive

You may also have to make some adjustments in K:\k\etc\kdesettings.bat . Importantly, the path to your python installation. 

Note that all git and svn checkouts are anonymous and thus read-only.

--- More technical details ---
I had to apply a small patch to nepomuk-core, locally. If this patch gets into conflict with patched included upstream, "git reset --hard" is your friend.
I compiled almost everything using EMERGE_USE_SHORT_PATH=0, except for Qt, where I had to enable this setting. Also, I installed cmake 2.8.11-rc1, 
(also via emerge, though), as the default target did not run at all on this machine.

Finally, I copied the MinGW runtime libs from k\mingw\bin\ to k\bin, in order to make KDE applications start without having to set the path,
first. Hope that doesn't cause any probs, elsewhere.

Thomas Friedrichsmeier, 2013-04-25