Getting Started/Build/Windows/emerge - Revision history

Fengchao: /* Introduction */ Clean up style.

2013-04-02T05:34:34Z

‎Introduction: Clean up style.

Winterz: warn about msys-git in your path

2012-12-16T15:02:36Z

warn about msys-git in your path

Darkstar: /* Check out using the 'git' command */ use /d switch for CD to also change the drive, if %KDEROOT% is not on C:

2012-10-05T22:28:08Z

‎Check out using the 'git' command: use /d switch for CD to also change the drive, if %KDEROOT% is not on C:

Djszapi: Update the wiki as emerge is available nowadays through Git

2012-09-22T23:34:48Z

Update the wiki as emerge is available nowadays through Git

SaroEngels: /* Configure the emerge tool */

2012-08-03T08:55:27Z

‎Configure the emerge tool

Djszapi: /* Using emerge */ Update the left-over documentation to python32

2012-07-09T11:03:51Z

‎Using emerge: Update the left-over documentation to python32

Djszapi: /* Check out using the 'git' command */ Add a helper text and command for cloning over http

2012-07-09T10:41:17Z

‎Check out using the 'git' command: Add a helper text and command for cloning over http

SaroEngels: /* [Optional, Advanced] emerge-boost-config.jam */

2012-03-02T22:54:23Z

‎[Optional, Advanced] emerge-boost-config.jam

SaroEngels: /* Configure the emerge tool */

2012-03-02T22:53:21Z

‎Configure the emerge tool

SaroEngels: /* Python interpreter */

2012-03-02T22:52:48Z

‎Python interpreter

@@ Line 3: / Line 3: @@
 == Introduction ==
 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:
-* it is easy for people to join us:
+=== Easy for people to join 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 Git 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.
-* it is easy for us to do (nightly/continuous/release/reproducable/...) builds:
+=== Easy for us to do build ===
 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.
-* it is easier to collaborate:
+=== Easy to collaborate ===
 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.

@@ Line 48: / Line 48: @@
 Note 0: '''Read the comments in that file very carefully'''
-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 from the path.'''
+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 from the path.'''  The same goes for msys-git, so make sure to remove c:\Program Files (x86)\git\bin from your path.
 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.'''

@@ Line 35: / Line 35: @@
 ==== Check out using the 'git' command ====
-*Option 1: With the ''git'' command line tool, you can accomplish this with the following commands:<pre>cd %KDEROOT%</pre>
+*Option 1: With the ''git'' command line tool, you can accomplish this with the following commands:<pre>cd /d %KDEROOT%</pre>
 **if you will only use anonymous (read-only) access to the KDE git repository:<pre>git clone git://anongit.kde.org/emerge.git</pre>
 **if the git and ssh ports are blocked, and only http is allowed, it is better to clone over the http port for getting (read-only) access to the KDE git repository:<pre>git clone http://anongit.kde.org/emerge.git</pre>

@@ Line 5: / Line 5: @@
 * it is easy for people to join 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.
+Now to get a development machine you need a Windows computer, need to install Python and Git 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.
 * it is easy for us to do (nightly/continuous/release/reproducable/...) builds:
 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.

← Older revision		Revision as of 08:55, 3 August 2012
Line 45:		Line 45:

	The kdesettings.bat script will be called by the main kdeenv.bat script.		The kdesettings.bat script will be called by the main kdeenv.bat script.
		+
		+	Note 0: '''Read the comments in that file very carefully'''

	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 from the path.'''		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 from the path.'''

@@ Line 122: / Line 122: @@
   KDECOMPILER : mingw
   KDESVNDIR   : C:\kderoot\svn
-  PYTHONPATH  : C:\python27
+  PYTHONPATH  : C:\python32
   DOWNLOADDIR : C:\kderoot\download

@@ Line 85: / Line 85: @@
 # Configure specific Python version.
-using python : 2.7 : C:\\Python27_x86 ;
+using python : 3.2 : C:\\Python32_x86 ;
 </syntaxhighlight>
-This way boost-python would be using the headers & libraries from C:\\Python27_x86 instead of the default one.
+This way boost-python would be using the headers & libraries from C:\\Python32_x86 instead of the default one.
 Please remember that for mingw compilers you must regenerate the import library for the python dll (also for the mingw 64bit compiler):
 <syntaxhighlight lang="text">
 R:\> emerge pexports
-R:\> pexports C:\Python27_x86\python27.dll > C:\Python27_x86\libs\python27.def
+R:\> pexports C:\Python32_x86\python32.dll > C:\Python32_x86\libs\python32.def
 </syntaxhighlight>
-NOTE: In case you generate the import library for the 64bit compiler, add the following line to the file python27.def:
+NOTE: In case you generate the import library for the 64bit compiler, add the following line to the file python32.def:
 <syntaxhighlight lang="text">
 Py_InitModule4 = Py_InitModule4_64
@@ Line 99: / Line 99: @@
 For both compilers you should now run:
 <syntaxhighlight lang="text">
-dlltool -d C:\Python27_x86\libs\python27.def -l C:\Python27_x86\libs\libpython27.dll.a
+dlltool -d C:\Python32_x86\libs\python32.def -l C:\Python32_x86\libs\libpython32.dll.a
 </syntaxhighlight>
 Now you should be able to do emerge -i boost-python-src without errors.

@@ Line 51: / Line 51: @@
 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.'''
-emerge has several branches which contain specific package versions. E.g. if you want to build the 4.7 branch of KDE (or one of the 4.7 releases) you should checkout the ''kde-4.7'' branch of emerge; in the ''master'' branch, you can find KDE ''master/trunk''. To view all branches, use the following command:
+emerge has several branches which contain specific package versions. E.g. if you want to build the 4.8 branch of KDE (or one of the 4.8 releases) you should checkout the ''kde-4.8'' branch of emerge; in the ''master'' branch, you can find KDE ''master/trunk''. To view all branches, use the following command:
 <pre>git branch -a</pre>
 To change the branch of emerge, do the following:
-<pre>cd emerge && git checkout kde-4.7</pre>
+<pre>cd emerge && git checkout kde-4.8</pre>
 === [Optional, Advanced] emergehosts.conf ===

@@ Line 18: / Line 18: @@
 === Python interpreter ===
-<tt>emerge.bat</tt> invokes an <tt>emerge.py</tt> script written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] programming language, so you first need to [http://www.python.org/download/ install the Python 2.7 Interpreter]. The ''python'' installation directory will be added to the PATH later by <tt>%KDEROOT%\etc\kdesettings.bat</tt> script.
+<tt>emerge.bat</tt> invokes an <tt>emerge.py</tt> script written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] programming language, so you first need to [http://www.python.org/download/ install the Python 3.2 Interpreter]. The ''python'' installation directory will be added to the PATH later by <tt>%KDEROOT%\etc\kdesettings.bat</tt> script.
 ''Beginning from the KDE 4.8 (including master and the frameworks branch) Python 3.2 will be required.''