|
|
|
|
@ -80,6 +80,7 @@ |
|
|
|
|
<copyright> |
|
|
|
|
<year>2006</year> |
|
|
|
|
<year>2007</year> |
|
|
|
|
<year>2008</year> |
|
|
|
|
<holder>Michael Pyne</holder> |
|
|
|
|
</copyright> |
|
|
|
|
|
|
|
|
|
@ -91,8 +92,8 @@ |
|
|
|
|
|
|
|
|
|
<legalnotice>&FDLNotice;</legalnotice> |
|
|
|
|
|
|
|
|
|
<date>2007-05-01</date> |
|
|
|
|
<releaseinfo>1.4</releaseinfo> |
|
|
|
|
<date>2008-01-14</date> |
|
|
|
|
<releaseinfo>1.6</releaseinfo> |
|
|
|
|
|
|
|
|
|
<abstract> |
|
|
|
|
<para>&kdesvn-build; is a script which builds and installs &kde; directly from the sources found in the &kde; &subversion; repository.</para> |
|
|
|
|
@ -149,6 +150,13 @@ about packaging tools and requirements, common compilation pitfalls and |
|
|
|
|
strategies and information about running your new &kde; installation. |
|
|
|
|
</para> |
|
|
|
|
|
|
|
|
|
<para> |
|
|
|
|
In addition, the <ulink url="http://techbase.kde.org/">&kde; TechBase</ulink> |
|
|
|
|
wiki maintains a procedure for <ulink |
|
|
|
|
url="http://techbase.kde.org/index.php?title=Getting_Started/Build/KDE4">building |
|
|
|
|
&kde; from source code</ulink>. |
|
|
|
|
</para> |
|
|
|
|
|
|
|
|
|
<sect1 id="before-building"> |
|
|
|
|
<title>Preparing the System to Build &kde;</title> |
|
|
|
|
|
|
|
|
|
@ -180,7 +188,8 @@ in order to prepare and use the system installation correctly. |
|
|
|
|
strategy) you must install the development tools and libraries needed for &kde;. |
|
|
|
|
The complete list of required tools can be found from the |
|
|
|
|
<ulink url="http://www.kde.org/info/requirements/3.5.php">&kde; Compilation |
|
|
|
|
Requirements</ulink> page. |
|
|
|
|
Requirements</ulink> page. Requirements for the &kde; 4 series may be obtained |
|
|
|
|
from the <ulink url="http://techbase.kde.org/">KDE TechBase</ulink>. |
|
|
|
|
</para> |
|
|
|
|
|
|
|
|
|
<para>Here is a list of some of the things you will need:</para> |
|
|
|
|
@ -190,7 +199,7 @@ Requirements</ulink> page. |
|
|
|
|
|
|
|
|
|
<listitem><para>&autoconf; version 2.57, or higher. (&kde; 3 only)</para></listitem> |
|
|
|
|
|
|
|
|
|
<listitem><para>&cmake; 2.4.5, or higher.</para></listitem> |
|
|
|
|
<listitem><para>&cmake; 2.4.7, or higher.</para></listitem> |
|
|
|
|
|
|
|
|
|
<listitem><para>The &subversion; client program, including support for Secure |
|
|
|
|
HTTP (https). To ensure needed support, you can run |
|
|
|
|
@ -646,6 +655,12 @@ use on your computer. |
|
|
|
|
anonymous &subversion; servers.</para> |
|
|
|
|
</listitem> |
|
|
|
|
|
|
|
|
|
<listitem><para> |
|
|
|
|
Another speedup is provided by starting the build process for a module as soon |
|
|
|
|
as the source code for that module has been downloaded. (Available since |
|
|
|
|
version 1.6) |
|
|
|
|
</para></listitem> |
|
|
|
|
|
|
|
|
|
<listitem><para> |
|
|
|
|
Has excellent support for the <link linkend="using-qt-copy">qt-copy module</link>, |
|
|
|
|
including optionally applying bugfix and optimization patches to the qt-copy |
|
|
|
|
@ -1195,7 +1210,11 @@ set the environment variable <envar>CXXFLAGS</envar> during the build process. |
|
|
|
|
<entry>Overrides global</entry> |
|
|
|
|
<entry>Use this option to change the name a module is given on disk. For |
|
|
|
|
example, if your module was extragear/network, you could rename it to |
|
|
|
|
extragear-network using this option. |
|
|
|
|
extragear-network using this option. Note that although this changes the |
|
|
|
|
name of the module on disk, it is not a good idea to include directories |
|
|
|
|
or directory separators in the name as this will interfere with any |
|
|
|
|
<link linkend="conf-build-dir">build-dir</link> or |
|
|
|
|
<link linkend="conf-source-dir">source-dir</link> options. |
|
|
|
|
</entry> |
|
|
|
|
</row> |
|
|
|
|
|
|
|
|
|
@ -1411,6 +1430,14 @@ lower a priority &kdesvn-build; will set for itself. The default is 10. |
|
|
|
|
</entry> |
|
|
|
|
</row> |
|
|
|
|
|
|
|
|
|
<row id="conf-no-svn"> |
|
|
|
|
<entry>no-svn</entry> |
|
|
|
|
<entry>Overrides global</entry> |
|
|
|
|
<entry>If this option is set to true then &kdesvn-build; will not update the |
|
|
|
|
source code for the module automatically. It will still try to build the |
|
|
|
|
module if it normally would have tried anyways.</entry> |
|
|
|
|
</row> |
|
|
|
|
|
|
|
|
|
<row id="conf-no-rebuild-on-fail"> |
|
|
|
|
<entry>no-rebuild-on-fail</entry> |
|
|
|
|
<entry>Overrides global</entry> |
|
|
|
|
|