Packaging RKWard for Windows
Out of date warning
The information on this page has not been fully tested for KF5, yet, but should mostly work. It’s targeted at developers or power users willing to solve problems themselves, not to end users!
RKWard for Windows is currently distributed in two different variants: as a single installer, and as an installation bundle including R and KDE. This page details the steps needed to create these two packages.
Creating the RKWard for Windows installer
- A source-based installation of KDE, using craft. In general you should not use the latest and greatest KDE, here, but the latest version which already has an official KDE on Windows release to it.
- Set up your KDE environment in your craft install.
Check out a clean copy of the RKWard source from git. When creating the installer package, you will probably want to check out a release branch, rather than trunk. Thus, typically you will use something like: -
:git clone git://anongit.kde.org/rkward.git :git checkout releases/0.7.0 It does not really matter, where you put the sources. It may be a good idea to do so outside the craft tree, though.
- CD to the “windows_nsis”-subdirectory of the sources.
- There is a batch file “make_release.bat”, here. Edit this (e.g.
using kwrite). Adjust the top few lines to reflect the details of
you installations. Follow these guidelines:
K:\K\bin\kwrite.exeexists, set -
KDEPREFIX=Ki.e. point this at the root of your emerge tree.
C:\R\R-x.y.z\bin\R.exeexists (and you want to compile against that version), set -
C:\NSIS\makensis.exeexists, set -
You’ll probably take MinGW from your emerge tree, i.e. -
- If all goes well, an .exe-file (eg: install_rkward_0.7.0.exe) of roughly 1.4MB will be created. Test this installer, by simply running it.
This should be it.
Creating the installation bundle
- You will probably want to edit the rkward blueprint to refer to the release branch:
- First compile
craft -i rkward
- Packaging is easy:
craft –package rkward