{{Note|It is recommended to install Visual studio into a path not containing spaces. To do this, change the installation path from the proposed ..\Program Files\ to something like c:\vc9.}}

−

Express Edition users: If you want to generate project files for Visual C++ then you must add the Platform SDK include and library directory to the default directories of the IDE:

+

{{warning|Visual Studio 2005 SP1 or free (as in beer) Express 2005 are no longer supported. Moreover the Express version is not available at microsoft.com.}}

−

<pre>

+

====Visual Studio 2008 SP1====

−

Open Visual C++, go to Tool->Options

+

There is not much to do - installer of the commercial version sets up the environment. Just do not forget to run <tt>vcvarsall.bat</tt> to set your environment variables.

−

in "Projects and Solutions" go to "VC++ Directories"

+

−

On the right add the paths to your Platform SDK files:

+

====Visual Studio 2008 SP1 Express Edition====

−

for "Library Files": YOUR_PLATFORM_SDK_PATH\lib

+

Install it using the Web Install (downloader) at [http://www.microsoft.com/express/download/ http://www.microsoft.com/express/download]. It takes about 130 MB of download, assuming no MS SQL Server is selected.

−

for "Include Files": YOUR_PLATFORM_SDK_PATH\include

+

−

</pre>

+

The installer also downloads the Windows SDK. It is installed into %PROGRAMFILES%\Microsoft SDKs\Windows.

+

Only version 6.0a is installed by the Visual Studio 2008 Express installer, while 6.1 is required to compile KDE components. So also download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=e6e1c3df-a74f-4207-8586-711ebe331cdc&displaylang=en version 6.1, i.e. Windows SDK for Windows Server 2008] by hand. See also the [http://msdn.microsoft.com/en-us/windowsserver/dd146047.aspx Which SDK is Right for Me?] document.

* use the most recent binaries from here [http://www.cmake.org/files/v2.4/ http://www.cmake.org/files/v2.4/] (the filename should be like <tt>cmake-2.4.?-win32-x86.zip</tt>; you can also pick an .exe file instead of .zip). Make sure you use at least cmake 2.4.5

+

You can get the most recent binaries from [http://www.cmake.org/HTML/Download.html here]. Use the Win32 Installer or the zip archive. Make sure you use at least cmake 2.4.5

−

* or get CMake from [http://cmake.org/HTML/Download.html#cvs CVS] and compile it yourself

+

−

+

−

Install cmake in a path without spaces to avoid troubles (at least under win2k).

+

−

+

−

=== Perl ===

+

−

Perl is a script language used to generate files. Install a Perl for Windows, e.g. ActivePerl from http://www.activestate.com

+

−

=== win32libs ===

+

On Windows 2000, it's recommended to install cmake in a path without spaces to avoid troubles.

−

''win32libs'' contains a collection of libraries not available by default on Windows. See [[Getting_Started/Build/KDE4/Windows/3rd-party_libraries|3rd-party libraries required for KDElibs 4]].

+

== Compile and Install additional libraries ==

== Compile and Install additional libraries ==

Line 41:

Line 40:

=== D-Bus for Windows ===

=== D-Bus for Windows ===

−

This library shouldn't be installed with the installer, you should rather [[Getting_Started/Build/KDE4/Windows/Building DBus|compile]] it yourself.

+

This library can be downloaded and installed with the installer (use the package name dbus-msvc) or you can [[Getting_Started/Build/KDE4/Windows/Building DBus|compile]] it by yourself.

=== Qt 4 ===

=== Qt 4 ===

−

This Framework can be downloaded with the installer, or you can [[Getting_Started/Build/KDE4/Windows/Building Qt 4|build it on your own]].

+

This Framework can be downloaded with the installer, or you can [[Getting_Started/Build/Windows/Building Qt 4|build it on your own]].

=== KDESupport Libraries ===

=== KDESupport Libraries ===

−

There are several libraries which will be required for building kdelibs. [[Getting Started/Build/KDE4/Windows/Building KDESupport Libraries|You may want to compile them yourself]] or simply download them using the KDEWin-Installer. You will need:

+

There are several libraries which will be required for building kdelibs. [[Getting Started/Build/Windows/Building KDESupport Libraries|You may want to compile them yourself]] or simply download them using the KDEWin-Installer. You will need:

*kdewin32 (compiled with msvc)

*kdewin32 (compiled with msvc)

*strigi

*strigi

*soprano

*soprano

*qca2

*qca2

+

*qimageblitz

−

=== shared-mime-info ===

+

=== Environment Settings ===

−

The shared-mime-info package, is the freedesktop MIME standard used now by KDE. Download update-mime-database-*.*-*-bin.zip from

+

To set up a build environment, follow the steps over [[Getting Started/Build/Windows/Environment|here]]. '''If you have Cygwin installed, please be sure to remove Cygwin's /bin out of your path.'''

−

http://82.149.170.66/kde-windows/win32libs/zip/single/ and unpack the archive to kde4/ directory to get share/mime/ directory and bin/update-mime-database.exe program.

+

== Build KDElibs ==

== Build KDElibs ==

Check out the sources and make another build directory at the same level as kdelibs:

Check out the sources and make another build directory at the same level as kdelibs:

<pre>

<pre>

−

cd {KDE_SOURCE_DIR}\trunk

+

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs

−

svn up -N KDE

+

cd ..

−

cd KDE

+

−

svn up kdelibs

+

mkdir kdelibs-build

mkdir kdelibs-build

cd kdelibs-build

cd kdelibs-build

Line 69:

Line 66:

Now you have to add some paths to your PATH environment variable simliar to this:

Now you have to add some paths to your PATH environment variable simliar to this:

*Don't use an automoc4 executable with spaces in the path, or you will get strange error messages when running nmake (seems to be a nmake bug)

== Going further: kdepimlibs ==

== Going further: kdepimlibs ==

Line 106:

Line 105:

=== Requirements ===

=== Requirements ===

kdepimlibs require:

kdepimlibs require:

−

* [http://boost.org/ boost libraries]. Download the tarball. As boost is consisted of headers only, unpack the tarball and copy <tt>boost</tt> subdirectory to <tt>%KDEDIR%\include</tt>. Then add use <tt>set BOOST_ROOT=%KDEDIR%\include</tt> (you may want to add it to your <tt>environment.bat</tt> file as well).

+

*[http://boost.org/ boost libraries]. Download the tarball. As boost is consisted of headers only, unpack the tarball and copy <tt>boost</tt> subdirectory to <tt>%KDEDIR%\include</tt>. Then add use <tt>set BOOST_ROOT=%KDEDIR%\include</tt> (you may want to add it to your <tt>environment.bat</tt> file as well).

This is a program that lets you easily install all the requirements for building kdelibs. It also has a list of tools in its list that are helpful and needed, like the mingw compiler suite, subversion clients, debugging tools and so on.

boost libraries. Download the tarball. As boost is consisted of headers only, unpack the tarball and copy boost subdirectory to %KDEDIR%\include. Then add use set BOOST_ROOT=%KDEDIR%\include (you may want to add it to your environment.bat file as well).

Little cms library. Download the newest lcms-1.??.zip from [1] and uncompress. To build it with msvc, go to Projects subdir and choose a subdir for your compiler (i.e. Vc7 or Vc2005).

Then you will see lcms.sln solution file - you can click it to open in the msvc IDE. But first, you need to fix some paths in the project files. You probably have %KDEDIR%\lib\jpeg.lib, not libjpeg.lib, so edit tifficc.vcproj, tiffdiff.vcproj and jpegicc.vcproj and change libjpeg.lib to jpeg.lib in AdditionalDependencies variable. Then add full path to your %KDEDIR%\include directory (where tiffio.h resides) in AdditionalIncludeDirectories variable, (note: do it by expanding KDEDIR environment variable, i.e the result should be like:

AdditionalIncludeDirectories="..\..\include;f:\kde4\include"

Then add AdditionalLibraryDirectories="c:\your\path\to\kde\lib" line just after every two occurences of AdditionalIncludeDirectories=. All the changes are presented in this pseudo-patch (change f:\ paths to your KDEDIR location!).

You probbaly want to skip building Python wrapper, so click on Build->Configuration Manager menu command and check off "Build" in "Python" line.