<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
  <!ENTITY kappname "kdesrc-build">
  <!ENTITY package "kdesdk">
  <!ENTITY % addindex "IGNORE">
  <!ENTITY % Estonian  "INCLUDE"
> <!-- Change language only here -->
  <!ENTITY kdesrc-build "<application
>kdesrc-build</application
>">
  <!ENTITY BSD '<acronym
>BSD</acronym
>'>
  <!ENTITY git '<application
>Git</application
>'>
  <!ENTITY cmake '<application
>CMake</application
>'>
  <!ENTITY make '<application
>Make</application
>'>
  <!ENTITY ssh '<application
>SSH</application
>'>
  <!ENTITY cron '<application
>Cron</application
>'>
  <!ENTITY subversion '<application
>Subversion</application
>'>
  <!ENTITY sudo '<application
>Sudo</application
>'>
  <!ENTITY url '<acronym
>URL</acronym
>'>

  <!-- These define shortcut entities for some of the configuration options.
       Just add them as necessary.
  -->

  <!ENTITY configure-flags '<link linkend="conf-configure-flags"
>configure-flags</link
>'>
  <!ENTITY kdedir '<link linkend="conf-kdedir"
>kdedir</link
>'>
  <!ENTITY qtdir '<link linkend="conf-qtdir"
>qtdir</link
>'>
  <!ENTITY build-dir '<link linkend="conf-build-dir"
>build-dir</link
>'>
  <!ENTITY module-base-path '<link linkend="conf-module-base-path"
>module-base-path</link
>'>
  <!ENTITY override-url '<link linkend="conf-override-url"
>override-url</link
>'>
  <!ENTITY source-dir '<link linkend="conf-source-dir"
>source-dir</link
>'>
  <!ENTITY email-address '<link linkend="conf-email-address"
>email-address</link
>'>
  <!ENTITY email-on-compile-error '<link linkend="conf-email-on-compile-error"
>email-on-compile-error</link
>'>
  <!ENTITY colorful-output '<link linkend="conf-colorful-output"
>colorful-output</link
>'>
  <!ENTITY tag '<link linkend="conf-tag"
>tag</link
>'>
  <!ENTITY branch '<link linkend="conf-branch"
>branch</link
>'>
  <!ENTITY do-not-compile '<link linkend="conf-do-not-compile"
>do-not-compile</link
>'>
  <!ENTITY checkout-only '<link linkend="conf-checkout-only"
>checkout-only</link
>'>
  <!ENTITY svn-server '<link linkend="conf-svn-server"
>svn-server</link
>'>
  <!ENTITY make-install-prefix '<link linkend="conf-make-install-prefix"
>make-install-prefix</link
>'>
  <!ENTITY niceness '<link linkend="conf-niceness"
>niceness</link
>'>
  <!ENTITY set-env '<link linkend="conf-set-env"
>set-env</link
>'>
  <!ENTITY libpath '<link linkend="conf-libpath"
>libpath</link
>'>
  <!ENTITY binpath '<link linkend="conf-binpath"
>binpath</link
>'>

  <!-- These define shortcut entities for some of the command line options.
       Just add them as necessary.
  -->
  <!ENTITY cmd-nice '<link linkend="cmdline-nice"
>--nice</link
>'>
  <!ENTITY cmd-ignore-modules '<link linkend="cmdline-ignore-modules"
>--ignore-modules</link
>'>
  <!ENTITY cmd-resume-from '<link linkend="cmdline-resume-from"
>--resume-from</link
>'>
  <!ENTITY cmd-resume-after '<link linkend="cmdline-resume-after"
>--resume-after</link
>'>
  <!ENTITY cmd-reconfigure '<link linkend="cmdline-reconfigure"
>--reconfigure</link
>'>
  <!ENTITY cmd-refresh-build '<link linkend="cmdline-refresh-build"
>--refresh-build</link
>'>
]>

<book lang="&language;">

<bookinfo>
<title
>&kdesrc-build; Script Manual</title>

<authorgroup id="authors">
<author
><firstname
>Michael</firstname
><surname
>Pyne</surname
> <affiliation
><address
><email
>mpyne@kde.org</email
></address
></affiliation>
</author>
<author
><firstname
>Carlos</firstname
><surname
>Woelz</surname
> <affiliation
><address
><email
>carloswoelz@imap-mail.com</email
></address
></affiliation>
</author>


<othercredit role="translator"
><firstname
>Marek</firstname
> <surname
>Laane</surname
> <affiliation
><address
><email
>bald@smail.ee</email
></address
></affiliation
><contrib
>Tõlge eesti keelde</contrib
></othercredit
> 

</authorgroup>

<copyright>
<year
>2006</year>
<year
>2007</year>
<year
>2008</year>
<year
>2009</year>
<year
>2010</year>
<holder
>Michael Pyne</holder>
</copyright>

<copyright>
<year
>2005</year>
<holder
>Carlos Woelz</holder>
</copyright>

<legalnotice
>&FDLNotice;</legalnotice>

<date
>2010-01-30</date>
<releaseinfo
>1.12</releaseinfo>

<abstract>
<para
>&kdesrc-build; is a script which builds and installs &kde; software directly from the &kde; project's source code repositories.</para>
</abstract>

<keywordset>
<keyword
>KDE</keyword>
<keyword
>kdesdk</keyword>
<keyword
>SVN</keyword>
<keyword
>Subversion</keyword>
<keyword
>git</keyword>
<keyword
>gitorious</keyword>
<keyword
>KDE arendus</keyword>
<!-- Older names for the software -->
<keyword
>kdesvn-build</keyword>
<keyword
>kdecvs-build</keyword>
</keywordset>

</bookinfo>

<chapter id="introduction">
<title
>Sissejuhatus</title>

<para
>&kdesrc-build; is a script to help users install <ulink url="http://www.kde.org/"
>&kde;</ulink
> software from its <ulink url="http://subversion.tigris.org/"
>&subversion;</ulink
> and <ulink url="http://gitscm.org/"
>&git;</ulink
> source repositories. </para>

<tip
><para
>This software used to be called kdesvn-build, so you may still see references to kdesvn-build on the Internet or in your installed documentation.</para
></tip>

<para
>This guide is an overview to describe the following aspects of &kdesrc-build; operation: </para>

<itemizedlist>
<listitem
><para
>Tähtsamad <link linkend="features"
>omadused</link
>.</para
></listitem>
<listitem
><para
><link linkend="getting-started"
>Ülevaade</link
> alustamiseks vajalikest sammudest.</para
></listitem>
<listitem
><para
><link linkend="configure-data"
>Seadistustefaili</link
> süntaks ja valikud.</para
></listitem>
<listitem
><para
><link linkend="cmdline"
>Käsureavõtmed</link
>.</para
></listitem>
</itemizedlist>

<para
>Also documented are the steps which you should perform using other tools, (in other words, steps that are not automatically performed by &kdesrc-build;). </para>

</chapter>
<chapter id="getting-started">
<title
>Alustamine</title>

<para
>In this chapter, we show how to use the &kdesrc-build; to checkout modules from the &kde; repository and build them. We also provide a basic explanation of the &kde; &subversion; structure and the steps you have to perform before running the script. </para>

<para
>Kõiki peatükis vaadeldavaid teemasid käsitleb veelgi põhjalikumalt artikkel <ulink url="http://techbase.kde.org/Getting_Started/Build/KDE4"
> Building &kde; 4 from Source</ulink
>, mille leiab <ulink url="http://techbase.kde.org/"
>&kde; TechBase'i leheküljelt</ulink
>. Kui kompileerid &kde;-d esimest korda, tasuks seda lugeda kas või põgusalt. Sealt leiab põhjaliku info pakendamistööriistade ja nõuete kohta, levinud kompileerimisprobleemide ja -strateegiate kirjelduse ning juhiseid oma uue &kde; paigalduse kasutamiseks. </para>

<sect1 id="before-building">
<title
>Süsteemi ettevalmistamine &kde; ehitamiseks</title>

<sect2 id="before-building-users">
<title
>Uue kasutajakonto loomine</title>

<para
>Soovitatav on kasutada &kde; tarkvara ehitamiseks, paigaldamiseks ja kasutamiseks mõnda muud kasutajakontot, sest vaja läheb vähem õigusi ning samuti ei teki segadusi sinu distributsiooni pakettidega. Kui sul on juba &kde; paketid paigaldatud, oleks kõige mõistlikum luua spetsiaalne kasutaja uue &kde; ehitamiseks ja kasutamiseks. </para>

<tip
><para
>Süsteemse &kde; puutumata jätmine võimaldab vajaduse korral kasutada seda varuvariandina, kui kompileeritud &kde; peaks mis tahes põhjusel osutuma ebastabiilseks. </para
></tip>

<para
>Hiljem võid muidugi soovi korral paigaldada ka administraatori õigustes. Käesolevas käsiraamatus me seda siiski ei puuduta. Kui paigaldad süsteemselt, siis arvatavasti tead juba nagunii, mida ja kuidas teha. Kui mitte, siis tasuks uurida oma distributsiooni dokumentatsiooni või abimaterjale, et süsteem korrektselt ette valmistada ja süsteemne paigaldus õigesti läbi viia. </para>

</sect2>
<sect2 id="before-building-preparation">
<title
>Süsteemi valmisoleku kontrollimine &kde; ehitamiseks lähtekoodist</title>

<para
>Before using the &kdesrc-build; script (or any other building 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://techbase.kde.org/"
>KDE TechBase</ulink
>. </para>

<para
>Loetleme siin mõningad vajalikud asjad:</para>
<itemizedlist>

<listitem
><para
>Vajalik on &cmake;. Nõutav versioon sõltub sellest, millise &kde; 4 versioonis ehitamise ette võtad, vaata täpsemaid asjaolusid TechBase'ist.</para
></listitem>

<listitem
><para
>Samuti on vajalik &subversion;i klientprogramm, mis toetab turvalist HTTP-d (https). Vajaliku toetuse tagamiseks anna käsk <userinput
><command
>svn <option
>--version</option
></command
></userinput
> ja uuri tulemust. Kui väljund teatab, et suudab käsitleda https skeemi (kirjutamisõigusega ligipääsuks svn.kde.org-is) või svn skeemi (kirjutuskaitstud ligipääsuks anonsvn.kde.org-is), siis on asi korras.</para
></listitem>

<listitem
><para
>Kui ehitad &Qt; või mis tahes &kde; mooduleid, mis leiduvad <ulink url="http://gitorious.org/"
>Gitoriouses</ulink
>, siis on vajalik paigaldada ka <ulink url="http://gitscm.org/"
>Giti lähtekoodi juhtimise haldur</ulink
>.</para
></listitem>

<listitem
><para
>Vajalik on C++ arenduskeskkond. Soovitatav on GCC 3.4 või uuem.</para
></listitem>

</itemizedlist>

<note
><para
>Enamik operatsioonisüsteemi distributsioone pakub võimalust vähese vaevaga paigaldada vajalikud arendustööriistad. Uuri TechBase'i <ulink url="http://techbase.kde.org/Getting_Started/Build/KDE4"
>Getting Started</ulink
> lehekülje sektsiooni <quote
>Required Packages from your Distribution</quote
>, kust peaks selguma, kas sellised juhised on juba olemas.</para
></note>

<para
>One exception to the required libraries is the &Qt; library. &kdesrc-build; will normally install a copy of &Qt; whether you have it installed or not, so it is not necessary for you to have it. If you do not want to use the &Qt; copy, you need to do these things:</para>

<itemizedlist>
<listitem>
  <para
>Eemalda moodul qt-copy oma <link linkend="configure-data"
>seadistustefailist</link
>, sest seda ei lähe sul ju sel juhul vaja ning selle olemasolu seal pikendab lihtsalt ehitamisaega.</para>
</listitem>

<listitem>
  <para
>Muuda <link linkend="configure-data"
>seadistustefailis</link
> sätet <link linkend="conf-qtdir"
>qtdir</link
>, nii et see osutaks sinu süsteemi &Qt; peale. Enamasti on selleks keskkonnamuutuja $<envar
>QTDIR</envar
> määratlus.</para>
</listitem>

<listitem>
  <para
>Kui sul pole veel &Qt; paigaldatud, paigalda see, kaasa arvatud kõik asjakohased -dev- või -devel-paketid. Vajalik on vähemalt &Qt; 4.6, kui ehitad &kde; 4.</para>
</listitem>
</itemizedlist>

<para
>Osa neist tarkvarapakettidest on jagatud teekide, programmide või utiliitide ja arenduspakettideks. Sul läheb vaja vähemalt programmi- või teegi- ja arenduspaketti. Kahtluse korral paigalda kõik. Vajalikud teegid sõltuvad moodulitest, mida kavatsed ehitada, sest igal moodulil on oma nõuded. Täpsemalt kõneleb paigaldamiseks vajalikest tööriistadest ja võtetest ning nõutud tarkvarast <ulink url="http://techbase.kde.org/Getting_Started/Build/KDE4#Required_packages_from_your_distribution"
>&kde; TechBase</ulink
>. </para>

</sect2>

<sect2 id="before-building-prepare-script">
<title
>Setup &kdesrc-build;</title>

<sect3 id="get-kdesrc-build">
<title
>Install &kdesrc-build;</title>
<para
>You probably already have a version of the &kdesrc-build; script installed in your system. However, if you do not, you can download it from <ulink url="http://kdesrc-build.kde.org/"
>&kdesrc-build; home page</ulink
>, or you can find it from its home in the &kde; source repository.</para>

<note
><para
>&kdesrc-build; is included with the kdesdk module, and the module is often installed by distributions already. If you have downloaded &kdesrc-build; ensure that you are using the version you downloaded. You can use the --version option to be sure you are running the version you think you are.</para
></note>

<orderedlist>
<listitem
><para
>To download &kdesrc-build; from its home page, simply go to the <ulink url="http://kdesrc-build.kde.org/"
>&kdesrc-build; home page</ulink
> and download the latest appropriate release. The release is packaged as a compressed tarball archive, which you can extract using &ark; or <command
>tar</command
>. The contents of the archive include the actual &kdesrc-build; script, and a sample configuration file (<filename
>kdesrc-buildrc-sample</filename
>).</para
></listitem>

<listitem
><para
>Or, you can obtain &kdesrc-build; from its source repository, located at: <ulink url="http://websvn.kde.org/trunk/KDE/kdesdk/scripts/"
>http://websvn.kde.org/trunk/KDE/kdesdk/scripts/</ulink
>. This is the &kde; Software Development Kit scripting directory, which is the home of &kdesrc-build;. You can click on the <filename
>kdesrc-build</filename
> entry which will bring you to a page where you can download the latest revision. Do so, and save it to a convenient spot on your hard disk. Do the same for <filename
>kdesrc-buildrc-sample</filename
> if you need to.</para
></listitem>
</orderedlist>

<para
>No matter which technique you use, you need to make sure that the <filename
>kdesrc-build</filename
> file is executable. For convenience you should make sure it is in a directory contained in the <envar
>PATH</envar
> environment variable, otherwise you may get messages saying that the command was not found, or you may run a previously-installed version by mistake.</para>
</sect3>

<sect3 id="setup-rcfile">
<title
>Seadistustefaili häälestamine</title>

<para
>Although &kdesrc-build; does not require you to create a <link linkend="configure-data"
>configuration file</link
>, it makes the work flow much easier. Using a <link linkend="configure-data"
>configuration file</link
>, you can control which modules are installed, or remove modules you do not want to install. &kdesrc-build; by default installs a useful &kde; installation using very generic installation flags, which may be different from your needs. So it is best to use a <link linkend="configure-data"
>configuration file</link
>. </para>

<para
>The <link linkend="configure-data"
>configuration file</link
> should be called <filename
>.kdesrc-buildrc</filename
>. This file should be installed on the home folder (<filename class="directory"
>~/</filename
>), and contain all configuration data required for the script to run, like configuration options, compiling options, location of the sources, the destination of the installation (prefix), the modules that should be built, &etc;. The default configuration data is provided by the <filename
>kdesrc-buildrc-sample</filename
> file, which you can copy over as <filename
>~/.kdesrc-buildrc</filename
> and then edit. </para>

<para
>You can find more information about the syntax of the <link linkend="configure-data"
>configuration file</link
> in <xref linkend="configure-data"/> and in <xref linkend="kdesrc-buildrc"/>. </para>

</sect3>
</sect2>
</sect1>

<sect1 id="configure-data">
<title
>Konfiguratsiooniandmete määramine</title>

<para
>To use &kdesrc-build;, you should have a file in your home directory called <filename
>.kdesrc-buildrc</filename
>, which sets the general options and sets the modules you would like to download and build. </para>

<note
><para
>It is possible to use different configuration files for &kdesrc-build;, which is described in <xref linkend="kdesrc-buildrc"/>. If you need to use multiple configurations, please see that section. Here, we will assume the configuration is stored in <filename
>~/.kdesrc-buildrc</filename
>.</para
></note>

<para
>The easiest way to proceed is to use the <filename
>kdesrc-buildrc-sample</filename
> file as a template, changing global options to match your wants, and also change the list of modules you want to build. </para>

<para
>Vaikimisi seadistused peaksid üldiselt sobima &kde; ehitamiseks. Seadistused, mida võib olla mõttekas muuta, on järgmised: <itemizedlist>
<listitem
><para
><link linkend="conf-binpath"
>binpath</link
> võimaldab muuta kataloogide nimekirja, kust käske otsitakse. See võrdub shelli keskkonnamuutujaga <envar
>PATH</envar
>.</para
></listitem>

<listitem
><para
><link linkend="conf-kdedir"
>kdedir</link
> võimaldab muuta sihtkataloogi, kuhu &kde; paigaldatakse. Vaikimisi on selleks <filename class="directory"
>~/kde</filename
>, mis vastab üksikkasutaja paigaldusele.</para
></listitem>

<listitem
><para
><link linkend="conf-qtdir"
>qtdir</link
>, which controls the path to the installation of &Qt; to use. The default is to use a &Qt; compiled by &kdesrc-build;, using the special qt-copy module and the latest available source code. (<filename class="directory"
>~/kdesrc/build/qt-copy</filename
>).</para>

<para
>This also controls where to install qt-copy.</para
></listitem>

<listitem
><para
><link linkend="conf-svn-server"
>svn-server</link
> võimaldab määrata &url;-i, kust lähtekood alla laadida. See on kasulik juhul, kui oled arendaja, kellel on <ulink url="http://techbase.kde.org/Contribute/First_Steps_with_your_KDE_SVN_Account"
>&kde; &subversion;i konto</ulink
>.</para
></listitem>
</itemizedlist>
</para>

<para
>After the global section is a list of modules to build, bracketed by module ... end module lines. Check if the listed modules are in fact the modules you want to build. The default options from the <filename
>kdesrc-buildrc-sample</filename
> file should be enough to get a fairly complete &kde; installation. Save the result as <filename
>.kdesrc-buildrc</filename
> in your home folder. </para>

<para
>If you wish to fine tune your <filename
>.kdesrc-buildrc</filename
>, consult <xref linkend="kdesrc-buildrc"/> for detailed information about all configuration options. </para>

</sect1>

<sect1 id="building-and-troubleshooting">
<title
>Using the &kdesrc-build; script</title>

<para
>Nüüd oled valmis skripti käivitama. Logi terminaliaknas sisse selle kasutaja õigustega, kelle lõid &kde; kompileerimiseks, ning käivita skript: <screen
><prompt
>$</prompt
><command
>kdesrc-build</command
>
</screen>
</para>

<para
>Now, the script should start downloading the sources and compiling them. Depending on how many modules you are downloading, it is possible that &kdesrc-build; will not succeed the first time you compile &kde;. Do not despair! </para>

<para
>&kdesrc-build; logs the output of every command it runs. By default, the log files are kept in <filename class="directory"
>~/kdesvn/log</filename
>. To see what the caused an error for a module in the last &kdesrc-build; command, usually it is sufficient to look at <filename class="directory"
>~/kdesvn/log/latest/<replaceable
>module-name</replaceable
>/error.log</filename
>.</para>

<para
>Selles failis näed viga, mis põhjustas antud mooduli ehitamise nurjumise. Kui failis seisab kirjas, et mõned paketid puuduvad, ürita need paigaldada (kaasa arvatud vastavad -dev paketid), enne kui hakkad seda moodulit uuesti ehitama, ning kasuta pärast puuduvate pakettide paigaldamist võtit <link linkend="cmdline-reconfigure"
>--reconfigure</link
>.</para>

<para
>Kui aga tegemist on ehitamisveaga, on see arvatavasti &kde; lähtekoodi viga, mis usutavasti parandatakse mõne tunni või päeva jooksul. Kui seda ei juhtu, on mõttekas ehitamisveast teada anda postiloendis <email
>kde-devel@kde.org</email
> (eelnevalt on vaja ennast selle liikmeks registreerida).</para>

<para
>Rohkem näiteid asjadest, mis võivad valesti minna, ning nende lahendusi, aga ka mitmeid üldiseid näpunäiteid ja soovitusi &kde; ehitamiseks leiab veebist: <ulink url="http://techbase.kde.org/Getting_Started/Build/KDE4"
>Building &kde; 4 from Source</ulink
>. </para>

<note
><para
>For more information about &kdesrc-build;'s logging features, please see <xref linkend="kdesrc-build-logging"/>.</para
></note>

</sect1>

<sect1 id="environment">
<title
>Värske &kde; töökeskkonna määramine</title>

<para
>Eeldusel, et lõid &kde; ehitamiseks spetsiaalse kasutaja ja sul on juba paigaldatud &kde; versioon, on oma uue &kde; töölepanek mõnevõrra keerulisem, sest vana asemel peab ju käivituma uus &kde;. Selleks tuleb muuta keskkonnamuutujaid. </para>

<sect2 id="changing-profile">
<title
>Käivitusprofiili seadistuste muutmine</title>

<important
><para
>Failis <filename
>.bash_profile</filename
> on kirjas sisselogimisseadistused paljudes &Linux; distributsioonides kasutatava shelli <application
>bash</application
> jaoks. Kui kasutad mõnda muud shelli, võib olla vajalik siinkohal antud näidet veidi kohandada.</para
></important>

<para
>Ava või loo kodukataloogis lemmikredaktoriga fail <filename
>.bash_profile</filename
> ja lisa selle lõppu juhul, kui ehitad moodulit qt-copy (nagu vaikimisi): <programlisting>
QTDIR=(qtdir'i asukoht)   # Such as ~/kdesvn/build/qt-copy by default.
KDEDIR=(kdedir'i asukoht) # Such as ~/kde by default.
KDEDIRS=$KDEDIR
PATH=$KDEDIR/bin:$QTDIR/bin:$PATH
MANPATH=$QTDIR/doc/man:$MANPATH

# Act appropriately if LD_LIBRARY_PATH is not already set.
if [ -z $LD_LIBRARY_PATH ]; then
  LD_LIBRARY_PATH=$KDEDIR/lib:$QTDIR/lib
else
  LD_LIBRARY_PATH=$KDEDIR/lib:$QTDIR/lib:$LD_LIBRARY_PATH
fi

export QTDIR KDEDIRS PATH MANPATH LD_LIBRARY_PATH
</programlisting
> Kui sa ei ehita moodulit qt-copy, vaid kasutad oma süsteemi &Qt;, siis: <programlisting
>KDEDIR=(kdedir'i asukoht)  # Such as ~/kde by default.
KDEDIRS=$KDEDIR
PATH=$KDEDIR/bin:$QTDIR/bin:$PATH

# Act appropriately if LD_LIBRARY_PATH is not already set.
if [ -z $LD_LIBRARY_PATH ]; then
  LD_LIBRARY_PATH=$KDEDIR/lib
else
  LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH
fi

export KDEDIRS PATH LD_LIBRARY_PATH
</programlisting>
</para>

<para
>Kui sa ei tarvita spetsiaalset kasutajat, määra oma failis <filename
>.bash_profile</filename
> uuele keskkonnale teistsugune $<envar
>KDEHOME</envar
>: <programlisting
>export KDEHOME="${HOME}/.kde-svn"

# Create it if needed
[ ! -e ~/.kde-svn ] &amp;&amp; mkdir ~/.kde-svn
</programlisting>
</para>

<note>
<para
>Kui hiljem peaks K-menüü tühi olema või hoopis liiga täis, võib olla vajalik failis <filename
>.bash_profile</filename
> kindlaks määrata ka <acronym
>XDG</acronym
> keskkonnamuutuja: <programlisting
>XDG_CONFIG_DIRS="/etc/xdg"
XDG_DATA_DIRS="${KDEDIR}/share:/usr/share"
export XDG_CONFIG_DIRS XDG_DATA_DIRS
</programlisting>

</para>
</note>

</sect2>
<sect2 id="starting-kde">
<title
>&kde; käivitamine</title>

<para
>Kui keskkonnamuutujad on üle vaadatud, et kasutataks õiget &kde;-d, tuleb kontrollida, et ka skript <command
>startkde</command
> oleks õige. </para>

<para
>Ava kodukataloogis tekstifail <filename
>.xinitrc</filename
> või loo see vajaduse korral. Lisa rida: <programlisting
><command
>exec</command
> <option
>${KDEDIR}/bin/startkde</option
>
</programlisting>
</para>

<important
><para
>Mõne distributsiooni korral võib olla vajalik sama samm ette võtta samuti kodukataloogis paikneva failiga <filename
>.xsession</filename
>. See on eriti vajalik siis, kui kasutusel on graafiline sisselogimishaldur, näiteks &kdm;, <application
>gdm</application
> või <application
>xdm</application
>.</para>
</important>

<para
>Nüüd käivita oma uus &kde;: virtuaalsete terminalide toetusega &BSD; ja &Linux; süsteemides kasutatakse klahvikombinatsioone <keycombo action="simul"
>&Ctrl;&Alt;<keycap
>F1</keycap
></keycombo
> ... <keycombo action="simul"
>&Ctrl;&Alt;<keycap
>F12</keycap
></keycombo
> lülitumiseks vastavalt virtuaalsele konsoolile 1 kuni 12. See võimaldab korraga panna tööle enam kui ühe töökeskkonna. Esimesed kuus on tekstiterminalid, viimased kuus graafilised kuvad. </para>

<para
>Kui sind ootab arvuti käivitamisel ees graafiline sisselogimishaldur, võid ometi kasutada uut &kde; keskkonda ka juhul, kui seda ei leidu halduri loendis. Enamik kuvahaldureid, sealhulgas &kdm;, pakuvad <quote
>kohandatud seansi</quote
> võimalust. Sel juhul laaditakse seansi seadistused sinu kodukataloogis asuvast failist <filename
>.xsession</filename
>. Kui oled seda juba muutnud, nagu eespool kirjeldatud, võimaldabki see sul laadida oma uue &kde; paigalduse. </para>

<para
>Kui see miskipärast siiski ei õnnestu, võib proovida veel üht asja, mis enamasti peaks aitama: vajuta <keycombo action="simul"
>&Ctrl;&Alt;<keycap
>F2</keycap
></keycombo
>, mis avab tekstiterminali. Logi sisse vajaliku kasutaja õigustes ja kirjuta: </para>

<screen
><command
>startx</command
> <option
>--</option
> <option
>:1</option
>
</screen>

<tip>
<para
>Lähtekoodist paigaldatud &kde; ja sinu vana &kde; võivad töötada ka üheaegselt! Logi sisse tavalise kasutajana ning käivita oma stabiilne &kde; töölaud. Vajuta <keycombo action="simul"
>&Ctrl;&Alt;<keycap
>F2</keycap
></keycombo
> (või <keycap
>F1</keycap
>, <keycap
>F3</keycap
> jne.), mis avab tekstiterminali. Logi sisse &kde;&subversion;i kasutajana ja kirjuta:</para>

<screen
><command
>startx</command
> <option
>--</option
> <option
>:1</option
>
</screen>

<para
>You can go back to the &kde; desktop of your regular user by pressing the shortcut key for the already running desktop. This is normally <keycombo action="simul"
>&Ctrl;&Alt;<keycap
>F7</keycap
></keycombo
>, you may need to use <keycap
>F6</keycap
> or <keycap
>F8</keycap
> instead. To return to your &kdesrc-build;-compiled &kde;, you would use the same sequence, except with the next function key. For example, if you needed to enter <keycombo action="simul"
>&Ctrl;&Alt;<keycap
>F7</keycap
></keycombo
> to switch to your regular &kde;, you would need to enter <keycombo action="simul"
>&Ctrl;&Alt;<keycap
>F8</keycap
></keycombo
> to go back to your &kdesrc-build; &kde;.</para>
</tip>

</sect2>
</sect1>

</chapter>

<chapter id="features">
<title
>Skripti omadused</title>

<sect1 id="features-overview">
<title
>Omaduste ülevaade</title>

<para
>&kdesrc-build; features include: </para>

<itemizedlist>

<listitem
><para
><link linkend="changing-verbosity"
>Väljundi teadete tasemete</link
> toetus alates väga vaiksest kuni täieliku silumistasemeni. </para
></listitem>

<listitem
><para
>&kdesrc-build; can, with the assistance of the <ulink url="http://kdesrc-build.kde.org/"
>&kdesrc-build; website</ulink
> and the &kde; FTP server (FTP since &kdesrc-build; 1.4), allow for speedy checkouts of some modules. If the module you are checking out has already been packaged at the website, then &kdesrc-build; will download the snapshot and prepare it for use on your computer. </para>

<para
>See on sinu jaoks palju kiirem ning aitab vähendada koormust kde.org-i anonüümse &subversion;i serverites.</para>
</listitem>

<listitem
><para
>Teine asju kiirendav tegur on mooduli ehitamise alustamine kohe pärast seda, kui mooduli lähtekood on alla laaditud (alates versioonist 1.6). </para
></listitem>

<listitem
><para
>Suurepärane <link linkend="using-qt-copy"
>qt-copy mooduli</link
> toetus, sealhulgas vajaduse korral vigu parandavate ja optimeerivate paikade rakendamine qt-copy moodulile. </para
></listitem>

<listitem
><para
>&kdesrc-build; has <link linkend="kdesrc-build-color"
>colorized output</link
>. </para
></listitem>

<listitem
><para
>&kdesrc-build; does not require a <acronym
>GUI</acronym
> present to operate. So, you can build &kde; without needing an alternate graphical environment. </para
></listitem>

<listitem
><para
>Kõigi moodulite vaikevõtmete määramise (näiteks kompileerimise seadistused või seadistusvõtmed) määramise toetus. Neid võtmeid saab muuta ka iga konkreetse mooduli korral.</para>

<para
>Also, &kdesrc-build; will <link linkend="kdesrc-build-std-flags"
>add standard flags</link
> as appropriate to save you the trouble and possible errors from typing them yourself. </para
></listitem>

<listitem
><para
>&kdesrc-build; can checkout a specific <link linkend="using-branches"
>branch or tag</link
> of a module. You can also ensure that a specific <link linkend="conf-revision"
>revision</link
> is checked out of a module. </para
></listitem>

<listitem
><para
>&kdesrc-build; can automatically switch a source directory to checkout from a different repository, branch, or tag. This happens automatically when you change an option that changes what the repository &url; should be, but you must use the <link linkend="cmdline-src-only"
>--src-only</link
> option to let &kdesrc-build; know that it is acceptable to perform the switch. </para
></listitem>

<listitem
><para
>&kdesrc-build; can <link linkend="partial-builds"
>checkout only portions of a module</link
>, for those situations where you only need one program from a large module. </para
></listitem>

<listitem
><para
>The initial download of some modules can be accelerated by &kdesrc-build;, which will (if available) automatically download a module snapshot from the &kde; mirrors and use that to setup the initial checkout. This saves time and bandwidth for both your system and the &kde; servers. </para
></listitem>

<listitem
><para
>For developers: &kdesrc-build; will <link linkend="ssh-agent-reminder"
>remind you</link
> if you use svn+ssh:// but <application
>ssh-agent</application
> is not running, as this will lead to repeated password requests from &ssh;. </para
></listitem>

<listitem
><para
>Võib saata kasutajale vigade kohta <link linkend="email-reports"
>e-postiga aruandeid</link
>. </para
></listitem>

<listitem
><para
>Võib <link linkend="deleting-build-dir"
>kustutada ehitamiskataloogi</link
> pärast mooduli paigaldamist, et hoida kokku ruumi, ehkki samas pikendab see edaspidi kompileerimisaega. </para
></listitem>

<listitem
><para
>The locations for the directories used by &kdesrc-build; are configurable (even per module). </para
></listitem>

<listitem
><para
>Can use &sudo;, or a different user-specified command to <link linkend="root-installation"
>install modules</link
> so that &kdesrc-build; does not need to be run as the super user. </para
></listitem>

<listitem
><para
>&kdesrc-build; runs <link linkend="build-priority"
>with reduced priority</link
> by default to allow you to still use your computer while &kdesrc-build; is working. </para
></listitem>

<listitem
><para
>&kde; &subversion;i <link linkend="using-branches"
>siltide ja harude</link
> kasutamise toetus. </para
></listitem>

<listitem
><para
>&kdesrc-build; will use a set of techniques to <link linkend="building-successfully"
>try and guarantee</link
> a successful build. </para
></listitem>

<listitem
><para
>Määratud mooduli <link linkend="resuming"
>ehitamise taasalustamise</link
> toetus. Võimalik on isegi konkreetse ehitamise korral <link linkend="ignoring-modules"
>eirata teatavaid mooduleid</link
>. </para
></listitem>

<listitem
><para
>&kdesrc-build; can quickly perform a <link linkend="partial-builds"
>partial build</link
> of a module directly from the command line, when you only need to update part of a module. </para
></listitem>

<listitem
><para
>&kdesrc-build; will show the <link linkend="build-progress"
>progress of your build</link
> when using &cmake;, and will always time the build process so you know after the fact how long it took. </para
></listitem>

<listitem
><para
>Püüab automaatselt ümber ehitada mooduleid, mis kasutavad kasvavat make'i (tõsi, see ei pruugi alati õnnestuda). </para
></listitem>

<listitem
><para
>Pakub omalt poolt välja mõistliku valiku vaikevõtmeid &kde; elementaarse ühekasutajapaigalduse tekitamiseks anonüümse &subversion;i hoidla lähtekoodi põhjal. </para
></listitem>

<listitem
><para
>Võimaldab tildega seadistusvõtmeid laiendada. Nii võib näiteks määrata: <programlisting
>qtdir ~/kdesvn/build/qt-copy</programlisting>
</para
></listitem>

<listitem
><para
>Loob automaatselt ehitamissüsteemi, kus lähtekoodikataloog ja ehitamiskataloog erinevad, et lähtekoodikataloog oleks kindlasti puutumatu. </para
></listitem>

<listitem
><para
>Võimaldab määrata globaalsed võtmed kõigile väljavõetavale moodulile, samuti võtmed igale moodulile eraldi. </para
></listitem>

<listitem
><para
>Since the autotools sometimes get out of sync with changes to the source tree, you can force a rebuild of a module by creating a file called .refresh-me in the build directory of the module in question, or by running &kdesrc-build; with the <option
>--refresh-build</option
> option. </para
></listitem>

<listitem
><para
>Võimaldab määrata mitmesuguseid ehitamise ajal kasutatavaid keskkonnamuutujaid, sealhulgas <envar
>KDEDIR</envar
>, <envar
>QTDIR</envar
>, <envar
>DO_NOT_COMPILE</envar
> ja <envar
>CXXFLAGS</envar
>. </para
></listitem>

<listitem
><para
>Käskude logimine. Logid dateeritakse ja nummerdatakse, nii et iga skripti käivitamise kohta on alati omaette logi. Samuti osutab spetsiaalne link nimega latest alati logikataloogi kõige uuemale logile. </para
></listitem>

<listitem
><para
>Kui ehitad &kde; kasutajale, mitte süsteemsena (viimaseks peab olema administraator), saab lasta skriptil enda eest paigaldamine ära teha. See kood ei ole küll saanud vajalikku tähelepanu ning kasutab ohtralt funktsiooni <function
>system()</function
> väljakutseid, mistõttu hetkel ei ole ilmselt soovitatav seda administraatorina tarvitada. </para
></listitem>

<listitem
><para
>Võimaldab kasutada <link linkend="conf-make-install-prefix"
>make-install-prefix</link
>, et anda käsule <userinput
><command
>make</command
> <option
>install</option
></userinput
> prefiks omaette käsuna, mis on kasulik näiteks &sudo; pruukimisel. </para
></listitem>

<listitem
><para
>Välja võib võtta ainult osa &kde; &subversion;i moodulist. Näiteks võib välja võtta ainult <application
>taglib</application
> moodulist <application
>kdesupport</application
> või ainult <application
>K3B</application
> moodulist <application
>extragear/multimedia</application
>. Skript võtab automaatselt välja <application
>kde-common</application
>, kui seda on ehitamiseks vaja. </para
></listitem>

<listitem
><para
>Võimalik on <quote
>teeselda</quote
> millegi tegemist. Käsureal võtit <option
>--pretend</option
> või <option
>-p</option
> andes pakub skript väga põhjaliku käivitatavate käskude kirjelduse ilma neid tegelikult käivitatamata. </para
></listitem>

</itemizedlist>

</sect1>

<sect1 id="kdesrc-build-logging">
<title
>&kdesrc-build;'s build logging</title>

<sect2 id="logging-overview">
<title
>Logimise ülevaade</title>

<para
>Logging is a &kdesrc-build; feature whereby the output from every command that &kdesrc-build; runs is saved to a file for examination later, if necessary. This is done because it is often necessary to have the output of these programs when there is a build failure, because there are so many reasons why a build can fail in the first place.</para>

<sect3 id="log-directory-layout">
<title
>Logimiskataloogi struktuur</title>

<para
>Logid salvestatakse alati logimiskataloogi. Logimiskataloogi sihtkoha määrab võti <link linkend="conf-log-dir"
>log.dir</link
>, milleks vaikimisi on <filename class="directory"
><symbol
>${source-dir}</symbol
>/log</filename
> (kus <symbol
>${source-dir}</symbol
> on võtme <link linkend="conf-source-dir"
>source-dir</link
> väärtus. Allpool räägitaksegi sellest väärtusest kui <symbol
>${log-dir}</symbol
>).</para>

<para
>Under <symbol
>${log-dir}</symbol
>, is a set of directories, one for every time that &kdesrc-build; was run. Each directory is named with the date, and the run number. For instance, the second time that &kdesrc-build; is run on May 26, 2004, it would create a directory called <filename
>2004-05-26-02</filename
>, where the 2004-05-26 is for the date, and the -02 is the run number.</para>

<para
>For your convenience, &kdesrc-build; will also create a link to the logs for your latest run, called <filename class="directory"
>latest</filename
>. So the logs for the most recent &kdesrc-build; run should always be under <filename class="directory"
><symbol
>${log-dir}</symbol
>/latest</filename
>. </para>

<para
>Now, each directory for a &kdesrc-build; run will itself contain a set of directories, one for every &kde; module that &kdesrc-build; tries to build. Also, a file called <filename
>build-status</filename
> will be contained in the directory, which will allow you to determine which modules built and which failed.</para>

<note
><para
>If a module itself has a submodule (such as extragear/multimedia, playground/utils, or KDE/kdelibs), then there would actually be a matching layout in the log directory. For example, the logs for KDE/kdelibs after the last &kdesrc-build; run would be found in <filename class="directory"
><symbol
>${log-dir}</symbol
>/latest/KDE/kdelibs</filename
>, and not under <filename class="directory"
><symbol
>${log-dir}</symbol
>/latest/kdelibs</filename
>. </para
></note>

<para
>In each module log directory, you will find a set of files for each operation that &kdesrc-build; performs. If &kdesrc-build; updates a module, you may see filenames such as <filename
>svn-co.log</filename
> (for a module checkout) or <filename
>svn-up.log</filename
> (when updating a module that has already been checked out). If the <command
>configure</command
> command was run, then you would expect to see a <filename
>configure.log</filename
> in that directory.</para>

<para
>If an error occurred, you should be able to see an explanation of why in one of the files. To help you determine which file contains the error, &kdesrc-build; will create a link from the file containing the error (such as <filename
>build-1.log</filename
> to a file called <filename
>error.log</filename
>).</para>

<para
>The upshot to all of this is that to see why a module failed to build after your last &kdesrc-build;, the file you should look at first is <filename
><symbol
>${log-dir}</symbol
>/latest/<replaceable
>module-name</replaceable
>/error.log</filename
>. </para>

<tip
><para
>Kui fail <filename
>error.log</filename
> on tühi (eriti pärast paigaldamist), siis vahest vigu ei esinenudki. Mõned &kde; ehitamissüsteemi tööriistad annavad mõnikord ekslikult veast teada ka siis, kui viga ei olnudki.</para>

<para
>Also, some commands will evade &kdesrc-build;'s output redirection and bypass the log file in certain circumstances (normally when performing the first &subversion; checkout), and the error output in that case is not in the log file but is instead at the &konsole; or terminal where you ran &kdesrc-build;.</para>
</tip>

</sect3>
</sect2>
</sect1>

</chapter>

<chapter id="kdesrc-buildrc">
<title
>Configuring &kdesrc-build;</title>

<sect1 id="kdesrc-buildrc-overview">
<title
>Overview of &kdesrc-build; configuration</title>

<para
>To use the script, you must have a file in your home directory called <filename
>.kdesrc-buildrc</filename
>, which describes the modules you would like to download and build. </para>

<para
>See algab globaalsete võtmetega umbes nii: </para>

<programlisting
>global
<replaceable
>võtme-nimi võtme-väärtus</replaceable>
<replaceable
>[...]</replaceable>
end global
</programlisting>

<para
>Sellele järgneb üks või enam moodulisektsiooni, mis näeb välja umbes nii: </para>

<programlisting
>module <replaceable
>mooduli-nimi</replaceable>
<replaceable
>võtme-nimi võtme-väärtus</replaceable>
<replaceable
>[...]</replaceable>
end module
</programlisting>

<para
><replaceable
>mooduli-nimi</replaceable
> peab olema &kde; &subversion;i hoidlas leiduva mooduli nimi (näiteks kdelibs või kdebase). Mõned võtmed tühistavad globaalsed võtmed, mõned täiendavad globaalseid võtmeid, mõningaid globaalseid võtmeid aga ei saagi millegagi tühistada. </para>

<para
>The following is a list of commonly-used options. Click on the option to find out more about it. To see the full list of options, see <xref linkend="conf-options-table"/>. </para>

<itemizedlist>
<listitem
><para
><link linkend="conf-branch"
>branch</link
> teeb väljavõtte harust, mitte aga tüvest (trunk).</para
></listitem>
<listitem
><para
><link linkend="conf-build-dir"
>build-dir</link
> määrab ehitamiskataloogi.</para
></listitem>
<listitem
><para
><link linkend="conf-cmake-options"
>cmake-options</link
> määrab, milliste lippudega moodulit konfigureerida &cmake;'i kasutades.</para
></listitem>
<listitem
><para
><link linkend="conf-configure-flags"
>configure-flags</link
> määrab, milliste lippudega moodulit konfigureerida.</para
></listitem>
<listitem
><para
><link linkend="conf-cxxflags"
>cxxflags</link
> määrab muutuja <envar
>CXXFLAGS</envar
>.</para
></listitem>
<listitem
><para
><link linkend="conf-kdedir"
>kdedir</link
> määrab kataloogi, kuhu &kde; paigaldada.</para
></listitem>
<listitem
><para
><link linkend="conf-kde-languages"
>kde-languages</link
> määrab kataloogi, kuhu alla laadida ja paigaldada tõlkepaketid.</para
></listitem>
<listitem
><para
><link linkend="conf-make-options"
>make-options</link
> edastab võtmed programmile &make;.</para
></listitem>
<listitem
><para
><link linkend="conf-qtdir"
>qtdir</link
> määrab &Qt; asukoha.</para
></listitem>
<listitem
><para
><link linkend="conf-set-env"
>set-env</link
> määrab keskkonnamuutuja.</para
></listitem>
<listitem
><para
><link linkend="conf-source-dir"
>source-dir</link
> muudab asukohta, kuhu laaditakse alla lähtekood.</para
></listitem>
<listitem
><para
><link linkend="conf-svn-server"
>svn-server</link
> muudab serverit, kust lähtekood alla laaditakse.</para
></listitem>
</itemizedlist>

</sect1>
<sect1 id="conf-options-table">
<title
>Saadaolevate seadistamisvalikute tabel</title>

<para
>Here is a table of the various options, containing the following information:</para>

<itemizedlist>

<listitem
><para
>The option name</para
></listitem>

<listitem
><para
>A description of how &kdesrc-build; responds if the option is set in both the global section, and the module section of the <link linkend="configure-data"
>configuration file</link
> while building a module.</para
></listitem>

<listitem
><para
>Special comments on the purpose and usage of the option.</para
></listitem>

</itemizedlist>

<table id="option-table">
<title
>Võtmete tabel</title>
<tgroup cols="3">

<thead>
<row>
<entry
>Võtme nimi</entry>
<entry
>Mooduli ja globaalse võtme suhe</entry>
<entry
>Märkused</entry>
</row>
</thead>

<tbody>

<row>
<entry
>apidox</entry>
<entry
></entry>
<entry
><para
>This option was used to allow for building KDE module API documentation. It was removed in &kdesrc-build; 1.6.3 due to it not being supported in KDE 4. Online API documentation is available from <ulink url="http://api.kde.org/"
>kde.org</ulink
>. In addition it is possible to build KDE 4's API documentation using a script included in the kdesdk module (/scripts directory). See <ulink url="http://techbase.kde.org/Development/Tools/apidox"
>KDE TechBase</ulink
> for more details. It is still possible to manually build API documentation for older modules of course.</para>
</entry>
</row>

<row>
<entry
>apply-qt-patches</entry>
<entry
></entry>
<entry
>This option was removed in kdesrc-build 1.10. To get the same effect, see <xref linkend="using-qt-copy"/> and the <link linkend="conf-repository"
>repository</link
> option.</entry>
</row>

<row id="conf-async">
<entry
>async</entry>
<entry
>Ei ole tühistatav</entry>
<entry
><para
>Selle võtmega saab sisse lülitada asünkroonse režiimi, mille puhul lähtekoodi uuendamine ja ehitamine käib paralleelselt, mitte ei oodata kogu lähtekoodi allalaadimist, enne kui alustada ehitamist. Vaikimisi on asünkroonne režiim sisse lülitatud. Kui sa seda ei soovi, määra võtme väärtuseks <replaceable
>false</replaceable
>.</para>
<para
>Võti on kasutatav alates versioonist 1.6.</para
></entry>
</row>

<row id="conf-binpath">
<entry
>binpath</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Selle võtmega saab ehitamiseks määrata keskkonnamuutuja PATH. Seda ei saa moodulivõtmega tühistada. Vaikimisi on väärtuseks $<envar
>PATH</envar
>, mis määratakse skripti käivitamisel. Keskkonnamuutuja peab koolonitega eraldatult sisaldama sinu arendustööriistade asukohti. Asukohad <filename class="directory"
>$<envar
>KDEDIR</envar
>/bin</filename
> ja <filename class="directory"
>$<envar
>QTDIR</envar
>/bin</filename
> lisatakse automaatselt. Selle võtme juures võib iga asukoha määramisel tarvitada ka tildet (~).</para>
</entry>
</row>

<row id="conf-branch">
<entry
>branch</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Set this option to checkout from a branch of &kde; instead of the default of <replaceable
>trunk</replaceable
>, where &kde; development occurs. For instance, to checkout &kde; 4.5 branch, you would set this option to <replaceable
>4.5</replaceable
>.</para>
<para
>If &kdesrc-build; fails to properly download a branch with this option, you may have to manually specify the &url; to download from using the <link linkend="conf-module-base-path"
>module-base-path</link
> or <link linkend="conf-override-url"
>override-url</link
> options.</para>
<para
>Märkus: see valik toimib ka lähtekoodi moodulitega, mis kasutavad &subversion;i asemel &git;i.</para>
</entry>
</row>

<row id="conf-build-dir">
<entry
>build-dir</entry>
<entry
>Module setting overrides global</entry>
<entry
>Selle võtmega saab muuta ehitamiseks kasutatava lähtekoodikataloogi asukohta. Seda saab määrata kolmel viisil: <orderedlist
> <listitem
><para
>Suhteline &kde; &subversion;i lähtekoodikataloogi suhtes (vaata <link linkend="conf-source-dir"
>võtit source-dir</link
>). See on vaikevalik ja valitakse juhul, kui annad kataloogi nime, mille alguses ei seisa tilde (~) või kaldkriips (/).</para
> <para
>Vaikeväärtus on <filename class="directory"
>build</filename
>.</para
></listitem
> <listitem
><para
>Absoluutne asukoht. Kui määrad asukoha, mille alguses seisab kaldkriips (/), kasutatakse täpselt määratud asukohta. Näide: <filename class="directory"
>/tmp/kde-obj-dir/</filename
>.</para
></listitem
> <listitem
><para
>Suhteline kodukataloogi suhtes. Kui määrad asukoha, mille alguses seisab tilde (~), arvestatakse seda asukohta sinu kodukataloogist lähtudes. Näide: <filename class="directory"
>~/builddir</filename
> määrab ehitamiskataloogiks <filename class="directory"
>/home/user-name/builddir</filename
>.</para
></listitem
> </orderedlist
> Mõnevõrra üllatuslikult saab seda võtit muuta ka igas moodulis eraldi. </entry>
</row>

<row id="conf-build-when-unchanged">
<entry
>build-when-unchanged</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Use this option in order to control whether &kdesrc-build; always tries to build a module that has not had any source code updates.</para>

<para
>By setting <option
>build-when-unchanged</option
> to <replaceable
>true</replaceable
>, &kdesrc-build; always attempts the build phase for a module, even if the module did not have any source code updates. This is the default setting since it is more likely to lead to a correct build.</para>

<para
>By setting <option
>build-when-unchanged</option
> to <replaceable
>false</replaceable
>, &kdesrc-build; will only attempt to run the build phase for a module if the module has a source code update, or in other situations where it is likely that a rebuild is actually required. This can save time, especially if you run &kdesrc-build; daily, or more frequently.</para>

<important
><para
>This feature is provided as an optimization only. Like many other optimizations, there are trade-offs for the correctness of your installation. For instance, changes to the qt-copy or kdelibs modules may cause a rebuild of other modules to be necessary, even if the source code doesn't change at all.</para
></important>
</entry>
</row>

<row id="conf-checkout-only">
<entry
>checkout-only</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Selle võtmega saab määrata &subversion;i lähtekoodi väljavõtmise jupphaaval. Võtme väärtus kujutab endast tühikutega eraldatud väljavõetavate kataloogide nimekirja. Ehkki see võti tühistab globaalse võtme, pane tähele, et selle määramine globaalse võtmena pole just eriti mõttekas. </para>

<para
>Pane tähele, et see seadistus ei avalda mõju &git;i moodulitele &git;i lähtekoodi haldussüsteemi tegevuse tõttu.</para>

<para
>See <xref linkend="checking-out-parts"/> for an example.</para
></entry>
</row>

<row id="conf-cmake-options">
<entry
>cmake-options</entry>
<entry
>Täiendab globaalset võtit (v.a. qt-copy korral)</entry>
<entry
><para
>Selle võtmega saab määrata, millised lipud edastada &cmake;'ile mooduli ehitamissüsteemi loomisel. Kasutamisel globaalse võtmena rakendatakse seda kõigile moodulitele, mida skriptiga ehitatakse. Mooduli võtmena lisatakse see globaalsete võtmete lõppu. See võimaldab määrata globaalses sektsioonis üldised &cmake;'i võtmed.</para>

<para
>See võti ei käi qt-copy kohta (sest see ei kasuta &cmake;'i). Selle asemel tuleks kasutada <link linkend="conf-configure-flags"
>configure'i lippe</link
>.</para>

<para
>Et need võtmed edastatakse otse &cmake;'ile, tuleb need anda nii, nagu olekski nad kirjutatud otse &cmake;'i, näiteks:</para>

<screen
>cmake-options -DCMAKE_BUILD_TYPE=RelWithDebInfo
</screen>

<para
>Since this is a hassle, &kdesrc-build; takes pains to ensure that as long as the rest of the options are set correctly, you should be able to leave this option blank. (In other words, <emphasis
>required</emphasis
> &cmake; parameters are set for you automatically)</para
></entry>
</row>

<row id="conf-colorful-output">
<entry
>colorful-output</entry>
<entry
>Ei ole tühistatav</entry>
<entry
>Set this option to <replaceable
>false</replaceable
> to disable the colorful output of &kdesrc-build;. This option defaults to <replaceable
>true</replaceable
>. Note that &kdesrc-build; will not output the color codes to anything but a terminal (such as xterm, &konsole;, or the normal &Linux; console). </entry>
</row>

<row id="conf-configure-flags">
<entry
>configure-flags</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Selle võtmega saab määrata, millised lipud edastada käsule ./configure mooduli ehitamissüsteemi loomisel. Kasutamisel globaalse võtmena rakendatakse seda kõigile moodulitele, mida skriptiga ehitatakse. <emphasis
>See võti käib ainult qt-copy kohta</emphasis
>.</para>

<para
>KDE 4 moodulite konfigureerimisseadistuste muutmise kohta vaata <link linkend="conf-cmake-options"
>cmake-options</link
>. </para>
</entry>
</row>

<row id="conf-cxxflags">
<entry
>cxxflags</entry>
<entry
>Täiendab globaalset võtit</entry>
<entry
><para
>Selle võtmega saab määrata, milliseid lippe kasutada mooduli ehitamisel. See võti on siin võtme <link linkend="conf-configure-flags"
>configure-flags</link
> või <link linkend="conf-cmake-options"
>cmake-options</link
> asemel, sest see määrab ka ehitamise ajal keskkonnamuutuja <envar
>CXXFLAGS</envar
>.</para>

<para
>Pane tähele, et &kde; 4 ja kõigi teiste moodulite korral, mille puhul on kasutusel &cmake;, tuleb mooduli konfigureerimisel võtme CMAKE_BUILD_TYPE väärtuseks määrata "none". Seda saab teha võtmega <link linkend="conf-cmake-options"
>cmake-options</link
>.</para>
</entry>
</row>

<row id="conf-dest-dir">
<entry
>dest-dir</entry>
<entry
>Module setting overrides global</entry>
<entry
>Selle võtmega saab muuta moodulile kettal antavat nime. Kui moodul on näiteks extragear/network, võib sellele käesoleva võtmega anda nimeks extragear-network. Pane tähele, et kuigi see muudab mooduli nime kettal, ei ole sugugi hea mõte kasutada nimes katalooge või kataloogide eraldajaid, sest see häiriks võtmete <link linkend="conf-build-dir"
>build-dir</link
> või <link linkend="conf-source-dir"
>source-dir</link
> kasutamist. </entry>
</row>

<row id="conf-disable-agent-check">
<entry
>disable-agent-check</entry>
<entry
>Ei ole tühistatav</entry>
<entry
>Normally if you are using &ssh; to download the &subversion; sources (such as if you are using the svn+ssh protocol), &kdesrc-build; will try and make sure that if you are using ssh-agent, it is actually managing some &ssh; identities. This is to try and prevent &ssh; from asking for your pass phrase for every module. You can disable this check by setting <option
>disable-agent-check</option
> to <replaceable
>true</replaceable
>. </entry>
</row>

<row id="conf-do-not-compile">
<entry
>do-not-compile</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Selle võtmega saab määrata kindlad kataloogid, mida mooduli korral ei ehitata. Ehitamata jäävad kataloogid tuleb eraldada tühikuga.</para>

<para
>Pane tähele, et programmide lähtekood laaditakse sellele vaatamata alla. Määramaks, milliseid katalooge alla laaditakse, kasuta võtit <link linkend="conf-checkout-only"
>checkout-only</link
>.</para>

<para
>Kui näiteks soovid jätta kdemultimedia moodulis kompileerimata rakendused &juk; ja &kscd;, lisagi kdemultimedia seadistustele "do-not-compile juk kscd".</para>

<para
>See <xref linkend="not-compiling"/> for an example.</para>
</entry>
</row>

<row id="conf-email-address">
<entry
>email-address</entry>
<entry
>Ei ole tühistatav</entry>
<entry>
<para
>Set this option to the e-mail address &kdesrc-build; should send from should it ever need to send e-mail. You do not need to worry about this if you do not use any feature which send e-mail. (They are all disabled by default). </para>

<para
>Praegu vajab seda võtit ainult võti <link linkend="conf-email-on-compile-error"
>email-on-compile-error</link
>.</para>
</entry>
</row>

<row id="conf-email-on-compile-error">
<entry
>email-on-compile-error</entry>
<entry
>Ei ole tühistatav</entry>
<entry>
<para
>You can set this option to the email address to send a report to when a module fails to build. &kdesrc-build; will wait until all the modules are done and collate all of the results in the report. The report is only sent if a module fails to build. </para>

<para
>Please see the <link linkend="conf-email-address"
>email-address</link
> option to set the address &kdesrc-build; should send from, since the default is usually not what you want. </para>
</entry>
</row>

<row>
<entry
>inst-apps</entry>
<entry
></entry>
<entry
>See valik eemaldati kdesvn-buildi versioonis 1.10 </entry>
</row>

<row id="conf-install-after-build">
<entry
>install-after-build</entry>
<entry
>Module setting overrides global</entry>
<entry
>This option is used to install the package after it successfully builds. This option is enabled by default. If you want to disable this, you need to set this option to <replaceable
>false</replaceable
> in the <link linkend="configure-data"
>configuration file</link
>. You can also use the <link linkend="cmdline-no-install"
><option
>--no-install</option
></link
> command line flag. </entry>
</row>

<row id="conf-kdedir">
<entry
>kdedir</entry>
<entry
>Module setting overrides global</entry>
<entry
>Selle võtmega määratakse kataloog, kuhu &kde; pärast ehitamist paigaldatakse. Vaikimisi on selleks <filename class="directory"
>~/kde</filename
>. Kui määrad siin kataloogi, mille ligipääs nõuab administraatori õigusi, tasuks tutvuda ka võtme <link linkend="conf-make-install-prefix"
>make-install-prefix</link
> kirjeldusega.</entry>
</row>

<row id="conf-kde-languages">
<entry
>kde-languages</entry>
<entry
>Ei ole tühistatav</entry>
<entry
><para
>See võti võimaldab &kde; kõrval alla laadida ja paigaldada lokaliseerimispaketid. See on eriti mõttekas, kui sa ei ela näiteks Ameerika Ühendriikides ja soovid, et &kde; oleks tõlgitud ka sinu emakeelde.</para>

<para
>Võtme kasutamisel tuleb tühikutega eraldatult määrata paigaldatavad keeled. Iga keelega on seotud kindel keelekood, mille leiab näiteks veebilehelt <ulink url="http://i18n.kde.org/teams/"
>http://i18n.kde.org/teams/</ulink
>. </para>

<para
>Valida võib ka ainult ühe keele. Vaikimisi ei laadita alla ühtegi keelt, mis ühtlasi tähendab, et &kde; on Ameerika inglise keeles.</para>

<para
>Näiteks prantsuse keele paigaldamiseks peaks võti välja nägema umbes nii: <userinput
><option
>kde-languages</option
> <replaceable
>fr</replaceable
></userinput
>. Aga ka pärast seda tuleb Süsteemi seadistustes prantsuse keele kasutamine sisse lülitada.</para>
</entry>
</row>

<row id="conf-libpath">
<entry
>libpath</entry>
<entry
>Module setting overrides global</entry>
<entry
>Selle võtmega saab määrata ehitamise ajal kasutatava keskkonnamuutuja <envar
>LD_LIBRARY_PATH</envar
>. Seda ei saa moodulivõtmega tühistada. Vaikimisi on see tühi, kuid asukohad <filename class="directory"
>$<envar
>KDEDIR</envar
>/lib</filename
> ja <filename class="directory"
>$<envar
>QTDIR</envar
>/lib</filename
> lisatakse automaatselt. Võtme juures võib iga asukoha määramisel kasutada tildet (~). </entry>
</row>

<row id="conf-log-dir">
<entry
>log-dir</entry>
<entry
>Module setting overrides global</entry>
<entry
>Selle võtmega saab muuta kataloogi, kus hoitakse skripti tekitatud logifaile. </entry>
</row>

<row id="conf-make-install-prefix">
<entry
>make-install-prefix</entry>
<entry
>Module setting overrides global</entry>
<entry
>Selle võtmega saab tühikutega eraldatult määrata nimekirja, mida tõlgendatakse käsu ja selle võtmetena, mis lisatakse moodulite paigaldamiseks kasutatava käsu <userinput
><command
>make</command
> <option
>install</option
></userinput
> ette. See on kasulik näiteks pakettide paigaldamisel &sudo;'ga, kuid palun ole ettevaatlik, kui tegemist on administraatori õigustega.</entry>
</row>

<row id="conf-make-options">
<entry
>make-options</entry>
<entry
>Module setting overrides global</entry>
<entry
>Selle muutujaga saab edastada käsule <command
>make</command
> käsureavõtmeid. See on kasulik sellistele programmidele nagu <ulink url="http://distcc.samba.org/"
><application
>distcc</application
></ulink
> või süsteemides, kus on enam kui üks protsessorituum. </entry>
</row>

<row id="conf-manual-build">
<entry
>manual-build</entry>
<entry
>Module setting overrides global</entry>
<entry
>Määra võtme väärtuseks <replaceable
>true</replaceable
>, kui soovid, et ehitamisel ei ehitataks antud moodulit. &subversion;ist uuendamisel seda siiski uuendatakse. See on samaväärne käsureavõtmega <link linkend="cmdline-no-build"
><option
>--no-build</option
></link
>. </entry>
</row>

<row id="conf-manual-update">
<entry
>manual-update</entry>
<entry
>Module setting overrides global</entry>
<entry
>Määra võtme väärtuseks <replaceable
>true</replaceable
>, kui soovid, et ehitamisel ei üritataks moodulit uuendada (ja seeläbi ka ehitada ega paigaldada). Kui määrad selle võtme moodulile, siis tähendab see sisuliselt selle kõrvalejätmist ehitamisest. </entry>
</row>

<row id="conf-module-base-path">
<entry
>module-base-path</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Set this option to override &kdesrc-build;'s default directory path to the module in question. This can be used, for example, to pull specific branches or tagged versions of libraries. <ulink url="http://websvn.kde.org/"
>The &kde; Source Viewer</ulink
> is invaluable in helping to pick the right path.</para>

<para
>Note that &kdesrc-build; constructs the final path according to the following template: <filename class="directory"
><varname
>$svn-server</varname
>/home/kde/<varname
>$module-base-path</varname
></filename
>. </para>

<para
>Vaikeväärtus on sõltuvalt mooduli nimest <filename class="directory"
>trunk/<varname
>$module</varname
></filename
> või <filename class="directory"
>trunk/KDE/<varname
>$module</varname
></filename
>.</para>

<tip
><para
>Võimaluse korral kasuta selle asemel võtmeid <link linkend="conf-branch"
>branch</link
> või <link linkend="conf-tag"
>tag</link
>. </para
></tip>
</entry>
</row>

<row id="conf-niceness">
<entry
>niceness</entry>
<entry
>Ei ole tühistatav</entry>
<entry
>Set this option to a number between 20 and 0. The higher the number, the lower a priority &kdesrc-build; will set for itself, i.e. the higher the number, the "nicer" the program is. The default is 10. </entry>
</row>

<row id="conf-no-svn">
<entry
>no-svn</entry>
<entry
>Module setting overrides global</entry>
<entry
>If this option is set to true then &kdesrc-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>
<entry
>no-rebuild-on-fail</entry>
<entry
></entry>
<entry
>See valik eemaldati kdesvn-buildi versioonis 1.10, sest ehitussüsteemi paranduste tõttu ei ole sel käitumisel enam mõtet.</entry>
</row>

<row id="conf-override-url">
<entry
>override-url</entry>
<entry
>Module setting overrides global</entry>
<entry
>If you set this option, &kdesrc-build; will use its value as the &url; to pass to &subversion; <emphasis
>completely unchanged</emphasis
>. You should generally use this if you want to download a specific release but &kdesrc-build; cannot figure out what you mean using <link linkend="conf-branch"
>branch</link
>. </entry>
</row>

<row id="conf-prefix">
<entry
>prefix</entry>
<entry
>Module setting overrides global</entry>
<entry
>This option controls where to install the module (normally the <option
><link linkend="conf-kdedir"
>kdedir</link
></option
> setting is used). Using this option allows you to install a module to a different directory than where the KDE Platform libraries are installed, such as if you were using &kdesrc-build; only to build applications. </entry>
</row>

<row id="conf-purge-old-logs">
<entry
>purge-old-logs</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>See valik määrab, kas vanad logikataloogid automaatselt kustutada või mitte. Vaikeväärtus on <replaceable
>false</replaceable
>.</para>

<para
>Isegi kui sa ei ole määranud seda valikut tõeseks, võid käsitsi kõrvaldada vanad logikataloogid käsuga:</para>

<command
>kdesrc-build --no-src --no-build --purge-old-logs <replaceable
>kdelibs</replaceable
></command>

<para
>Eeltoodud käsus võib kasutada mis tahes mooduli nime, see ei pea olema kdelibs.</para>
</entry>
</row>

<row id="conf-qtdir">
<entry
>qtdir</entry>
<entry
>Module setting overrides global</entry>
<entry
>Selle võtmega saab määrata ehitamisel kasutatava keskkonnamuutuja <envar
>QTDIR</envar
>. Seda ei saa moodulivõtmega tühistada. Kui see pole määratud, kasutatakse vaikimisi asukohta <filename class="directory"
><symbol
>$(source-dir)</symbol
>/build/qt-copy</filename
>, mis kasutab &kde; lähtekoodihoidlas leiduvat qt-copy moodulit. Kodukataloogi tähistamiseks võib kasutada tildet (~). </entry>
</row>

<row id="conf-remove-after-install">
<entry
>remove-after-install</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Kui sul napib kõvakettal ruumi, võib selle võtmega lasta automaatselt kustutada ehitamiskataloogi (või ka korraga nii lähtekoodi- kui ka ehitamiskataloogi) pärast mooduli edukat paigaldamist. </para>
<para
>Võtme võimalikud väärtused on järgmised: <itemizedlist>
<listitem
><para
>none - midagi ei kustutata (vaikimisi).</para
></listitem>
<listitem
><para
>builddir - kustutatakse ehitamiskataloog, aga mitte lähtekoodikataloog.</para
></listitem>
<listitem
><para
>all - kustutatakse nii lähtekoodi- kui ehitamiskataloog.</para
></listitem>
</itemizedlist>
</para>

<para
>Note that using this option can have a significant detrimental impact on both your bandwidth usage (if you use <replaceable
>all</replaceable
>) and the time taken to compile &kde;, since &kdesrc-build; will be unable to perform incremental builds.</para>
</entry>
</row>

<row id="conf-repository">
<entry
>repository</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>See valik ilmus versioonis 1.10 ning seda kasutatakse &git;i hoidla määramiseks, kust laadida alla mooduli lähtekood. Seda valikut vajavad &Qt; (ja seega ka qt-copy) ning mitmed &kde; moodulid, mis tasapisi lähevad üle &git;i kasutamisele.</para
></entry>
</row>

<row id="conf-revision">
<entry
>revision</entry>
<entry
>Module setting overrides global</entry>
<entry
>If this option is set to a value other than 0 (zero), &kdesrc-build; will force the &subversion; update to bring the module to the exact revision given, even if options like <link linkend="conf-branch"
>branch</link
> are in effect. If the module is already at the given revision then it will not be updated further unless this option is changed or removed from the configuration.</entry>
</row>

<row id="conf-run-tests">
<entry
>run-tests</entry>
<entry
>Module setting overrides global</entry>
<entry
>If set to <replaceable
>true</replaceable
>, then the module will be built with support for running its test suite, and the test suite will be executed as part of the build process. &kdesrc-build; will show a simple report of the test results. This is useful for developers or those who want to ensure their system is setup correctly.</entry>
</row>

<row id="conf-set-env">
<entry
>set-env</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Selle võtme juures saab anda tühikuga eraldatult väärtuste nimekirja, mille esimene väärtus on määratav keskkonnamuutuja ja ülejäänud selle muutuja väärtused. Näiteks muutujale <envar
>RONALD</envar
> väärtuse McDonald andmine käib nii:</para>
<screen
><command
>set-env</command
> <envar
>RONALD</envar
> <userinput
>McDonald</userinput
></screen>
<para
>See võti on eriline selle poolest, et seda võib korrata ilma varasemaid set-env määratlusi <link linkend="configure-data"
>konfiguratsioonifaili</link
> samas sektsioonis tühistamata. Sel moel võid moodulis (või ka globaalselt) määrata mitu keskkonnamuutujat.</para>
</entry>
</row>

<row id="conf-source-dir">
<entry
>source-dir</entry>
<entry
>Module setting overrides global</entry>
<entry
>This option is used to set the directory on your computer to store the &kde; &subversion; sources at. If you do not specify this value, the default is <filename class="directory"
>~/kdesrc</filename
>. You may use the tilde (~) to represent the home directory if using this option. </entry>
</row>

<row id="conf-stop-on-failure">
<entry
>stop-on-failure</entry>
<entry
>Module setting overrides global</entry>
<entry
>Määra selle võtme väärtuseks <replaceable
>true</replaceable
>, kui soovid, et skript peataks töö pärast vea tekkimist ehitamisel või paigaldamisel. Vaikimisi on see välja lülitatud. </entry>
</row>

<row id="conf-svn-server">
<entry
>svn-server</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Selle võtmega saab määrata serveri, kust &subversion; välja võetakse. Vaikimisi on see anonüümne &subversion;i hoidla <filename
>svn://anonsvn.kde.org/</filename
>.</para>
<note
><para
>If you are developing for KDE, use the &subversion; repository that was provided to you when you received your developer account, instead of the anonymous repository.</para
></note>
</entry>
</row>

<row id="conf-tag">
<entry
>tag</entry>
<entry
>Module setting overrides global</entry>
<entry
><para
>Selle võtmega saab alla laadida mooduli konkreetse väljalaske.</para>
<para
><emphasis
>Märkus:</emphasis
> on üsna usutav, et <emphasis
>sa ei soovi</emphasis
> seda võtit kasutada. &kde; väljalasked asuvad tar-failidena <ulink url="ftp://ftp.kde.org/"
>&kde; FTP-saidil</ulink
> ning selle <ulink url="http://download.kde.org/download.php"
>peegelsaitidel</ulink
>.</para>
</entry>
</row>

<row>
<entry
>use-cmake</entry>
<entry
></entry>
<entry
>This option was removed in &kdesrc-build; 1.4 as all &kde; 4 modules require &cmake;, and &cmake; use is not permitted on any other modules. </entry>
</row>

<row id="conf-use-idle-io-priority">
<entry
>use-idle-io-priority</entry>
<entry
>Ei ole tühistatav</entry>
<entry
>This option, added in &kdesrc-build; 1.12, will cause a lower priority to be used for disk and other I/O usage, which can significantly improve the responsiveness of the rest of the system at the expense of slightly longer running times for &kdesrc-build;. The default is to be disabled, to enable the lower disk priority set this to <replaceable
>true</replaceable
>. </entry>
</row>

<row id="conf-use-qt-builddir-hack">
<entry
>use-qt-builddir-hack</entry>
<entry
>Module setting overrides global</entry>
<entry
>See võti on eemaldatud &Qt; ehitamissüsteemi paranduste tõttu. </entry>
</row>

<row>
<entry
>use-stable-kde</entry>
<entry
></entry>
<entry
><para
>See valik eemaldati kdesvn-buildi versioonis 1.10, mis piirab toetuse KDE 4-ga. </para>
</entry>
</row>

</tbody>

</tgroup>
</table>

</sect1>
</chapter>

<chapter id="cmdline">
<title
>Käsureavõtmed ja keskkonnamuutujad</title>

<sect1 id="supported-envvars">
<title
>Toetatud keskkonnamuutujad</title>

<para
>&kdesrc-build; does not use environment variables. If you need to set environment variables for the build or install process, please see the <link linkend="conf-set-env"
>set-env</link
> option. </para>

</sect1>

<sect1 id="supported-cmdline-params">
<title
>Toetatud käsureaparameetrid</title>

<para
>Skript tunnistab järgmisi käsureavõtmeid: </para>

<variablelist>

<varlistentry id="cmdline-async">
<term
><parameter
>--async</parameter
></term>
<listitem
><para
>Lülitab sisse <link linkend="conf-async"
>asünkroonse režiim</link
>, mis lubab lähtekoodi uuendada ja mooduleid ehitada ühel ja samal ajal. Vaikimisi on see sisse lülitatud, see vajab määramist ainult siis, kui keelad selle seadistuses. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-help">
<term
><parameter
>--help</parameter
></term>
<listitem
><para
>Näitab lihtsat abiinfot skripti kohta. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-version">
<term
><parameter
>--version</parameter
></term>
<listitem
><para
>Näitab programmi versiooni. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-author">
<term
><parameter
>--author</parameter
></term>
<listitem
><para
>Näitab autori kontaktinfot. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-color">
<term
><parameter
>--color</parameter
></term>
<listitem
><para
>Värvilise väljundi lubamine (vaikimisi interaktiivsete terminalide puhul). </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-nice">
<term
><parameter
>--nice=<replaceable
>väärtus</replaceable
></parameter
></term>
<listitem
><para
>This value adjusts the computer CPU priority requested by &kdesrc-build;, and should be in the range of 0-20. 0 is highest priority (because it is the least <quote
>nice</quote
>), 20 is lowest priority. &kdesrc-build; defaults to 10. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-no-async">
<term
><parameter
>--no-async</parameter
></term>
<listitem
><para
>Disables the <link linkend="conf-async"
>asynchronous mode</link
> of updating. Instead the update will be performed in its entirety before the build starts. This option will slow down the overall process, but if you encounter IPC errors while running &kdesrc-build; try using this option, and submitting a <ulink url="http://bugs.kde.org/"
>bug report</ulink
>. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-no-color">
<term
><parameter
>--no-color</parameter
></term>
<listitem
><para
>Keelab värvilise väljundi. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-pretend">
<term
><parameter
>--pretend</parameter
> (või <parameter
>-p</parameter
>)</term>
<listitem
><para
>&kdesrc-build; will run through the update and build process, but instead of performing any actions to update or build, will instead output what the script would have done (e.g. what commands to run, general steps being taken, etc.).</para>

<para
>Märkus: käivitada võidakse siiski lihtsaid kirjutuskaitstud käske (näiteks failiteabe lugemine), et väljund oleks asjakohasem (näiteks korrektne matkimine, kas lähtekood võetakse välja või seda uuendatakse). </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-quiet">
<term
><parameter
>--quiet</parameter
> (või <parameter
>-q</parameter
>)</term>
<listitem
><para
>Väljund on väheminformatiivsem, näidatakse ainult kõige olulisemaid teateid. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-really-quiet">
<term
><parameter
>--really-quiet</parameter
></term>
<listitem
><para
>Väljund näitab ainult hoiatusi ja veateateid. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-verbose">
<term
><parameter
>--verbose</parameter
> (või <parameter
>-v</parameter
>)</term>
<listitem
><para
>Be very descriptive about what is going on, and what &kdesrc-build; is doing. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-src-only">
<term
><parameter
>--src-only</parameter
> (või <parameter
>--svn-only</parameter
>)</term>
<listitem
><para
>Võetakse ette ainult lähtekoodi uuendamine (<parameter
>svn-only</parameter
> on toetatud ainult ühilduvuse nimel vanemate skriptidega). </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-build-only">
<term
><parameter
>--build-only</parameter
></term>
<listitem
><para
>Võetakse ette ainult ehitamine. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-ignore-modules">
<term
><parameter
>--ignore-modules</parameter
></term>
<listitem
><para
>Uuendamisse/ehitamisse ei kaasata ülejäänud käsureal antud mooduleid (see on abiks, kui soovid ehitada enamiku <link linkend="configure-data"
>seadistustefailis</link
> määratud moodulitest, mõned üksikud aga vahele jätta). </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-no-src">
<term
><parameter
>--no-src</parameter
> (või <parameter
>--no-svn</parameter
>)</term>
<listitem
><para
>Ei looda ühendust &subversion;i serveriga. (<parameter
>--no-svn</parameter
> on kasutusel ainult ühilduvuse nimel skripti vanemate versioonidega). </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-no-build">
<term
><parameter
>--no-build</parameter
></term>
<listitem
><para
>Ehitamine jäetakse vahele. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-no-install">
<term
><parameter
>--no-install</parameter
></term>
<listitem
><para
>Pakette ei paigaldata pärast ehitamist automaatselt. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-no-build-when-unchanged">
<term
><parameter
>--no-build-when-unchanged</parameter
></term>
<term
><parameter
>--force-build</parameter
></term>
<listitem
><para
>This option explicitly disables skipping the build process (an optimization controlled by the <link linkend="conf-build-when-unchanged"
>build-when-unchanged</link
> option). This is useful for making &kdesrc-build; run the build when you have changed something that &kdesrc-build; cannot check.</para>

<para
><parameter
>--force-build</parameter
> performs the exact same function, and is perhaps easier to remember.</para>
</listitem>
</varlistentry>

<varlistentry id="cmdline-debug">
<term
><parameter
>--debug</parameter
></term>
<listitem
><para
>Lülitab sisse silumisrežiimi. Praegu tähendab see seda, et lisaks logimisele logikataloogi saadetakse kogu väljund ka standardväljundisse (STDOUT). Samuti annavad paljud funktsioonid silumisrežiimis märksa enam infot oma tegevuse kohta. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-no-rebuild-on-fail">
<term
><parameter
>--no-rebuild-on-fail</parameter
></term>
<listitem
><para
>Do not try to rebuild modules that have failed building from scratch. &kdesrc-build; will never try to do this to a module that already was tried to be built from scratch. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-refresh-build">
<term
><parameter
>--refresh-build</parameter
></term>
<listitem
><para
>Taasluuakse ehitamissüsteem ja alustatakse algusest peale. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-reconfigure">
<term
><parameter
>--reconfigure</parameter
></term>
<listitem
><para
>Run <command
>cmake</command
> (for &kde; modules) or <command
>configure</command
> (for &Qt;) again, without cleaning the build directory. You should not normally have to specify this, as &kdesrc-build; will detect when you change the relevant options and automatically re-run the build setup. This option is implied if <parameter
><link linkend="cmdline-refresh-build"
>--refresh-build</link
></parameter
> is used. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-resume-from">
<term
><parameter
>--resume-from</parameter
></term>
<listitem
><para
>Selle võtmega taasalustatakse ehitamist alates määratud moodulist, mis ongi käsureal järgmine võti. See eeldab võtit <link linkend="cmdline-no-src"
><parameter
>--no-src</parameter
></link
>. Käsureal ei tohi määrata teisi moodulinimesid. </para>
<para
>See also: <xref linkend="cmdline-resume-after"/> and <xref linkend="resuming-failed"/>. You would prefer to use this command line option if you have fixed the build error and want &kdesrc-build; to complete the build.</para
></listitem>
</varlistentry>

<varlistentry id="cmdline-resume-after">
<term
><parameter
>--resume-after</parameter
></term>
<listitem
><para
>Selle võtmega taasalustatakse ehitamist alates pärast määratud moodulit, mis ongi käsureal järgmine võti. See eeldab võtit <link linkend="cmdline-no-src"
><parameter
>--no-src</parameter
></link
>. Käsureal ei tohi määrata teisi moodulinimesid. </para>
<para
>See also: <xref linkend="cmdline-resume-from"/> and <xref linkend="resuming-failed"/>. You would prefer to use this command line option if you have fixed the build error and have also built and installed the module yourself, and want &kdesrc-build; to start again with the next module.</para
></listitem>
</varlistentry>

<varlistentry id="cmdline-rc-file">
<term
><parameter
>--rc-file</parameter
></term>
<listitem
><para
>This interprets the next command line parameter as the file to read the configuration options from. The default value for this parameter is <filename
>kdesrc-buildrc</filename
> (checked in the current directory) if it is present, or <filename
>~/.kdesrc-buildrc</filename
> otherwise. See also <xref linkend="kdesrc-buildrc"/>. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-run">
<term
><parameter
>--run</parameter
></term>
<listitem
><para
>This option interprets the next item on the command line as a program to run, and &kdesrc-build; will then finish reading the configuration file, update the environment as normal, and then execute the given program.</para>

<para
>This will not work to start a shell with the &kdesrc-build; environment in most cases however, since interactive shells typically reset at least part of the environment variables (such as <envar
>PATH</envar
> and <envar
>KDEDIRS</envar
>) in the startup sequence. </para>

<tip
><para
>If you want to see the environment used by &kdesrc-build;, you can run the <command
>printenv</command
> command:</para>
<informalexample>
<screen
>$ <command
>kdesrc-build</command
> <parameter
>--run</parameter
> <parameter
>printenv</parameter>
KDE_SESSION_VERSION=4
SDL_AUDIODRIVER=alsa
LANGUAGE=
XCURSOR_THEME=Oxygen_Blue
LESS=-R -M --shift 5
QMAIL_CONTROLDIR=/var/qmail/control
... etc.
</screen>
</informalexample
></tip>
</listitem>
</varlistentry>

<varlistentry id="cmdline-prefix">
<term
><parameter
>--prefix=&lt;/kde/asukoht&gt;</parameter
></term>
<listitem
><para
>Võimaldab muuta kataloogi, kuhu &kde; paigaldatakse. See eeldab võtit <link linkend="cmdline-reconfigure"
><parameter
>--reconfigure</parameter
></link
>, kuid siiski võib nõutav olla <link linkend="cmdline-refresh-build"
><parameter
>--refresh-build</parameter
></link
> kasutamine. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-revision">
<term
><parameter
>--revision</parameter
></term>
<listitem
><para
>This option causes &kdesrc-build; to checkout a specific numbered revision for each &subversion; module, overriding any <link linkend="conf-branch"
>branch</link
>, <link linkend="conf-tag"
>tag</link
>, or <link linkend="conf-revision"
>revision</link
> options already set for these modules.</para>

<para
>Seda valikut pole just kõige mõistlikum kasutada ning see on toetatud ainult ühilduvuse nimel vanemate skriptidega. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-build-system-only">
<term
><parameter
>--build-system-only</parameter
></term>
<listitem
><para
>This option causes &kdesrc-build; to abort building a module just before the <command
>make</command
> command would have been run. This is supported for compatibility with older versions only, this effect is not helpful for the current &kde; build system. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-install"
><term
><parameter
>--install</parameter
></term>
<listitem
><para
>Kui see on ainus käsureavõti, üritatakse paigaldada kõik edukalt ehitatud moodulid, mida sisaldab <filename
>log/latest/build-status</filename
>. Kui pärast võtit <option
>--install</option
> esineb veel käsureavõtmeid, tõlgendatakse neid paigaldatavate moodulitena (isegi kui neid ei õnnestunud eelmisel korral edukalt ehitada). </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-purge-old-logs"
><term
><parameter
>--purge-old-logs</parameter
></term>
<listitem
><para
>This option causes &kdesrc-build; to delete unneeded log directories after the build, to save disk space. All log directories that are not needed to satisfy a link from <filename
>log/latest</filename
> will be deleted. This is disabled by default. To enable this option by default, see the <link linkend="conf-purge-old-logs"
>purge-old-logs</link
> option. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-no-snapshots"
><term
><parameter
>--no-snapshots</parameter
></term>
<listitem
><para
>Supplying this option causes &kdesrc-build; to always prefer a &subversion; initial checkout of a module instead of using a &subversion; module snapshot. </para>

<note
><para
>Mooduli hetktõmmised <emphasis
>on</emphasis
> tõelised &subversion;i väljavõtted. Seda valikut ei ole vaja määrata, see on mõeldud kasutamiseks ainult probleemide ilmnemisel.</para
></note>
</listitem>
</varlistentry>

<varlistentry id="cmdline-global-option">
<term
><parameter
>--&lt;võtme-nimi&gt;=</parameter
></term>
<listitem
><para
>Selle võtmega saab kõigi moodulite jaoks tühistada <link linkend="configure-data"
>konfiguratsioonifailis</link
> leiduva võtme. Kui näiteks soovid tühistada võtit <link linkend="conf-log-dir"
>log-dir</link
>, siis see käib nii: <userinput
><parameter
>--log-dir=<filename class="directory"
><replaceable
>/kataloogi/asukoht</replaceable
></filename
></parameter
></userinput
>. </para
></listitem>
</varlistentry>

<varlistentry id="cmdline-module-option">
<term
><parameter
>--&lt;mooduli-nimi&gt;,&lt;võtme-nimi&gt;=</parameter
></term>
<listitem
><para
>Selle võtmega saab konkreetse mooduli jaoks tühistada <link linkend="configure-data"
>konfiguratsioonifailis</link
> leiduva võtme. </para
></listitem>
</varlistentry>

</variablelist>

<para
>Kõiki muid käsureavõtmeid tõlgendatakse uuendatavate ja ehitatavate moodulitena. Palun ära aja ehitamist segamini paigaldamisega. </para>

</sect1>

</chapter>

<chapter id="using-kdesrc-build">
<title
>Using &kdesrc-build;</title>

<sect1 id="using-kdesrc-build-preface">
<title
>Eessõna</title>

<para
>Normally using &kdesrc-build; after you have gone through <xref linkend="getting-started"/> is as easy as doing the following from a terminal prompt:</para>

<screen
><prompt
>&percnt;</prompt
> <command
><userinput
>kdesrc-build</userinput
></command
>
</screen>

<para
>&kdesrc-build; will then download the sources for &kde;, try to configure and build them, and then install them.</para>

<para
>Read on to discover how &kdesrc-build; does this, and what else you can do with this tool.</para>

</sect1>

<sect1 id="basic-features">
<title
>Basic &kdesrc-build; features</title>

<sect2 id="using-qt-copy">
<title
>qt-copy toetus</title>
<para
>&kdesrc-build; supports building the &Qt; toolkit used by &kde; software as a convenience to users. This support is handled by a special module named qt-copy.</para>

<note
><para
>&Qt; arendatakse &kde; tarkvarast eraldi hoidlas asukohaga <ulink url="http://qt.gitorious.org/qt"
>http://qt.gitorious.org/qt</ulink
>.</para
></note>

<para
>&Qt; ehitamiseks tuleb kontrollida, et <link linkend="conf-qtdir"
>qtdir</link
> seadistuses on määratud kataloog, kuhu soovid &Qt; paigaldada, nagu räägib <xref linkend="configure-data"/>.</para>

<para
>You should then ensure that the qt-copy module is added to your <filename
>.kdesrc-buildrc</filename
>, before any other modules in the file. If you are using the sample configuration file, you can simply uncomment the existing qt-copy module entry.</para>

<para
>Nüüd tuleks kontrollida, kas võtmed <link linkend="conf-repository"
>repository</link
> ja <link linkend="conf-branch"
>branch</link
> on korrektselt määratud.</para>

<orderedlist>
<listitem
><para
>Esimene valik on ehitamine nii, et rakendataks ka soovitatavaid veaparandusi ja optimeerimispaiku (seda määrati varem valikuga apply-patches). Neid arendatakse eraldi hoidlas aadressiga <ulink url="http://gitorious.org/+kde-developers/qt/kde-qt"
>http://gitorious.org/+kde-developers/qt/kde-qt</ulink
>. Kui soovid ehitamisel rakendada paiku (enamik &kde; arendajaid seda soovib), siis tuleb valikule repository määrata väärtuseks <userinput
>git://gitorious.org/+kde-developers/qt/kde-qt.git</userinput
></para>
</listitem>

<listitem
><para
>Vastasel juhul määra standardse &Qt; ehitamiseks valiku repository väärtuseks <userinput
>git://gitorious.org/qt/qt.git</userinput
>.</para
></listitem>
</orderedlist>

<para
>Mõlemal juhul tuleb valiku branch väärtuseks määrata <userinput
>master</userinput
> (kui sa just ei soovi ehitada mõnda muud haru).</para>

<note
><para
>In some cases the underlying source control software is unable to work when run from &kdesrc-build;, but will still work fine when run from the command prompt. This bug is still under investigation.</para
></note>

</sect2>

<sect2 id="kdesrc-build-std-flags">
<title
>Standard flags added by &kdesrc-build;</title>
<para
>To save you time, &kdesrc-build; adds some standard paths to your environment for you: </para>

<itemizedlist>
<listitem
><para
>&kde; ja &Qt; teekide asukoht lisatakse automaatselt muutujale <envar
>LD_LIBRARY_PATH</envar
>. See tähendab, et nende kaasamiseks ei ole vaja enam muuta &libpath;'i. </para
></listitem>

<listitem
><para
>&kde; ja &Qt; arendusprogrammide asukoht lisatakse automaatselt muutujale <envar
>PATH</envar
>. See tähendab, et nende kaasamiseks ei ole vaja enam muuta &binpath;'i. </para
></listitem>

<listitem
><para
>&kde; pakutava <application
>pkg-config</application
> asukoht lisatakse automaatselt muutujale <envar
>PKG_CONFIG_PATH</envar
>. See tähendab, et nende lisamiseks ei ole enam vajalik kasutada võtit &set-env;. </para
></listitem>

<listitem
><para
>&kdedir; määratlus edastatakse ehitamise ajal automaatselt keskkonnamuutujale <envar
>KDEDIR</envar
> (see ei puuduta muutujat <envar
>KDEDIRS</envar
>). </para
></listitem>

<listitem
><para
>&qtdir; määratlus edastatakse ehitamise ajal automaatselt keskkonnamuutujale <envar
>QTDIR</envar
>. </para
></listitem>

</itemizedlist>

</sect2>

<sect2 id="build-priority">
<title
>Changing &kdesrc-build;'s build priority</title>
<para
>Tänapäeva operatsioonisüsteemides (sealhulgas &Linux; ja &BSD;) võivad programmid töötada erineva prioriteediga. See võimaldab süsteemil eraldada eri programmidele aega vastavalt nende tähtsusele. </para>

<para
>&kdesrc-build; will normally allocate itself a low priority so that the rest of the programs on your system are unaffected and can run normally. Using this technique, &kdesrc-build; will use extra CPU when it is available. </para>

<para
>&kdesrc-build; will still maintain a high enough priority level so that it runs before routine batch processes and before CPU donation programs such as <ulink url="http://setiathome.ssl.berkeley.edu/"
>Seti@Home</ulink
>. </para>

<para
>To alter &kdesrc-build; so that it uses a higher (or lower) priority level permanently, then you need to adjust the &niceness; setting in the <link linkend="configure-data"
>configuration file</link
>. The &niceness; setting controls how <quote
>nice</quote
> &kdesrc-build; is to other programs. In other words, having a higher &niceness; gives &kdesrc-build; a lower priority. So to give &kdesrc-build; a higher priority, reduce the &niceness; (and vice versa). The &niceness; can go from 0 (not nice at all, highest priority) to 20 (super nice, lowest priority).</para>

<para
>You can also temporarily change the priority for &kdesrc-build; by using the &cmd-nice; <link linkend="cmdline"
>command line option</link
>. The value to the option is used exactly the same as for &niceness;.</para>

<note
><para
>It is possible for some programs run by the super user to have a negative nice value, with a correspondingly even higher priority for such programs. Setting a negative (or even 0) &niceness; for &kdesrc-build; is not a great idea, as it will not help run time significantly, but will make your computer seem very sluggish should you still need to use it. </para
></note>

<informalexample>
<para
>To run &kdesrc-build; with a niceness of 15 (a lower priority than normal):</para>

<screen
><prompt
>&percnt;</prompt
> <userinput
><command
>kdesrc-build</command
> <option
>--nice=<replaceable
>15</replaceable
></option
></userinput
>
</screen>

<para
>Soovi korral võib muuta <link linkend="configure-data"
>seadistustefaili</link
>, et muuta see püsivaks:</para>

<screen
>&niceness; <replaceable
>15</replaceable
>
</screen>
</informalexample>

<tip>
<para
>The <link linkend="conf-niceness"
>niceness</link
> option only affects the usage of the computer's processor(s). One other major affect on computer performance relates to how much data input or output (<acronym
>I/O</acronym
>) a program uses. In order to control how much <acronym
>I/O</acronym
> a program can use, modern &Linux; operating systems support a similar tool called <application
>ionice</application
>. &kdesrc-build; supports <application
>ionice</application
>, (but only to enable or disable it completely) using the <link linkend="conf-use-idle-io-priority"
>use-idle-io-priority</link
> option, since &kdesrc-build; version 1.12. </para>
</tip>

</sect2>

<sect2 id="root-installation">
<title
>Paigaldamine administraatorina</title>
<para
>You may wish to have &kdesrc-build; run the installation with super user privileges. This may be for the unrecommended system-wide installation. This is also useful when using a recommended single user &kde; build, however. This is because some modules (especially kdebase) install programs that will briefly need elevated permissions when run. They are not able to achieve these permission levels unless they are installed with the elevated permissions. </para>

<para
>You could simply run &kdesrc-build; as the super user directly, but this is not recommended, since the program has not been audited for that kind of use. Although it should be safe to run the program in this fashion, it is better to avoid running as the super user when possible.</para>

<para
>To take care of this, &kdesrc-build; provides the &make-install-prefix; option. You can use this option to specify a command to use to perform the installation as another user. The recommended way to use this command is with the &sudo; program, which will run the install command as the super user. </para>

<informalexample>
<para
>Näiteks kõigi moodulite paigaldamiseks &sudo; abil võib talitada nii:</para>

<screen
>global
  &make-install-prefix; <replaceable
>sudo</replaceable>
  # Teised võtmed
end global
</screen>

<para
>&make-install-prefix; kasutamiseks ainult ühe mooduli puhul peaks talitama nii: </para>

<screen
>module <replaceable
>kdemultimedia</replaceable>
  &make-install-prefix; <replaceable
>sudo</replaceable>
end module
</screen>
</informalexample>

</sect2>

<sect2 id="build-progress">
<title
>Mooduli ehitamise edenemise näitamine</title>
<para
>See võimalus on alati olemas ning lülitatakse automaatselt sisse, kui vähegi võimalik. See näitab mooduli ehitamise ajal selle hinnangulist edenemist, andes teada, kui kaua tõenäoliselt veel kulub ehitamise lõpuni. </para>

</sect2>

</sect1>

<sect1 id="advanced-features">
<title
>Muud omadused</title>

<sect2 id="partial-builds">
<title
>Mooduli osaline ehitamine</title>
<para
>It is possible to build only pieces from a single &kde; module. For example, you may want to compile only one program from a module. &kdesrc-build; has features to make this easy. There are several complementing ways to do this. </para>

<sect3 id="checking-out-parts">
<title
>Mooduli üksikute osade väljavõte</title>

<para
>This is perhaps the best way to do this. When it works, it will save you download time and disk space. What happens is that &kdesrc-build; will download only the parts of a module that you specify. This is done using the &checkout-only; option for a module, which will specify a list of directories to download. </para>

<tip
><para
>If you do not already know what to download from a module, it may be a good idea to browse the &subversion; layout for a module first, using <ulink url="http://websvn.kde.org/branches/KDE/4.5/"
>WebSVN</ulink
>. </para
></tip>

<informalexample>
<para
>To only grab &kuser; and <application
>KSystemLog</application
> from kdeadmin, you could use &checkout-only; like this:</para>

<screen
>module <replaceable
>kdeadmin</replaceable>
  &checkout-only; <replaceable
>kuser ksystemlog</replaceable>
end module
</screen>

</informalexample>

<important
><para
>Kataloogid ehitatakse selles järjekorras, nagu nad on parameetritena loetletud. Kui mõni kataloog vajab kompileerimiseks moodulist veel midagi, tuleb kontrollida, et mõlemad oleks määratud &checkout-only; real ja et sõltuvus paikneks enne kataloogi, mis seda vajab.</para>

<para
>Also, sometimes an application may need other directories and it is hard to figure out what they are, which may require some trial and error of constantly adding directories to the option to figure out. This option depends on support from the build system of the module, so it is only useful for modules that are collections of individual applications.</para>
</important>

<para
>One final note to make about this option: If you change the value of this option, you should use <userinput
><command
>kdesrc-build</command
> <option
>&cmd-refresh-build;</option
> <option
><replaceable
>module</replaceable
></option
></userinput
> in order to ensure that the module is reconfigured properly. In addition, &kdesrc-build; will never remove existing files if you take away the number of directories from your &checkout-only; option, or add the option to a module that has already been checked out.</para>

</sect3>

<sect3 id="not-compiling">
<title
>Kataloogide eemaldamine ehitamisest</title>
<para
>Allalaadimise piiramise asemel võib ka kõik alla laadida, kuid lasta ehitamissüsteemil jätta ehitamise ajal teatavad kataloogid välja. See võib olla kasulik näiteks juhul, kui mõne kataloogiga tekib pidevalt vigu ning see ei ole ülejäänud mooduli jaoks iseenesest vajalik. </para>

<para
>Seda saab määrata võtmega &do-not-compile;. See toimib sarnaselt äsja kirjeldatud võtmega &checkout-only; selles mõttes, et kujutab endast lihtsalt loendit kataloogidega, mis tuleb kompileerimisel arvestamata jätta.</para>

<important
><para
>Also like &checkout-only;, this option requires at least that the build system for the module is reconfigured after changing it. This is done using the <userinput
><command
>kdesrc-build</command
> <option
>&cmd-reconfigure;</option
> <option
><replaceable
>module</replaceable
></option
></userinput
> command. </para
></important>

<informalexample>
<para
>To remove the <filename class="directory"
>python</filename
> directory from the kdebindings build process:</para>

<screen
>module <replaceable
>kdebindings</replaceable>
  &do-not-compile; <replaceable
>python</replaceable>
end module
</screen>

</informalexample>

<note
><para
>This function depends on some standard conventions used in most &kde; modules. Therefore it may not work for all programs.</para
></note>

</sect3>

</sect2>

<sect2 id="using-branches">
<title
>Branching and tagging support for &kdesrc-build;</title>

<sect3 id="branches-and-tags">
<title
>Mis on harud ja sildid?</title>

<para
>&subversion; toetab &kde; lähtekoodi ajalo haldamist. &kde; kasutab seda ära harude loomiseks arendamise käigus ning hoidla sildistamiseks teatava ajavahemiku järel uute väljalasete tarbeks. </para>

<para
>Näiteks võivad mõned &kmail;i arendajad töötada omaette harus mõne uue võimaluse kallal, et vältida võimalikke probleeme versioonis, mida kasutab enamik arendajaid. Selles harus käib arendus omaette, sõltumata sellest, kuidas kulgeb arendustegevus põhiharus (/trunk). </para>

<para
>Silt on aga nii-öelda hetkvõte lähtekoodihoidlast teataval ajahetkel. Seda kasutab &kde; haldusmeeskond väljalaskeks sobiva versiooni tähistamiseks, mis samal ajal võimaldab arendajatel jätkata tööd koodi kallal. </para>

<para
>In &subversion;, there is no difference between branches, tags, or trunk within the code. It is only a convention used by the developers. This makes it difficult to properly support branches and tags within &kdesrc-build;. However, there are some things that can be done. </para>

</sect3>

<sect3 id="branch-support">
<title
>Harude ja siltide kasutamine</title>

<para
>Harude ja siltide toetust tagab rida võtmeid, mis ulatuvad konkreetse versiooni väljavõttest kuni kindlate &url;-ideni, kust kogenenumad kasutajad saavad vajalikke asju alla laadida. </para>

<para
>The easiest method is to use the &branch; and &tag; options. You simply use the option along with the name of the desired branch or tag for a module, and &kdesrc-build; will try to determine the appropriate location within the &kde; repository to download from. For most &kde; modules this works very well.</para>

<informalexample>
<para
>To download kdelibs from &kde; 4.5 (which is simply known as the 4.5 branch): </para>

<screen
>module kdelibs
  branch <replaceable
>4.5</replaceable>
  # other options...
end module
</screen>

<para
>Or, to download kdemultimedia as it was released with &kde; 4.5.1:</para>

<screen
>module kdemultimedia
  tag <replaceable
>4.5.1</replaceable>
  # other options...
end module
</screen>

</informalexample>

<tip
><para
>Võib kindlaks määrata ka haru globaalse väärtuse. Kuid sel juhul ei tohi unustada määramast konkreetset haru, kui soovid moodulit, mida ei leidu globaalses harus, või selle uuemat või vanemat versiooni! </para
></tip>
</sect3>

<sect3 id="advanced-branches">
<title
>Muud harudega seotud võtmed</title>

<para
>&kdesrc-build; supports two options for situations where &branch; and &tag; guess the correct path improperly: &module-base-path; and &override-url;. </para>

<itemizedlist>
<listitem
><para
>&module-base-path; is used to help &kdesrc-build; fill in the missing part of a module's path. In the &kde; repository, all of the paths are of the form <filename class="directory"
>svnRoot/module-base-path/<replaceable
>module-name</replaceable
></filename
>. Normally &kdesrc-build; can figure out the appropriate middle part by itself. When it cannot, you can use &module-base-path;, like this: </para>

<informalexample>
<screen
>module kdesupport
    # kdesupport supports various tags to easily organize the required
    # software for a given KDE Platform release.
    module-base-path tags/kdesupport-for-4.5
end module
</screen>

<para
>This would cause &kdesrc-build; to download kdesupport from (in this example), <filename
>svn://anonsvn.kde.org/home/kde/<replaceable
>tags/kdesupport-for-4.5</replaceable
></filename
>. </para>
</informalexample>
<tip
><para
>In previous versions of &kdesrc-build;, the &module-base-path; was handled differently. If you encounter trouble using an old module-base-path definition perhaps you should verify that the actual path is as &kdesrc-build; expects by using the <link linkend="cmdline-pretend"
>--pretend</link
> option. </para
></tip>
</listitem>

<listitem
><para
>The &override-url; option, on the other hand, requires you to specify the exact path to download from. However, this allows you to pull from paths that previous versions of &kdesrc-build; would have no hope of downloading from. Currently, the &module-base-path; option should be sufficient for any Subversion source URL. </para>

<important
><para
>&kdesrc-build; will not touch or correct the value you specify for &override-url; at all, so if you change your &svn-server; setting, you may need to update this as well. </para
></important>

</listitem>
</itemizedlist>

</sect3>

</sect2>

<sect2 id="building-successfully">
<title
>How &kdesrc-build; tries to ensure a successful build</title>

<sect3 id="automatic-rebuilds">
<title
>Automaatne taasehitamine</title>

<para
>&kdesrc-build; used to include features to automatically attempt to rebuild the module after a failure (as sometimes this re-attempt would work, due to bugs in the build system at that time). Thanks to switching to &cmake; the build system no longer suffers from these bugs, and so &kdesrc-build; will not try to build a module more than once. There are situations where &kdesrc-build; will automatically take action though:</para>

<itemizedlist>

<listitem
><para
>If you change <link linkend="conf-configure-flags"
>configure-flags</link
> or <link linkend="conf-cmake-options"
>cmake-options</link
> for a module, then &kdesrc-build; will detect that and automatically re-run configure or cmake for that module.</para
></listitem>

<listitem
><para
>If the buildsystem does not exist (even if &kdesrc-build; did not delete it) then &kdesrc-build; will automatically re-create it. This is useful to allow for performing a full <link linkend="cmdline-refresh-build"
>--refresh-build</link
> for a specific module without having that performed on other modules.</para
></listitem>

</itemizedlist>

</sect3>

<sect3 id="manual-rebuilds">
<title
>Mooduli taasehitamine käsitsi</title>
<para
>If you make a change to a module's option settings, or the module's source code changes in a way &kdesrc-build; does not recognize, you may need to manually rebuild the module.</para>

<para
>You can do this by simply running <userinput
><command
>kdesrc-build</command
> <option
>--refresh-build</option
> <option
><replaceable
>module</replaceable
></option
></userinput
>. </para>

<para
>If you would like to have &kdesrc-build; automatically rebuild the module during the next normal build update instead, you can create a special file. Every module has a build directory. If you create a file called <filename
>.refresh-me</filename
> in the build directory for a module, &kdesrc-build; will rebuild the module next time the build process occurs, even if it would normally perform the faster incremental build.</para>

<tip>
<para
>Vaikimisi on ehitamiskataloogiks <filename class="directory"
>~/kdesvn/build/<replaceable
>moodul</replaceable
>/</filename
>. Kui muudad võtme &build-dir; seadistusi, kasuta aga <filename class="directory"
>~/kdesvn/build</filename
>.</para>
</tip>

<informalexample>
<para
>Mooduli <replaceable
>arts</replaceable
> taasehitamine <filename
>.refresh-me</filename
> abil:</para>
<screen
><prompt
>%</prompt
> <userinput
><command
>touch</command
> <filename class="directory"
>~/kdesvn/build/<replaceable
>arts</replaceable
>.refresh-me</filename
></userinput>
<prompt
>%</prompt
> <userinput
><command
>kdesrc-build</command
></userinput
>
</screen>
</informalexample>
</sect3>

</sect2>

<sect2 id="changing-environment">
<title
>Keskkonnamuutujate seadistuste muutmine</title>
<para
>Normally &kdesrc-build; uses the environment that is present when starting up when running programs to perform updates and builds. This is useful for when you are running &kdesrc-build; from the command line.</para>

<para
>However, you may want to change the setting for environment variables that &kdesrc-build; does not provide an option for directly. (For instance, to setup any required environment variables when running &kdesrc-build; on a timer such as &cron;) This is possible with the &set-env; option.</para>

<para
>Erinevalt enamikust võtmetest saab seda määrata mitu korda ning see tunnustab kaht kirjet, mida eraldab tühik. Esimene neist on määratava keskkonnamuutuja nimi ja teine selle väärtus.</para>

<informalexample>
<para
>Kõigile moodulitele <userinput
><envar
>DISTRO</envar
>=<replaceable
>BSD</replaceable
></userinput
> määramine:</para>
<screen
>global
  set-env <replaceable
>DISTRO</replaceable
> <replaceable
>BSD</replaceable>
end global
</screen>
</informalexample>

</sect2>

<sect2 id="resuming">
<title
>Ehitamise jätkamine</title>

<sect3 id="resuming-failed">
<title
>Nurjunud või katkestatud ehitamise jätkamine</title>

<para
>You can tell &kdesrc-build; to start building from a different module than it normally would. This can be useful when a set of modules failed, or if you canceled a build run in the middle. You can control this using the &cmd-resume-from; option and the &cmd-resume-after; option.</para>

<note
><para
>Ükspuha kumba võtme kasutamisel lähtekoodi ei uuendata.</para
> </note>

<informalexample>
<para
>Ehitamise jätkamine alates moodulist kdebase:</para>

<screen
><prompt
>%</prompt
> <userinput
><command
>kdesrc-build</command
> <option
>--resume-from=<replaceable
>kdebase</replaceable
></option
></userinput
>
</screen>
</informalexample>

<informalexample>
<para
>Ehitamise jätkamine alates pärast moodulit kdebase (juhul kui oled ise käsitsi parandanud probleemi ja paigaldanud mooduli):</para>

<screen
><prompt
>%</prompt
> <userinput
><command
>kdesrc-build</command
> <option
>--resume-after=<replaceable
>kdebase</replaceable
></option
></userinput
>
</screen>
</informalexample>

</sect3>

<sect3 id="ignoring-modules">
<title
>Moodulite eiramine ehitamisel</title>

<para
>Nii nagu võib <link linkend="resuming-failed"
>jätkata ehitamist kindlast moodulist</link
>, võib ka kõike uuendada ja ehitada nagu tavaliselt, kuid eirata teatavaid mooduleid.</para>

<para
>You can do this using the &cmd-ignore-modules; option. This option tells &kdesrc-build; to ignore all the modules on the command line when performing the update and build.</para>

<informalexample>
<para
>extragear/multimedia ja kdereview eiramine:</para>
<screen
><prompt
>%</prompt
> <userinput
><command
>kdesrc-build</command
> <option
>--ignore-modules</option
> <replaceable
>extragear/multimedia kdereview</replaceable
></userinput
>
</screen>
</informalexample>

</sect3>
</sect2>

<sect2 id="changing-env-from-cmd-line">
<title
>Võtmete muutmine käsureal</title>

<sect3 id="changing-global-opts">
<title
>Globaalsete võtmete muutmine</title>
<para
><link linkend="configure-data"
>Seadistustefailist</link
> loetavate võtmete seadistusi saab muuta otse käsurealt. See tühistab seadistustefailis määratu ainult ajutiselt, mõjudes vaid nii kaua, kuni töötab käsk, millega muutus rakendati.</para>

<para
>&kdesrc-build; allows you to change options named like <replaceable
>option-name</replaceable
> by passing an argument on the command line in the form <userinput
><option
>--<replaceable
>option-name</replaceable
>=value</option
></userinput
>. &kdesrc-build; will recognize whether it does not know what the option is, and search for the name in its list of option names. If it does not recognize the name, it will warn you, otherwise it will remember the value you set it to and override any setting from the configuration file.</para>

<informalexample>
<para
>Võtmele &source-dir; testimiseks väärtuse <filename
>/dev/null</filename
> määramine:</para>

<screen
><prompt
>%</prompt
> <userinput
><command
>kdesrc-build</command
> <option
>--pretend</option
> <option
>--<replaceable
>source-dir</replaceable
>=<replaceable
>/dev/null</replaceable
></option
></userinput
>
</screen>

</informalexample>

</sect3>

<sect3 id="changing-module-opts">
<title
>Mooduli võtmete muutmine</title>
<para
>Võtmeid võib muuta ka ainult kindla mooduli puhul. Süntaks on samasugune: --<replaceable
>moodul</replaceable
>,<replaceable
>võtmenimi</replaceable
>=<replaceable
>väärtus</replaceable
>. </para>

<para
>See tühistab igasuguse moodulile määratud samalaadse seadistuse <link linkend="configure-data"
>seadistustefailis</link
> ja rakendub ainult siis, kui võti edastatakse käsureal.</para>

<informalexample>
<para
>Teistsuguse ehitamiskataloogi määramine moodulile kdeedu:</para>

<screen
><prompt
>%</prompt
> <userinput
><command
>kdesrc-build</command
> <option
>--<replaceable
>kdeedu</replaceable
>,<replaceable
>build-dir</replaceable
>=<replaceable
>temp-build</replaceable
></option
></userinput
>
</screen>

</informalexample>

</sect3>

</sect2>

</sect1>

<sect1 id="developer-features">
<title
>Võimalused &kde; arendajatele</title>

<sect2 id="ssh-agent-reminder">
<title
>&ssh; agendi kontrollimine</title>
<para
>&kdesrc-build; can ensure that &kde; developers that use &ssh; to access the &kde; source repository do not accidentally forget to leave the &ssh; Agent tool enabled. This can cause &kdesrc-build; to hang indefinitely waiting for the developer to type in their &ssh; password, so by default &kdesrc-build; will check if the Agent is running before performing source updates. </para>

<note
><para
>Seda tehakse ainult nende &kde; arendajate korral, kes kasutavad &ssh;-d, sest vaikimisi anonüümse väljavõtte jaoks ei ole mingit parooli vaja. &subversion; tuleb toime paroolidega ka &kde; arendajate teise võimaliku protokolli ehk https korral. </para
></note>

<para
>You may wish to disable the &ssh; Agent check, in case of situations where &kdesrc-build; is mis-detecting the presence of an agent. To disable the agent check, set the <option
>disable-agent-check</option
> option to <replaceable
>true</replaceable
>.</para>

<informalexample>
<para
>&ssh; agendi kontrollise keelamine:</para>
<screen
>global
  disable-agent-check true
end global
</screen>
</informalexample>

</sect2>

</sect1>

<sect1 id="other-features">
<title
>Other &kdesrc-build; features</title>

<sect2 id="changing-verbosity">
<title
>Changing the amount of output from &kdesrc-build;</title>
<para
>&kdesrc-build; has several options to control the amount of output the script generates. In any case, errors will always be output.</para>

<itemizedlist>
<listitem
><para
>The <option
>--quiet</option
> option (short form is <option
>-q</option
>) causes &kdesrc-build; to be mostly silent. Only important messages, warnings, or errors will be shown. When available, build progress information is still shown.</para
></listitem>

<listitem
><para
>The <option
>--really-quiet</option
> option (no short form) causes &kdesrc-build; to only display important warnings or errors while it is running.</para
></listitem>

<listitem
><para
>The <option
>--verbose</option
> option (short form is <option
>-v</option
>) causes &kdesrc-build; to be very detailed in its output.</para
></listitem>

<listitem
><para
>The <option
>--debug</option
> option is for debugging purposes only, it causes &kdesrc-build; to act as if <option
>--verbose</option
> was turned on, causes commands to also output to the terminal, and will display debugging information for many functions.</para
></listitem>
</itemizedlist>

</sect2>

<sect2 id="kdesrc-build-color">
<title
>Värviline väljund</title>
<para
>When being run from &konsole; or a different terminal, &kdesrc-build; will normally display with colorized text.</para>

<para
>Selle saab keelata, kui anda käsureal võti <option
>--no-color</option
> või määrata <link linkend="configure-data"
>seadistustefailis</link
> võtme &colorful-output; väärtuseks <userinput
>false</userinput
>. </para>

<informalexample>
<para
>Värvilise väljundi keelamine seadistustefailis:</para>
<screen
>global
  colorful-output false
end global
</screen>
</informalexample>

</sect2>

<sect2 id="email-reports">
<title
>Teatamine ehitamise nurjumisest e-kirjaga</title>
<para
>&kdesrc-build; can send a e-mail report to an e-mail address of your choice when a module fails to build for whatever reason. The way it works is that you choose an e-mail address that &kdesrc-build; will send from, and an e-mail address to notify when there is an error.</para>

<para
>&kdesrc-build; will then, at the end of a complete run, construct an e-mail if there were any modules that failed to build. The e-mail will contain an abbreviated failure log for each module. Only one e-mail is sent for a run, even if 15 modules failed to build. </para>

<para
>This feature is not enabled by default. To enable it, you need to set both the &email-address; and &email-on-compile-error; options. <option
>email-address</option
> controls the address &kdesrc-build; sends from, and <option
>email-on-compile-error</option
> controls where to send the e-mail message to. </para>

<tip>
<para
>&kdesrc-build; uses the Perl-standard Mail::Mailer module to send e-mail. It is included with Perl 5.8, and is installable with Perl 5.6. Mail::Mailer supports <application
>Sendmail</application
> (including <application
>Sendmail</application
>-compatible e-mail clients), native <acronym
>SMTP</acronym
> transport, and <application
>qmail</application
>. </para>
</tip>

<informalexample>
<para
>Ehitamise veast teatava e-kirja saatmine aadressilt jama@kuskil.ee aadressile suva@kuskil.ee:</para>

<screen
>global
  email-address          foo@example.com    # From: address for any kdesrc-build e-mail
  email-on-compile-error bar@example.com    # To: address for build failure e-mail
end global
</screen>
</informalexample>

</sect2>

<sect2 id="deleting-build-dir">
<title
>Ebavajalike kataloogide eemaldamine pärast ehitamist</title>
<para
>Are you short on disk space but still want to run a bleeding-edge &kde; checkout? &kdesrc-build; can help reduce your disk usage when building &kde; from &subversion;.</para>

<note
><para
>Be aware that building &kde; does take a lot of space. There are several major space-using pieces when using &kdesrc-build;:</para
></note>

<orderedlist>
<listitem
><para
>The actual source checkout can take up a fair amount of space. The default modules take up about 1.6 gigabytes of on-disk space. You can reduce this amount by making sure that you are only building as many modules as you actually want. &kdesrc-build; will not delete source code from disk even if you delete the entry from the <link linkend="configure-data"
>configuration file</link
>, so make sure that you go and delete unused source checkouts from the source directory. Note that the source files are downloaded from the Internet, you <emphasis
>should not</emphasis
> delete them if you are actually using them, at least until you are done using &kdesrc-build;.</para>

<para
>Kui sul on juba nagunii paigaldatud &Qt;, ei ole erilist mõtet paigaldada qt-copy moodulit. Sellest loobumine hoiab kokku umbes 200 megabaiti.</para>

<para
>One thing to note is that due to the way &subversion; works: there are actually two files on disk for every file checked-out from the repository. &kdesrc-build; does not have code at this point to try and minimize the source size when the source is not being used. </para>
</listitem>

<listitem>
<para
>&kdesrc-build; will create a separate build directory to build the source code in. Sometimes &kdesrc-build; will have to copy a source directory to create a fake build directory. When this happens, space-saving symlinks are used, so this should not be a hassle on disk space. The build directory will typically be much larger than the source directory for a module. For example, the build directory for kdebase is about 1050 megabytes, whereas kdebase's source is only around 550 megabytes.</para>

<para
>Luckily, the build directory is not required after a module has successfully been built and installed. &kdesrc-build; can automatically remove the build directory after installing a module, see the examples below for more information. Note that taking this step will make it impossible for &kdesrc-build; to perform the time-saving incremental builds.</para>
</listitem>

<listitem
><para
>Lõpuks nõuab oma osa kettaruumist ka &kde; paigaldus. Reeglina on vajalik ruum väiksem kui ehitamiskataloogil, aga siin on raske tuua konkreetseid arve. </para
></listitem>
</orderedlist>

<para
>Kuidas siis vähendada &kde; ruuminõudeid? Üks võimalus on kasutada vastavaid kompileerimislippe, mis võimaldavad kiiruse arvel ruumi kokku hoida. Teine ja enamasti märksa tõhusam viis on eemaldada &kde; ehitamisest silumisteave. </para>

<warning
><para
>Enne silumisteabe eemaldamist peaksid oma sammu siiski väga tõsiselt kaaluma. Uhiuue tarkvara kasutamine sisaldab endas väga suurt tõenäosust, et see jookseb kokku palju kergemini kui stabiilne väljalase. Kui kasutad seda aga ilma silumisteabeta, on väga keeruline koostada veateateid ning sul tuleb tõenäoliselt silumisteave vähemalt krahhi üle elanud rakenduse puhul uuesti sisse lülitada ning rakendus uuesti ehitada, et saaksid aidata arendajatel viga parandada. Niisiis, silumisteabe eemaldamine jääb vaid sinu enda südametunnistusele! </para
></warning>

<informalexample>
<para
>Ehitamiskataloogi eemaldamine pärast mooduli paigaldamist. Lähtekoodikataloog jääb alles ning silumine on sisse lülitatud:</para>

<screen
>global
  configure-flags      --enable-debug
  remove-after-install builddir        # Ehitamiskataloogi eemaldamine pärast paigaldamist
end global
</screen>

<para
>Ehitamiskataloogi eemaldamine pärast ehitamist. Silumine on välja lülitatud ning suurust optimeeritakse.</para>

<screen
>global
  cxxflags             -Os             # Suuruse optimeerimine
  configure-flags      --disable-debug
  remove-after-install builddir        # Ehitamiskataloogi eemaldamine pärast paigaldamist
end global
</screen>
</informalexample>
</sect2>

</sect1>

</chapter>

<chapter id="kde-cmake">
<title
>&cmake; - &kde; 4 ehitamissüsteem</title>

<sect1 id="kde-cmake-intro">
<title
>&cmake;'i sissejuhatus</title>

<para
>2006. aasta märtsis võitis &cmake; mitmeid konkurente ning valiti &kde; 4 ehitamissüsteemiks, asendades muidu &kde; algusest peale kasutatud autotoolsi-põhise süsteemi.</para>

<para
>&cmake;'i sissejuhatuse leiab <ulink url="http://techbase.kde.org/Development/Tutorials/CMake"
>&kde; TechBase'ist</ulink
>. Põhimõtteliselt võib selle kokku võtta nii: selle asemel, et käivitada <userinput
><command
>make</command
> <option
>-f</option
> <filename
>Makefile.cvs</filename
></userinput
>, siis <command
>configure</command
> ja siis &make;, tuleb nüüd käivitada &cmake; ja siis &make;. </para>

<para
>&kdesrc-build; has support for &cmake;. A few features of &kdesrc-build; were really features of the underlying buildsystem, including <link linkend="conf-configure-flags"
>configure-flags</link
> and <link linkend="conf-do-not-compile"
>do-not-compile</link
>. When equivalent features are available, they are provided. For instance, the equivalent to the configure-flags option is <link linkend="conf-cmake-options"
>cmake-options</link
>, and the <link linkend="conf-do-not-compile"
>do-not-compile</link
> option is also supported for &cmake; as of &kdesrc-build; version 1.6.3. </para>

</sect1>
</chapter>

<chapter id="credits-and-licenses">
<title
>Autorid ja litsents</title>

<para
>Tõlge eesti keelde: Marek Laane<email
>bald@smail.ee</email
></para
> 
&underFDL; </chapter>

</book>
