* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

−

* from the '''KDE''' category select the kdeedu bin and source package - this will also select all depending packages

+

* choose the '''all''' category and then select the following packages

+

** the kdeedu bin and source package - this will also select all depending packages

+

** automoc, cmake, gcc-mingw and perl package

−

* from the '''devel-tools''' category select the cmake and gcc-mingw package

+

* then select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-mingw, kdebase-runtime-mingw and qt-mingw are required.

−

+

−

* from the '''KDE''' category select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-mingw, kdebase-runtime-mingw and qt-mingw are required.

+

* install the selected packages using the installer. For the gcc-mingw package use \Mingw as installation root.

* install the selected packages using the installer. For the gcc-mingw package use \Mingw as installation root.

Revision as of 22:55, 27 November 2008

This page describes (re)building of KDE binary packages using the kdewin distribution.

Applications build in this way will not have debugging support because the packages build in release mode do not have any debug symbols. If you need debug symbols you should use the Windows emerge tool

It is assumed that KDE is installed using the KDEWin gui or console installer in %PROGRAMFILES%\kde and a developer tries to recompile the kdeedu binary package.
It is also assumed that the KDE installation tree is empty or contains only packages for the related compiler.

(Re)building packages for MS Visual Studio C++

from the KDE category select the kdeedu bin and source package - this will also select all depending packages

from the devel-tools category select the cmake, one of vcexpress-xx-msvc and the psdk-msvc package

from the KDE category select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-msvc, kdebase-runtime-msvc and qt-msvc are required.

install the selected packages using the installer.

open a Visual Studio command prompt

set the required environment for the MS Platform SDK e.g. if your are using the 2003 R2 Release of the Platform SDK the command line looks like that:

the kdeedu bin and source package - this will also select all depending packages

automoc, cmake, gcc-mingw and perl package

then select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-mingw, kdebase-runtime-mingw and qt-mingw are required.

install the selected packages using the installer. For the gcc-mingw package use \Mingw as installation root.

add bin subdirectory of the mingw installation dir to the PATH environment variable

set PATH=\Mingw\bin;%PATH%

add bin subdirectory of the kde installation dir to the PATH environment variable