Getting Started/Build/Historic/KDE4 Windows: Difference between revisions

From KDE TechBase
(→‎Download needed packages: notes from Ben Aceler)
m (fix the download link)
 
(146 intermediate revisions by 19 users not shown)
Line 1: Line 1:
{{note|Perhaps actual developers should summarize status of KDE4 on Windows here, while we encourage users to describe their experiences on the [[Talk:{{PAGENAME}}|Talk page?]]}}
 
 
{{warning|These instructions are very old, and you probably want to go here: [https://community.kde.org/Windows] instead.}}


== KDE Installer for Windows ==
== KDE Installer for Windows ==
Line 6: Line 8:
KDE is free and open source so you can build all the applications "from scratch" from their source code;
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,
but as a convenience for others,
volunteers create these precompiled packages and make them available on the Internet.
volunteers create these pre-compiled packages and make them available on the Internet.


'''Disclaimer''' These are early days for KDE4 on Windows,
'''Disclaimer''' These are early days for KDE4 on Windows,
some programs work better than others and some fail to run altogether.
some programs work better than others and some fail to run altogether.
'''If you experience any problems please have a look into our [http://lists.kde.org/?l=kde-windows&r=1&w=2| 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
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);
(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/KDE4/Windows]].
see [[Getting Started/Build/Windows]].
 


=== Summary of Steps ===
=== Summary of Steps ===
* Visit http://download.cegit.de/kde-windows/installer
* Download and save the latest version of the installer from [http://download.kde.org/stable/kdewin/installer/kdewin-installer-gui-latest.exe here] to a directory, e.g. <tt>C:\KDE4</tt>
* Download and save the latest version to a directory, e.g. <tt>C:\KDE4</tt>
* Run the installer, download and install what you need (see [[#Download needed packages|Download needed packages]] below).
* Run the installer, download what you need (see [[#Download needed packages]] below).
* Try to run a KDE application from the windows start menu (see for KDE x.x.x Release entry) 
* Add your lib directory, e.g. <tt>C:\KDE4\lib</tt> to your Windows %PATH%.  (Start > Control Panel > System > Advanced > Environment Variables, double-click the Path System Variable and this to your path separated by semicolon.)
* Add a KDEDIRS environment variable (Start > Control Panel > System > Advanced > Environment Variables, click [New] User variable and create Variable name <tt>KDEDIRS</tt> with Variable value the directory where you installed KDE4, e.g. <tt>C:\KDE4</tt>).
* 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>kruler.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.
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''.
<br/>
 
<br/>
There are two development systems for KDE on Windows,
[[File:installer-002.png|600px]]
Microsoft's Visual C and [http://en.wikipedia.org/wiki/MinGW|MinGW].
<br/>
Even if you are only running binaries and do not intend to build KDE4 yourself,
Proceed to the next screen, where you choose the KDE4 installation directory. It can be anything you prefer, e.g. C:\KDE4.
you need to choose between these.
<br/>
As of October 2007, the former is more stable, so when you have a choice of packages in the KDE Installer for Windows, prefer the -msvc version.
<br/>
 
[[File:installer-003.png|600px]]
The KDE programs themselves are organized into several groups: kdeedu, kdegames, and kdegraphics.
<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.
Here are some of the minimal packages you need to run a KDE application:
<br/>
: dbus-msvc, kdewin32-msvc, qt-msvc, vcredist, ??
<br/>
 
[[File:installer-004.png|600px]]
The Dependencies tab for a particular package lists some of the additional packages it needs.
<br/>
However, the dependency checking currently only works for first-level dependencies
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.
Other dependencies are not easy to determine in advance.
<br/>
For example, if you install kdegames only with its dependencies,
<br/>
you will not be able to start it because you also need libstreamanalyze
[[File:installer-005.png|600px]]
(for which you have to install the strigi package).
<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/>


[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries]] is a more complete list of libraries that a full installation needs.
=== 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]


If a download fails, then the KDE Installer fails.
=== Additional software that you may want to install ===
If you have a broken file, you need to delete it
In a few special cases applications included in the KDE on Windows Installer need [[/additional_software_needed|additional software]] to be fully functional. You will have to install this, manually.
and then restart the KDE Installer to download it again.
You can also download and unpack files manually.


== Testing your installation ==
== Testing your installation ==
Line 63: Line 98:
Qt programs have fewer dependencies than a full-blown KDE application.
Qt programs have fewer dependencies than a full-blown KDE application.


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


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].
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.


== Status ==
=== 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.
http://techbase.kde.org/Projects/KDE_on_Windows/Installation
The first time you save or open, another background application, kioslave, will start.


Using the kdewin-installer-gui-0.8.1-2.exe to install packages, dbus-daemon.exe starts up, and many games run.
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.


It seems running kbuildsycoca4.exe by hand helps applications like KStars and Okular to run.
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.


There are problems with the file open dialog:
==  Fine-tuning ==
* Besides I/O errors if you do not have KDEDIRS set (see elsewhere), you may see "Windows - No Disk" exceptions for each empty removable drive on your computer (floppy disk, CD-ROM, etc.). Click [Continue] for each one.
Find some useful information on how to modify the behavior of KDE applications [[../Fine-tuning|here]].


[[Category: MS Windows]]
[[Category: MS Windows]]

Latest revision as of 09:46, 7 September 2016


Warning
These instructions are very old, and you probably want to go here: [1] instead.


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
  • Run the installer, download and install what you need (see Download needed packages below).
  • 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 [2]

Additional software that you may want to install

In a few special cases applications included in the KDE on Windows Installer need additional software to be fully functional. You will have to install this, manually.

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. http://techbase.kde.org/Projects/KDE_on_Windows/Installation 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

Find some useful information on how to modify the behavior of KDE applications here.