m (→Emerge works, now what?)
(Add a note about the short paths option)
|Line 119:||Line 119:|
to get some help on usage.
to get some help on usage.
== Setting up a compiler ==
== Setting up a compiler ==
emerge is a tool to build the KDE sources and its third-party requirements on MS Windows. It is the easy way to build KDE on MS Windows.
Emerge is a tool that can build the different parts of KDE and its dependencies under Windows. We created this tool to automate and simplify the build process under Windows. We try to build all packages that we offer in the KDE installer with emerge. That has some advantages for us:
Before emerge it was quite some work to set a system up for development. There were some quirks, which were documented in some mailing lists, but you had to remember them or you ran into an already solved problem again, etc. Now to get a development machine you need a Windows computer, need to install Python and Subversion and do the emerge checkout. Then execute emerge to build what you want to build. This is easy for developers coming from Windows to KDE, and also for KDE developers coming to Windows.
With emerge you can build the whole software stack (low-level libs, Qt, kdelibs, things above that) with only one command. You can start that build, and some hours later you can check if it worked, or if something broke. So we can spot problems easier and earlier. We can also start with a "naked" Windows computer without any other installed software and bootstrap kde on it. That ensures, that no hidden dependencies on some pieces of software sneak in, because then the builds on a "naked" computer would break and show the problem.
We can test the same emerge build description for a package on different Windows versions/computers before we do binary releases. People can also add build descriptions for new packages to the Subversion repository.
This emerge tool was inspired by the Gentoo emerge tool.
Create a directory if possible in your harddrive's root e.g. C:\kderoot or D:\kderoot (You will need this PATH later). This directory will contain the whole kde installation later. We will refer to it as %KDEROOT%.
emerge.bat invokes an emerge.py script written in Python programming language, so you first need to install the Python 2.6 Interpreter. The python installation directory will be added to the PATH later by %KDEROOT%\etc\kdesettings.bat script.
The latest source code for Windows emerge and the rest of KDE is stored in a repository created and managed using the Subversion version control tool. You need a Subversion client for the first checkout. There are at least two applications:
Note 1: If you experience problems with the checkout of Qt (Subversion doesn't work correctly) please remove any other Subversion binaries out of the path that you do have. The different versions of the Apache portable runtime (APR) are incompatible!
Note 2: Make sure to use a copy of Subversion that was built on Windows so that checked-out files do not use UNIX line endings. If you check out with UNIX line endings, the patch program will fail when attempting to apply a patch whose line endings don't match the system's.
The source code of the emerge tool and the recipes for creating KDE packages are located at svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge, which is an URL based on Subversion-specific svn protocol.
You need to check out the source code from the emerge Subversion directory into a new directory, which in this example we will call %KDEROOT%.
svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge
svn co --username yourusername https://svn.kde.org/home/kde/trunk/kdesupport/emerge
svn co svn+putty://svn.kde.org/home/kde/trunk/kdesupport/emerge
This would result with:
Error validating server certificate for 'https://svn.kde.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: svn.kde.org - Valid: from Wed, 11 May 2005 09:08:21 GMT until Sat, 09 May 2015 09:08:21 GMT - Issuer: SVN, KDE e.V., Nuernberg, Bavaria, DE - Fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx (R)eject, accept (t)emporarily or accept (p)ermanently?
enter p here to permanently accept the certificate:
Authentication realm: <https://svn.kde.org:443> KDE SVN account Password for 'yourusername': *************** A emerge\kdeenv.bat A emerge\portage A emerge\portage\kdesupport [....]
The password and cache for the certificates is saved in %APPDATA%\Subversion\auth directory.
After the checkout you should have the directory %KDEROOT%\emerge. If you don't, you move your emerge directory to that location.
The kdesettings.bat script will be called by the main kdeenv.bat script.
Note 1: Be sure that you neither have the msys/bin nor the cygwin/bin in your path. If so you have to definitely remove it.
Note 2 from a user: The applications gimp, inkscape and graphviz are also a problem. To make sure that there's nothing wrong I stripped my path to contain only what I needed to build.
Note 3(from another user): be careful when renaming the file to "kdesettings.bat" it is easy to end up with "kdesettings.bat.bat" instead of what you want since Windows(by default) will not show the the file extension part of a file.
I am getting the following error even though subversion is installed: emerge fatal error: required subversion package not installed
To use emerge you need to start a console window and point that to %KDEROOT%\emerge. For example:
C: cd \%KDEROOT%\emerge
Then you have to execute
This tells emerge about your environment settings (e.g. paths). It will load your configuration from %KDEROOT%\etc\kdesettings.bat. It should not give any error messages, otherwise emerge will not work as expected. The output should look similar to this one (of course with your paths):
C:\kderoot\emerge>kdeenv.bat kdesettings.bat executed KDEROOT : C:\kderoot KDECOMPILER : mingw KDESVNDIR : C:\kderoot\svn PYTHONPATH : C:\python25 DOWNLOADDIR : C:\kderoot\download
Now you should be able to use emerge. Type
to get some help on usage.
Note: There is a short path option in kdesettings which you will need if you want to build Qt in a directory that has a pathlenght of more then around 5 characters. This problem is due to limitations of the command line length and the Qt build system.
Currently emerge supports both the MinGW and MS Visual C++ (msvc) compilers. We did not add dependencies for the compilers, so you have to make sure to install a compiler by yourself. There are three ways to set up a compiler for emerge. We assumed you have set KDECOMPILER variable properly in the %KDEROOT%\etc\kdesettings.bat.
In the following sections you can find information on how to install or reuse an existing compiler.
Let emerge install the MinGW compiler:
To install the MinGW ("Minimalist GNU for Windows") compiler with emerge, type
and wait until it is finished.
If you encounter an error like
Assertion failed: hunk, file ../patch-2.5.9-src/patch.c, line 354
try to edit line 51 of file mingw-x.y.z.py (%KDEROOT%\emerge\portage\dev-util\mingw) by adding the --binary after -p1 parameter. The line should then look like this:
cmd = "cd %s && patch -p1 --binary < %s" % \
This is probably because the different line break types (Linux vs Dos) in the files and the bug in patch.exe. Althought this is an ugly hack and should be fixed somewhere else, it works for the current versions of patch (2.5.9) and mingw (3.4.5).
If you encounter an error like:
IOError: [Errno 2] No such file or directory: 'c:\\kderoot\\bin\\mingwm10.dll'
Then try creating the c:\kderoot\bin directory first.
This option is not recommended for now, because it only adds one more point of failure, and does not gain something in comparison to the option above.
NOTE from a user: be sure that path to \mingw\bin has been set correctly, by default it is pointing to: %KDEROOT%\mingw\bin which does not apply to most installations. If you see an error about cc1plus not being found, either add MinGW's \libexec\gcc\mingw32\3.4.5 to your PATH (in command line set PATH=%PATH%;path\to\directory) variable or copy the contents of this directory to MinGW's bin directory. The prior is preferred.
Under Vista, the mingw directory may need to be moved to c:\ in order to compile properly.
You need to point emerge to an existing msvc installation. To do that, execute vcvarsall.bat before running %KDEROOT%\emerge\kdeenv.bat. In recent versions this is run automatically for you from kdeenv.bat if configured properly in kdesettings.bat. Check your kdesettings.bat file to know if you need to run this manually or not.
Notes related to Vista:
Once you have emerge and a compiler installed and working, try:
You are now ready to start building KDE, it is recommended to enter emerge kdebase-apps. This command will automatically resole the required dependencies and perform the following steps:
It is strongly recommened you do not choose to manually install any of the utilities and libraries yourself, as you may install the wrong version and cause installation failures. Instead allow emerge to resolve the dependencies for you.
Every time you want to update or install a pacjake, you should first update your emerge checkout to ensure you are using the latest package recipies.
emerge package performs the separate actions --fetch, --unpack, --compile, --install, --manifest, and --qmerge.
There are some options that can be used when building with emerge.
|Command line switch||Command line argument||Description|
|-v||EMERGE_VERBOSE||This option sets the verbosity level. Currently the highest verbosity level is 3 (-v -v -v). A verbosity level of 0 should give no output and equals to -q. You can set EMERGE_VERBOSE=3 instead in the environment of the commandline or within your kdesettings.bat file.|
|--nocopy||EMERGE_NOCOPY||This very useful option suppresses copying the sources from the local Subversion tree to a directory within the build directory. It shouldn't be used while packaging; in the other cases it reduces the amount of harddisk used though and removes the copying time. You can set EMERGE_NOCOPY=True or =False instead.|
|--offline||This option suppresses the update step of the local tree - which needs some time. Be aware though that you have to have existing sources already if you want to use this option.|
|-t||EMERGE_BUILDTESTS||This option enables or disables KDE4 buildtests for KDE modules. Other packages will not change. Use EMERGE_BUILDTESTS=True or =False.|
|--buildtype=||Debug||This option enables full debugging mode for the build. Recommended if you plan to debug the runtime or provide more valuable feedback to developers about software defects. You can also change the 'set EMERGE_BUILDTYPE=RelWithDebInfo' line in the kdesettings.bat file.|
emerge --unmerge packagename --noclean --target=svnHEAD packagenameto update packagename from the Subversion and compile it without removing the build dir.
Replace ** with your lowercase alpha-2 country code, e.g. pl for Poland. You can edit your $HOME/.kde/share/config/kdeglobals file instead to alter your local settings, not for all users.
emerge can mostly cooperate with the kdewin-installer but we're currently still working on some packages which are packaged in a wrong way. It is not recommended to use another layout then installer for directory_layout in the kdesettings.bat anymore (see that file for more detailed information).
emerge creates lots of files in \kderoot\tmp during build. After a package is successfully installed (check \kderoot\etc\portage\installed or the directory \kderoot\manifest\), you can delete its temporary directory.
Windows emerge is derived from the Gentoo portage system, but we are currently not enforcing compatibility. If you have questions about that please contact us at the channel #kde-windows on irc.freenode.net.