If both commands give an output, the enviroment variables
If both commands give an output, the enviroment variables
are set (the above example are the settings of
are set (the above example are the settings of
@ -636,12 +636,12 @@ Please don't use the <filename>/usr/local</filename> directory as it simply won'
<filename>/usr/lib/qt3</filename> is your
<filename>/usr/lib/qt3</filename> is your
<envar>QTDIR</envar> and
<envar>QTDIR</envar> and
<filename>/usr</filename> is your
<filename>/usr</filename> is your
<envar>KDEDIR</envar>. The installed binaries will go to
<envar>TDEDIR</envar>. The installed binaries will go to
<filename>/usr/bin</filename>. Now we will set the
<filename>/usr/bin</filename>. Now we will set the
enviroment variables with the
enviroment variables with the
<command>export</command> command.
<command>export</command> command.
<screen><prompt>$</prompt> <userinput><command>export</command> QTDIR=<replaceable><replace with your QTDIR></replaceable></userinput></screen>
<screen><prompt>$</prompt> <userinput><command>export</command> QTDIR=<replaceable><replace with your QTDIR></replaceable></userinput></screen>
<screen><prompt>$</prompt> <userinput><command>export</command> KDEDIR=<replaceable><replace with your KDEDIR></replaceable></userinput></screen>
<screen><prompt>$</prompt> <userinput><command>export</command> TDEDIR=<replaceable><replace with your TDEDIR></replaceable></userinput></screen>
</para>
</para>
<note>
<note>
<para>These enviroment variables are only set for the
<para>These enviroment variables are only set for the
@ -654,7 +654,7 @@ Please don't use the <filename>/usr/local</filename> directory as it simply won'
> buttons you can load and save a Key-binding profile. This allows &krusader; to have the &tcmd;, &mc;, foo-commander, or your custom Key-bindings. The only limitation is that global &kde; key-bindings and some &krusader; key-bindings can't be changed yet, as well as some features in foo-commander that we either don't have or don't need. The Key-bindings are stored in <filename
> buttons you can load and save a Key-binding profile. This allows &krusader; to have the &tcmd;, &mc;, foo-commander, or your custom Key-bindings. The only limitation is that global &kde; key-bindings and some &krusader; key-bindings can't be changed yet, as well as some features in foo-commander that we either don't have or don't need. The Key-bindings are stored in <filename
> and re-run &krusader;. If you have compiled &krusader; from sources this is often caused when the &kdeqtdir_lnk; environment variables are not correctly set. The result is that the <filename
> and re-run &krusader;. If you have compiled &krusader; from sources this is often caused when the &kdeqtdir_lnk; environment variables are not correctly set. The result is that the <filename
> If both commands give an output, the enviroment variables are set (the above example are the settings of &mandriva;-&Linux;). In case you just receive empty lines, the variables are not set and you have to set them it manually. If you have no idea what to set the variables to, or if you want to check if the variables are correctly set, ask your distributor or use the <command
> If both commands give an output, the enviroment variables are set (the above example are the settings of &mandriva;-&Linux;). In case you just receive empty lines, the variables are not set and you have to set them it manually. If you have no idea what to set the variables to, or if you want to check if the variables are correctly set, ask your distributor or use the <command
>find</command
>find</command
@ -545,7 +545,7 @@
> and <filename
> and <filename
>/usr</filename
>/usr</filename
> is your <envar
> is your <envar
>KDEDIR</envar
>TDEDIR</envar
>. The installed binaries will go to <filename
>. The installed binaries will go to <filename
>/usr/bin</filename
>/usr/bin</filename
>. Now we will set the enviroment variables with the <command
>. Now we will set the enviroment variables with the <command
@ -553,7 +553,7 @@
> command. <screen
> command. <screen
><prompt>$</prompt> <userinput><command>export</command> QTDIR=<replaceable><replace with your QTDIR></replaceable></userinput></screen>
><prompt>$</prompt> <userinput><command>export</command> QTDIR=<replaceable><replace with your QTDIR></replaceable></userinput></screen>
<screen
<screen
><prompt>$</prompt> <userinput><command>export</command> KDEDIR=<replaceable><replace with your KDEDIR></replaceable></userinput></screen>
><prompt>$</prompt> <userinput><command>export</command> TDEDIR=<replaceable><replace with your TDEDIR></replaceable></userinput></screen>
</para>
</para>
<note
<note
@ -564,7 +564,7 @@
></note>
></note>
<para
<para
>If you can't determine your KDEDIR than <command
>If you can't determine your TDEDIR than <command
>kde-config --prefix</command
>kde-config --prefix</command
> might help you.</para>
> might help you.</para>
@ -642,7 +642,7 @@ If you haven't done so in a while, run ./configure --help
<listitem>
<listitem>
<para
<para
>Your &Linux; distro &krusader; RPM or DEB package will usually install &krusader; in the <filename
>Your &Linux; distro &krusader; RPM or DEB package will usually install &krusader; in the <filename
>KDEDIR/bin</filename
>TDEDIR/bin</filename
> directory. According to the &fhs_url;, any user installed files should go to the <filename
> directory. According to the &fhs_url;, any user installed files should go to the <filename
>/usr/local</filename
>/usr/local</filename
> directory, but in some cases you might want that &krusader; will be installed in an other directory, this behaviour can be determed with the prefix option. If you don't have root access <filename
> directory, but in some cases you might want that &krusader; will be installed in an other directory, this behaviour can be determed with the prefix option. If you don't have root access <filename
@ -673,7 +673,7 @@ kde_includes: /usr/lib
kde_locale: /usr/share/locale
kde_locale: /usr/share/locale
qt_libraries: /usr/lib/qt3/lib
qt_libraries: /usr/lib/qt3/lib
qt_includes: /usr/lib/qt3/include
qt_includes: /usr/lib/qt3/include
KDEDIR: /usr
TDEDIR: /usr
QTDIR: /usr/lib/qt3
QTDIR: /usr/lib/qt3
Install path: /usr/local/bin
Install path: /usr/local/bin
krusader version: 1.51
krusader version: 1.51
@ -737,13 +737,13 @@ Good - your configure finished. Start make now
<para
<para
>If you dit use the an other --prefix= than <filename
>If you dit use the an other --prefix= than <filename
>$KDEDIR or /usr/local</filename
>$TDEDIR or /usr/local</filename
> , then it can't hurt to do an extra check: <screen
> , then it can't hurt to do an extra check: <screen
> buttons you can load and save a Color Scheme profile. This allows that &krusader; can have the &tcmd;, &mc;, foo-commander or your custom colors. The Color Schemes are stored in <filename
> buttons you can load and save a Color Scheme profile. This allows that &krusader; can have the &tcmd;, &mc;, foo-commander or your custom colors. The Color Schemes are stored in <filename
>$KDEDIR/share/apps/krusader</filename
>$TDEDIR/share/apps/krusader</filename
>, the <filename
>, the <filename
>foo.color</filename
>foo.color</filename
> is a binary file that holds the Color Scheme.</para>
> is a binary file that holds the Color Scheme.</para>