| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
|---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|---|
| 4 | <!ENTITY % general-entities SYSTEM "../../general.ent">
|
|---|
| 5 | %general-entities;
|
|---|
| 6 | ]>
|
|---|
| 7 |
|
|---|
| 8 | <sect1 id="kde-pre-install-config">
|
|---|
| 9 | <?dbhtml filename="pre-install-config.html"?>
|
|---|
| 10 |
|
|---|
| 11 | <sect1info>
|
|---|
| 12 | <date>$Date$</date>
|
|---|
| 13 | </sect1info>
|
|---|
| 14 |
|
|---|
| 15 | <title>Trinity/KDE3 Pre-installation Configuration</title>
|
|---|
| 16 |
|
|---|
| 17 | <para>Based on your preference, set TRINITY_PREFIX.</para>
|
|---|
| 18 |
|
|---|
| 19 | <para>One option is to put <application>Trinity/KDE3</application> into the
|
|---|
| 20 | <filename class='directory'>/usr</filename> hierarchy. This creates a
|
|---|
| 21 | simpler setup but is more difficult to try multiple versions of
|
|---|
| 22 | <application>Trinity/KDE3</application>.</para>
|
|---|
| 23 |
|
|---|
| 24 | <screen><userinput>export TRINITY_PREFIX=/usr</userinput></screen>
|
|---|
| 25 |
|
|---|
| 26 | <para>The Trinty developers and BLFS editors recommend installing Trinity in
|
|---|
| 27 | the <filename class='directory'>/opt</filename> directory in order to support
|
|---|
| 28 | using one version while building another.</para>
|
|---|
| 29 |
|
|---|
| 30 | <screen><userinput>export TRINITY_PREFIX=/opt/trinity-&trinity-version;</userinput></screen>
|
|---|
| 31 |
|
|---|
| 32 | <para>Using this option requires updates to the PATH, PKG_CONFIG_PATH, and
|
|---|
| 33 | library search path:</para>
|
|---|
| 34 |
|
|---|
| 35 | <itemizedlist>
|
|---|
| 36 | <listitem>
|
|---|
| 37 | <para>Update PATH</para>
|
|---|
| 38 | <screen><userinput>export PATH=$TRINITY_PREFIX/bin:$PATH</userinput></screen>
|
|---|
| 39 | </listitem>
|
|---|
| 40 |
|
|---|
| 41 | <listitem>
|
|---|
| 42 | <para>Update PKG_CONFIG_PATH</para>
|
|---|
| 43 | <screen><userinput>export PKG_CONFIG_PATH=$TRINITY_PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH</userinput></screen>
|
|---|
| 44 | </listitem>
|
|---|
| 45 |
|
|---|
| 46 | <listitem>
|
|---|
| 47 | <para>Update the library search path</para>
|
|---|
| 48 | <screen><userinput>export LD_LIBRARY_PATH=$TRINITY_PREFIX/lib:$LD_LIBRARY_PATH</userinput></screen>
|
|---|
| 49 | </listitem>
|
|---|
| 50 |
|
|---|
| 51 | </itemizedlist>
|
|---|
| 52 |
|
|---|
| 53 | <para>The instructions for making these changes permanent are in
|
|---|
| 54 | <xref linkend='kde-core-config'/>.</para>
|
|---|
| 55 |
|
|---|
| 56 | <para>There are two other environment variables that need to be set to build
|
|---|
| 57 | <application>Trinity/KDE3</application>. These are needed for all the
|
|---|
| 58 | <userinput>cmake</userinput> based packages:</para>
|
|---|
| 59 |
|
|---|
| 60 | <screen><userinput>export CMAKE_PREFIX_PATH=/opt/qt:$TRINITY_PREFIX &&
|
|---|
| 61 |
|
|---|
| 62 | CMAKE_INCLUDE_PATH=/opt/qt/include:/usr/include/dbus-1.0 &&
|
|---|
| 63 | export CMAKE_INCLUDE_PATH=$CMAKE_INCLUDE_PATH:$TRINITY_PREFIX/include</userinput></screen>
|
|---|
| 64 |
|
|---|
| 65 | <para>You should also consider installing the <xref linkend="desktop-file-utils"/>
|
|---|
| 66 | package. Though not required, this package will allow you to easily use
|
|---|
| 67 | existing <filename>.desktop</filename> files in
|
|---|
| 68 | <filename class='directory'>/usr/share/applications</filename> (and any other
|
|---|
| 69 | locations identified by <envar>XDG_DATA_DIRS</envar>), and automatically add
|
|---|
| 70 | these applications to the menu system.</para>
|
|---|
| 71 |
|
|---|
| 72 | </sect1>
|
|---|
