diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2013-01-27 01:06:29 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2013-01-27 01:06:29 -0600 |
| commit | c0b24fe164924298d7e6ae33964b3c65fadbcba3 (patch) | |
| tree | 2ba50375d78b077b266b224e4413150ef3e60a15 /doc/tdevelop | |
| parent | 33d15e862e09fbcbb05e209f832414bd8a01291e (diff) | |
| download | tdevelop-c0b24fe164924298d7e6ae33964b3c65fadbcba3.tar.gz tdevelop-c0b24fe164924298d7e6ae33964b3c65fadbcba3.zip | |
Rename a number of libraries and executables to avoid conflicts with KDE4
Diffstat (limited to 'doc/tdevelop')
| -rw-r--r-- | doc/tdevelop/tdevelop-install.docbook | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/tdevelop/tdevelop-install.docbook b/doc/tdevelop/tdevelop-install.docbook index 5e07b0b6..14f7236b 100644 --- a/doc/tdevelop/tdevelop-install.docbook +++ b/doc/tdevelop/tdevelop-install.docbook @@ -608,7 +608,7 @@ That's all. If you installed &tdevelop; in the default &kde; directory you may n <indexterm zone="compile-and-install-options-dir"> <primary>TDEDIRS</primary></indexterm> <indexterm zone="compile-and-install-options-dir"> - <primary>kbuildsycoca</primary></indexterm> + <primary>tdebuildsycoca</primary></indexterm> <para> By default <command>configure</command> prepares the IDE to be installed in the default &kde; directory. This is necessary because &tdevelop; assumes direct access to some tools and parts which reside there. If want to use your own installation directory, you must tell <command>configure</command> this by the <option>--prefix</option> option: @@ -635,7 +635,7 @@ Call up a shell and have the following commands executed before you start &tdeve </member> <member> <prompt>~> </prompt> - <userinput>kbuildsycoca</userinput> + <userinput>tdebuildsycoca</userinput> </member> <member> (Now start &tdevelop;:) @@ -661,14 +661,14 @@ In a tcsh shell you must set the environment variables using: <userinput>setenv TDEDIRS /usr/local/kde:/opt/trinity</userinput> </member></simplelist></informalexample> <para> -The <command>kbuildsycoca</command> command (<quote>build system control cache</quote>) looks around for libraries and caches their location and version, so that &tdevelop; can find them. The caveat is that it takes noticeable time—and it has to be run any time you call up the shell to start &tdevelop; from a non-default directory. You may want to put the above commands into a shell script to reduce the typing effort. +The <command>tdebuildsycoca</command> command (<quote>build system control cache</quote>) looks around for libraries and caches their location and version, so that &tdevelop; can find them. The caveat is that it takes noticeable time—and it has to be run any time you call up the shell to start &tdevelop; from a non-default directory. You may want to put the above commands into a shell script to reduce the typing effort. </para> <para> -(You could as well put the lines in your <filename>.bashrc</filename> or <filename>.cshrc</filename> file, but this is not advisable as <command>kbuildsycoca</command> will then be run any time you call up the shell.) +(You could as well put the lines in your <filename>.bashrc</filename> or <filename>.cshrc</filename> file, but this is not advisable as <command>tdebuildsycoca</command> will then be run any time you call up the shell.) </para> <note><para> -The <command>kbuildsycoca</command> command does not run from within the root. You must call it from a non-root user. (But is <emphasis>not a very good idea</emphasis> after all to do software development from within the root!) +The <command>tdebuildsycoca</command> command does not run from within the root. You must call it from a non-root user. (But is <emphasis>not a very good idea</emphasis> after all to do software development from within the root!) </para></note> </sect3> <!-- compile-and-install-options-dir --> |