(Less confusing headers) |
(Add link to qt deployment info page) |
||
Line 124: | Line 124: | ||
* For documentation on NSIS, see http://nsis.sourceforge.net . | * For documentation on NSIS, see http://nsis.sourceforge.net . | ||
* One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 . | * One NSIS template is discussed at http://lists.kde.org/?l=kde-windows&m=127569323809833&w=2 . | ||
+ | |||
+ | |||
+ | = Further info = | ||
+ | * [http://qt-project.org/doc/qt-4.8/deployment-windows.html Deploying a Qt Application on Windows] (qt-project.org) |
Currently, several approaches exist towards packaging KDE applications for Windows, and we will try to outline each approach and the steps involved. Which approach (or approaches) you chose will depend on the type of your application, and your personal taste. The main benefits and drawbacks of each approach are listed in the respective sections.
Note that the approaches are not mutually exclusive, and in particular it is probably always a good idea to provide an emerge script.
Emerge allows to build KDE, and assorted other software on Windows from source, very easily. If you are developing KDE apps on Windows, you are probably familiar with it, already (and if you are not, you better take a look). Emerge also forms the basis for package building for the #KDE windows installer.
This section needs improvements: Please help us to
cleanup confusing sections and fix sections which contain a todo Does documentation exist? Write it/link it! |
Take a look at the existing emerge scripts in portage. Probably there is already a project with a similar setup, so you can copy most things.
The KDE windows installer is the officially recommended way for end-users to install the KDE SC, in whole or in part.
This section needs improvements: Please help us to
cleanup confusing sections and fix sections which contain a todo Does documentation exist? Write it/link it! |
You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.
[mingw32-]make install DESTIR=Some\temporary\folder
KDE on windows is self-contained, i.e. does not rely on the registry, or installed components outside of the main installation directory. This means you can simply zip a KDE installation (including your app) and let the user download and unzip on their system.
This section needs improvements: Please help us to
cleanup confusing sections and fix sections which contain a todo Properly list the steps from that mail, and the comments from the thread in this section. |
See http://lists.kde.org/?l=kde-windows&m=127499109727979&w=2 .
Of course developers can create a fully custom installer for their app, e.g. based on NSIS.