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.

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.

Note that the approaches are not mutually exclusive, and in particular it is probably always a good idea to provide an emerge script.

+

+

+

= Compile from source =

== Emerge ==

== Emerge ==

Line 30:

Line 31:

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.

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.

+

+

= Repository based =

== KDE windows installer ==

== KDE windows installer ==

Line 58:

Line 61:

# Profit

# Profit

+

== Quick and dirty pack ==

+

+

You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.

+

+

=== Advantages ===

+

+

* Should be real easy for you create.

+

+

=== Disadvantages ===

+

+

* You'll have to make sure your users understand the fine points, e.g. using the correct type of KDE installation, installing in the correct directory, etc.

Packaging / Distributing KDE applications for Windows – Overview

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.

Compile from source

Emerge

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.

Procedure

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.

Repository based

KDE windows installer

The KDE windows installer is the officially recommended way for end-users to install the KDE SC, in whole or in part.

Advantages

Full package management, including various packages, sources, headers.

Includes update capabilities

Downloads / installs only what is needed

Great if user wants to install a whole collection of KDE apps.

Disadvantages

Centralized? If your package is not part of the official KDE SC, you'll have to nag someone to get it into the installer.

More complex than most other windows installers.

Arguably too complex for some end users.

Cumbersome esp. if user wants to install only one specific KDE app.

Needs internet connection

Procedure

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!

Write an emerge script for your app

???

Profit

Quick and dirty pack

You can simply zip up the files needed for your package, and tell your users to unpack them in the KDE installation root.

Advantages

Should be real easy for you create.

Disadvantages

You'll have to make sure your users understand the fine points, e.g. using the correct type of KDE installation, installing in the correct directory, etc.

Procedure

Use

[mingw32-]make install DESTIR=Some\temporary\folder

Zip up Some\temporary\folder (should contain at least a "bin"-subdirectory).

As stand-alone application

Installation bundle

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.

Advantages

Easy to package

Easy to install in a single step

Can use a specific setup, including specific version of KDE, specific compiler, customized default settings, etc.

Disadvantages

Need to offer/distribute sources!

Wastes download size, and disk storage, if user want more than just one KDE application.

No easy way to update / extend KDE installation.

Procedure

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.