* Try running a Qt application in the <tt>bin</tt> directory, such as linguist.exe

+

−

* If that works, try running a KDE application such as <tt>kwrite.exe</tt>.

+

=== Download needed packages ===

=== Download needed packages ===

−

A single program in the The K Desktop Environment depends on many other libraries and packages; that is why each .exe is comparatively small.

+

<br/>

−

The KDE Installer for Windows has some awareness of dependencies,

+

<br/>

−

but not complete.

+

[[File:installer-001.png|600px]]

−

So, the first few times you try to run an application you may see alerts about missing DLLs.

+

<br/>

+

When you run KDE-installer for the first time, you'll see the welcome screen. Since it's your first launch leave the checkbox below unchecked.

+

<br/>

+

<br/>

+

[[File:installer-002.png|600px]]

+

<br/>

+

Proceed to the next screen, where you choose the KDE4 installation directory. It can be anything you prefer, e.g. C:\KDE4.

+

<br/>

+

<br/>

+

[[File:installer-003.png|600px]]

+

<br/>

+

On the next screen, define who you are: End User or Developer. The End User installation installs only binary packages and libraries needed to run KDE application. Package Manager mode provides you also with the source code for all packages needed to build KDE from scratch. <br/> Then you need to decide what compiler to use - MinGW or MSVC.

+

<br/>

+

<br/>

+

[[File:installer-004.png|600px]]

+

<br/>

+

Proceed to the next screen and there choose the directory where all the downloaded packages will be stored. Let it be something like C:\KDE4-tmp or C:\KDE4-packages.

+

<br/>

+

<br/>

+

[[File:installer-005.png|600px]]

+

<br/>

+

The next screen will ask you to choose your internet connection type, particularly whether or not you're using a proxy. If you don't use a proxy server, just click 'Next'. If you are unsure of whether you're using proxy or if you have web browser configured to work with it properly, choose the second or the third option, according to your favourite web-browser. If you'd like to set all the settings manually - choose the last option and go ahead.

+

<br/>

+

<br/>

+

[[File:installer-006.png|600px]]

+

<br/>

+

When you click the 'Next' button the (currently, rather short) list of available servers will be loaded and you could choose the one closest to you.

+

<br/>

+

<br/>

+

[[File:installer-007.png|600px]]

+

<br/>

+

When you click 'Next', a list of available releases on the selected server will be shown. Depending on the server there may be stable and/or unstable release available. Some unstable releases may only be available from www.winkde.org because the kde mirrors provides only a limited range of unstable releases.

+

<br/>

+

<br/>

+

[[File:installer-008.png|600px]]

+

<br/>

+

After selecting a release an a click on the 'Next' button, the list of all available packages will be loaded and processed, providing you with the list of package groups you can select for further installation. The short description next to each group of packages should make your choice easier. Select the packages you need. Proceed to the next screen.

+

<br/>

+

<br/>

+

[[File:installer-009.png|600px]]

+

<br/>

+

Here you can see all the required dependencies, or software necessary to support the choices you've made. Click 'Next' to download them all.

+

<br/>

+

<br/>

+

[[File:installer-010.png|600px]]

+

<br/>

+

[[File:installer-011.png|600px]]

+

<br/>

+

After all the packages are downloaded they'll be unpacked and processed by the installer.

+

<br/>

+

<br/>

+

[[File:installer-012.png|600px]]

+

<br/>

+

The final window will tell that your KDE installation for Windows is complete.

+

<br/>

−

If you do not intend to build from source, do not click "all" and do not click "src", as you do not need to download the source for each package. ''Unclear whether you need lib for each''.

+

=== Issues with KDE Installer for Windows ===

+

If something goes wrong during installation, for example a file can't be replaced because it is still in use, the installer may still report successful completion. If you see any alert or failure message from the installer, when it completes, quit and re-run it.<br>

+

If that didn't help and you think it's a bug, please report to [mailto:kde-windows@kde.org]

−

There are two development systems for KDE on Windows,

+

== Testing your installation ==

−

Microsoft's Visual C and [http://en.wikipedia.org/wiki/MinGW MinGW].

+

Navigate to the <tt>bin</tt> directory.

−

Even if you are only running binaries and do not intend to build KDE4 yourself,

+

−

you need to choose between these because of the provided runtime environments.

+

−

You're free to decide which to take.

+

−

The KDE programs themselves are organized into several groups: kdeedu, kdegames, and kdegraphics.

+

See if you can run the Qt program assistant.exe.

+

Qt programs have fewer dependencies than a full-blown KDE application.

−

Here are some of the minimal packages you need to run a KDE application:

+

If that works, try running a simple KDE application, such as lskat.exe from the kdegames package.

−

: dbus-msvc, kdebase-msvc, kdewin32-msvc, qt-msvc, vcredist, ??

+

−

The Dependencies tab for a particular package lists some of the additional packages it needs.

+

Look into your start menu: there will be a new entry KDE 4.XX.XX Release. Below that folder you can find all the apps you installed.

−

However, the dependency checking currently only works for first-level dependencies

+

−

Other dependencies are not easy to determine in advance.

+

−

For example, if you install kdegames only with its dependencies,

+

−

you will not be able to start it because you also need libstreamanalyze

+

−

(for which you have to install the strigi package).

+

−

rhabacker: This is fixed in installer version > 0.8.4.

+

−

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries]] is a more complete list of libraries that a full installation needs.

+

=== Startup, shutdown, and diagnosing problems ===

+

The first KDE program you run should automatically invoke <tt>kdeinit4.exe</tt>, the KDE initialization app,

+

which starts background KDE applications and services like dbus-daemon, klauncher and kded4.

−

=== Issues with KDE Installer for Windows ===

+

The first time you save or open, another background application, kioslave, will start.

−

Currently no issues known. If you found an issue, please report to [mailto:kde-windows@kde.org].

+

−

== post-install steps ==

+

These background KDE applications and services remain running after you close KDE applications. If you want you can shut them down by running <tt>kdeinit4 --terminate</tt> from a command prompt.

−

You currently need to run a number of command-line programs to set up KDE. Here are the steps.

+

−

===Run update-mime-database===

+

You can run <tt>kdeinit4 --list</tt> from a command prompt to see what processes are running. <tt>kdeinit4</tt> has other useful options documented elsewhere.

−

Be sure that you have no KDE-related applications: run the Windows Task Manager (taskmgr.exe), switch to its Processes tab, and kill all occurences of dbus-daemon.exe, kded4.exe, kioslave.exe and klauncher.exe (and all other KDE apps).

+

−

Open a Windows command prompt (cmd.exe) and navigate to the directory where you installed KDE. Say you installed KDE to C:\KDE4, then run from the cmd.exe window:

+

== Fine-tuning ==

−

C:\KDE4> '''bin\update-mime-database C:\KDE4\share\mime'''

+

=== Common step: editing the kdeglobals file ===

−

This will give you a lot of warning message. Most of them you can easily ignore; even if you should set [[KDE_System_Administration/Environment_Variables#XDG_DATA_HOME|XDG_DATA_HOME]] or [[KDE_System_Administration/Environment_Variables#XDG_DATA_DIRS|XDG_DATA_DIRS]] it worked perfectly. If it says you should rerun update-mime-database as root then you're not within your installation directory.

+

Unless otherwise stated you make all the setting changes below by editing the <tt>kdeglobals</tt> file in the directory <tt>%APPDATA%\.kde\share\config\</tt> with any text editor (such as kwrite).

+

(Note that for versions older than 4.0.85 the file is in <tt>%USERPROFILE%\.kde\share\config\kdeglobals</tt>.)

+

%APPDATA% (and %USERPROFILE%) is different for different Windows users/versions/locales; in a command prompt, entering the command <b><tt>cd %APPDATA%</tt></b> will switch to it, effectively telling you what it is.

−

===Run kbuildsyscoca4===

+

===Set Oxygen style for widgets===

−

After finishing the previous step, run

+

The default KDE widget style on Windows is the native one. The Oxygen style installs with basic KDE installation (as a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:

−

C:\KDE4> '''bin\kbuildsycoca4 --noincremental'''

+

# edit kdeglobals

−

If this tells you that your disk is full (which is most probably not the case) you have still some executables from KDE running. Please close them and try again.

+

#locate the General section (a line containing the text "[General]"). If there is no General section, create one.

+

#Within the General section ([General]), edit the line containing <tt>widgetStyle=....</tt> so that it reads <tt>widgetStyle=oxygen</tt>. If there is no such <tt>widgetStyle=...</tt> line, create it.

+

Newly started applications should be displayed with the Oxygen style now.

−

Excuse us for the inconvenience &mdash; we hope for a better solution in the next release.

+

===Set Tahoma (Windows default font) for widgets===

+

To set it for a single user:

+

# edit kdeglobals

+

#locate the General section (a line containing the text "[General]"). If there is no General section, create one.

+

#Within the General section ([General]), add these two lines:

+

<tt>font=Tahoma<br/>

+

menuFont=Tahoma</tt>

−

== Testing your installation ==

+

Newly started applications should use this font now.

−

Navigate to the <tt>bin</tt> directory.

+

<b>Note</b>: this works for any font you have installed.

−

See if you can run the Qt program assistant.exe.

+

===Change the mouse to Double Click===

−

Qt programs have fewer dependencies than a full-blown KDE application.

+

To change the mouse to use double click, add a new section with a line:

+

<syntaxhighlight lang="ini">

+

[KDE]

+

SingleClick=false

+

</syntaxhighlight>

+

Newly started applications (Dolphin and Konqueror) should use double click now.

+

===Change locale and country settings===

+

From KDE Release 4.5.4 onwards KDE should automatically detect the correct country and language to use. If it detects the wrong country or language, or you want your KDE apps to use a different locale than your Windows system, then you will need to manually set the country by either installing the kdebase-workspace package and running SystemSettings, or by manually editing your kdeglobals file.

−

If that works, try running a simple KDE application, such as kruler.exe from the kdegraphics package.

+

For earlier versions you will need to manually set the country and locale in your kdeglobals file.

−

The first KDE application you run will start a console window in order to run the [http://en.wikipedia.org/wiki/D-Bus D-Bus daemon].

+

To manually change your locale settings in your kdeglobals file, add a new section with the lines:

−

+

−

== Fine-tuning ==

+

−

===Set Oxygen style for widgets===

+

−

The default KDE widget style on Windows is the native one. You already have Oxygen style installed (which is a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:

* Help > ''Program'' Handbook (often mapped to the [F1] key) does not work because the KDE Help Center is not available on Windows. This is due to its use of the K3Process interface and external dependencies not ported such as perl scripts, htdig, and other libraries.

+

−

** khelpcenter will be included in the next unstable release. The K3Process issues are fixed now. Perl scripts are disabled, which means there is no fulltext search. -- rhabacker

+

−

* Applications that try to play sounds might display an alert about "Multimedia Backend" problems. This requires the Windows backend for [http://phonon.kde.org/ Phonon].

KDE Installer for Windows

You can use this installer to download and install the
various binary packages that you need to run KDE applications on MS Windows.
KDE is free and open source so you can build all the applications "from scratch" from their source code;
but as a convenience for others,
volunteers create these pre-compiled packages and make them available on the Internet.

Disclaimer These are early days for KDE4 on Windows,
some programs work better than others and some fail to run altogether.

If you experience any problems please have a look into our mailing list.

You can also use the KDE Installer for Windows to install source code and the packages that you need to build KDE4 on Windows
(although if you are building KDE4 on Windows you may prefer to use the emerge system to build KDE and its requirements from latest source);
see Getting Started/Build/Windows.

Summary of Steps

Download and save the latest version of the installer from here to a directory, e.g. C:\KDE4

Try to run a KDE application from the windows start menu (see for KDE x.x.x Release entry)

Download needed packages

When you run KDE-installer for the first time, you'll see the welcome screen. Since it's your first launch leave the checkbox below unchecked.

Proceed to the next screen, where you choose the KDE4 installation directory. It can be anything you prefer, e.g. C:\KDE4.

On the next screen, define who you are: End User or Developer. The End User installation installs only binary packages and libraries needed to run KDE application. Package Manager mode provides you also with the source code for all packages needed to build KDE from scratch. Then you need to decide what compiler to use - MinGW or MSVC.

Proceed to the next screen and there choose the directory where all the downloaded packages will be stored. Let it be something like C:\KDE4-tmp or C:\KDE4-packages.

The next screen will ask you to choose your internet connection type, particularly whether or not you're using a proxy. If you don't use a proxy server, just click 'Next'. If you are unsure of whether you're using proxy or if you have web browser configured to work with it properly, choose the second or the third option, according to your favourite web-browser. If you'd like to set all the settings manually - choose the last option and go ahead.

When you click the 'Next' button the (currently, rather short) list of available servers will be loaded and you could choose the one closest to you.

When you click 'Next', a list of available releases on the selected server will be shown. Depending on the server there may be stable and/or unstable release available. Some unstable releases may only be available from www.winkde.org because the kde mirrors provides only a limited range of unstable releases.

After selecting a release an a click on the 'Next' button, the list of all available packages will be loaded and processed, providing you with the list of package groups you can select for further installation. The short description next to each group of packages should make your choice easier. Select the packages you need. Proceed to the next screen.

Here you can see all the required dependencies, or software necessary to support the choices you've made. Click 'Next' to download them all.

After all the packages are downloaded they'll be unpacked and processed by the installer.

The final window will tell that your KDE installation for Windows is complete.

Issues with KDE Installer for Windows

If something goes wrong during installation, for example a file can't be replaced because it is still in use, the installer may still report successful completion. If you see any alert or failure message from the installer, when it completes, quit and re-run it.
If that didn't help and you think it's a bug, please report to [1]

Testing your installation

Navigate to the bin directory.

See if you can run the Qt program assistant.exe.
Qt programs have fewer dependencies than a full-blown KDE application.

If that works, try running a simple KDE application, such as lskat.exe from the kdegames package.

Look into your start menu: there will be a new entry KDE 4.XX.XX Release. Below that folder you can find all the apps you installed.

Startup, shutdown, and diagnosing problems

The first KDE program you run should automatically invoke kdeinit4.exe, the KDE initialization app,
which starts background KDE applications and services like dbus-daemon, klauncher and kded4.

The first time you save or open, another background application, kioslave, will start.

These background KDE applications and services remain running after you close KDE applications. If you want you can shut them down by running kdeinit4 --terminate from a command prompt.

You can run kdeinit4 --list from a command prompt to see what processes are running. kdeinit4 has other useful options documented elsewhere.

Fine-tuning

Common step: editing the kdeglobals file

Unless otherwise stated you make all the setting changes below by editing the kdeglobals file in the directory %APPDATA%\.kde\share\config\ with any text editor (such as kwrite).
(Note that for versions older than 4.0.85 the file is in %USERPROFILE%\.kde\share\config\kdeglobals.)
%APPDATA% (and %USERPROFILE%) is different for different Windows users/versions/locales; in a command prompt, entering the command cd %APPDATA% will switch to it, effectively telling you what it is.

Set Oxygen style for widgets

The default KDE widget style on Windows is the native one. The Oxygen style installs with basic KDE installation (as a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:

edit kdeglobals

locate the General section (a line containing the text "[General]"). If there is no General section, create one.

Within the General section ([General]), edit the line containing widgetStyle=.... so that it reads widgetStyle=oxygen. If there is no such widgetStyle=... line, create it.

Newly started applications should be displayed with the Oxygen style now.

Set Tahoma (Windows default font) for widgets

To set it for a single user:

edit kdeglobals

locate the General section (a line containing the text "[General]"). If there is no General section, create one.

Within the General section ([General]), add these two lines:

font=Tahoma
menuFont=Tahoma

Newly started applications should use this font now.
Note: this works for any font you have installed.

Change the mouse to Double Click

To change the mouse to use double click, add a new section with a line:

[KDE]SingleClick=false

Newly started applications (Dolphin and Konqueror) should use double click now.

Change locale and country settings

From KDE Release 4.5.4 onwards KDE should automatically detect the correct country and language to use. If it detects the wrong country or language, or you want your KDE apps to use a different locale than your Windows system, then you will need to manually set the country by either installing the kdebase-workspace package and running SystemSettings, or by manually editing your kdeglobals file.

For earlier versions you will need to manually set the country and locale in your kdeglobals file.

To manually change your locale settings in your kdeglobals file, add a new section with the lines: