TDE
/
tdevelop
mirror of https://mirror.git.trinitydesktop.org/gitea/TDE/tdevelop
0
0
Fork 0
Code Issues Releases Wiki Activity

Rename KDEHOME and KDEDIR

Browse Source
pull/1/head
Timothy Pearson 13 years ago
parent 8e7b3d87aa
commit 88838f421c
30 changed files with 97 additions and 97 deletions
Show Stats Download Patch File Download Diff File

24
Doxyfile
Unescape View File

@ -230,18 +230,18 @@ SKIP_FUNCTION_MACROS = YES
#---------------------------------------------------------------------------
# Configuration::additions related to external references
#---------------------------------------------------------------------------
TAGFILES = $(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/dcop/dcop.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/dcop/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/interfaces/interfaces.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/interfaces/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdecore/tdecore.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdecore/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdefx/tdefx.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdefx/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdeui/tdeui.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdeui/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/khtml/khtml.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/khtml/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kio/kio.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kio/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kjs/kjs.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kjs/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kparts/kparts.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kparts/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kmdi/kmdi.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kmdi/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kutils/kutils.tag=$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kutils/html/ \
$(KDEDIR)/share/doc/HTML/en/tdelibs-apidocs/qt/qt.tag=$(QTDIR)/doc/html
TAGFILES = $(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/dcop/dcop.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/dcop/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/interfaces/interfaces.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/interfaces/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdecore/tdecore.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdecore/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdefx/tdefx.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdefx/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdeui/tdeui.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/tdeui/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/khtml/khtml.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/khtml/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kio/kio.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kio/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kjs/kjs.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kjs/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kparts/kparts.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kparts/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kmdi/kmdi.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kmdi/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kutils/kutils.tag=$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/kutils/html/ \
$(TDEDIR)/share/doc/HTML/en/tdelibs-apidocs/qt/qt.tag=$(QTDIR)/doc/html
GENERATE_TAGFILE =
ALLEXTERNALS = NO
EXTERNAL_GROUPS = NO

4
doc/api/HowToAddApplicationTemplates.dox
Unescape View File

@ -27,7 +27,7 @@ applications like kedit as well as plugins for example for tdevelop or noatun.\n
\section templates_1 I. Example: How To Create a Simple KDE Application Template "KHello"
You can find this template in <code>$KDEDIR/share/apps/kdevappwizard/template-khello</code>.
You can find this template in <code>$TDEDIR/share/apps/kdevappwizard/template-khello</code>.
\subsection templates_1_1 I.1. Step 1: Basic Skeleton
@ -64,7 +64,7 @@ wizard will replace:
- \%{YEAR} ........ by the year
.
</pre></code>
All this can be found in <code>$KDEDIR/share/apps/kdevappwizard/template-common/tdevelop.pm</code>.
All this can be found in <code>$TDEDIR/share/apps/kdevappwizard/template-common/tdevelop.pm</code>.
\subsubsection templates_1_2a I.2.1. The Source Files
The files <code>template-khello/app.cpp, template-khello/app.h</code> and

2
doc/api/Mainpage.dox
Unescape View File

@ -71,7 +71,7 @@ To build your local copy of this documentation you have two choices, depending o
- make install-apidox (as root)
.
- If you have an older system then
- setenv KDEDIR=/location_of_your_kde_instalation
- setenv TDEDIR=/location_of_your_kde_instalation
- setenv QTDIR=/location_of_your_qt_instalation
- doxygen Doxyfile
- make install-apidox (as root)

8
doc/kdearch/index.docbook
Unescape View File

@ -1907,7 +1907,7 @@ a complex query language.
<para>
New service types are added by installing a description of them into the
directory <filename>KDEDIR/share/servicetypes</filename>. In an automake
directory <filename>TDEDIR/share/servicetypes</filename>. In an automake
framework, this can be done with this <filename>Makefile.am</filename>
snippet:
</para>
@ -1955,7 +1955,7 @@ Possible types are everything that can be stored in a
<para>
Service definitions are stored in the directory
<filename>KDEDIR/share/services</filename>:
<filename>TDEDIR/share/services</filename>:
</para>
<programlisting>
@ -2246,7 +2246,7 @@ cases the file name extension). For example, a file
extension is stripped off this is not safe, and you actually have to look at
the contents of the file. This is of course slower, in particular for files
that have to be downloaded via HTTP first. The content-based method is based
on the file <filename>KDEDIR/share/mimelnk/magic</filename> and therefore
on the file <filename>TDEDIR/share/mimelnk/magic</filename> and therefore
difficult to extend. But in general, MIME type information can easily be made
available to the system by installing a <literal>.desktop</literal> file, and
it is efficiently and conveniently available through the KDE libraries.
@ -2262,7 +2262,7 @@ it is efficiently and conveniently available through the KDE libraries.
Let us define a type <literal>"application/x-foo"</literal> for our new
<application>foobar</application> program. To this end, you have to write a
file <filename>foo.desktop</filename> and install it into
<filename>KDEDIR/share/mimelnk/application</filename>. (This is the usual
<filename>TDEDIR/share/mimelnk/application</filename>. (This is the usual
location, which may differ between distributions). This can be done by adding
this to the <filename>Makefile.am</filename>:
</para>

28
doc/tdevelop/app-files.docbook
Unescape View File

@ -28,20 +28,20 @@
<title>&tdevelop; Default Configuration</title>
<para>
On installation, &tdevelop; writes some default information files for setup and configuration purposes into subdirectories of the <filename class="directory">$<envar>KDEDIR</envar></filename> installation directory (usually something like <filename class="directory">/opt/kde</filename>, <filename class="directory">/usr/local/kde</filename>, or some other user-defined installation directory, see <link linkend="tdevelop-install">Installing &tdevelop;</link>).
On installation, &tdevelop; writes some default information files for setup and configuration purposes into subdirectories of the <filename class="directory">$<envar>TDEDIR</envar></filename> installation directory (usually something like <filename class="directory">/opt/kde</filename>, <filename class="directory">/usr/local/kde</filename>, or some other user-defined installation directory, see <link linkend="tdevelop-install">Installing &tdevelop;</link>).
</para>
<sect2 id="app-files-default-config">
<title>Default &tdevelop; Configuration</title>
<para>
There is only one &tdevelop; specific default configuration file in the <filename class="directory">$<envar>KDEDIR</envar>/share/config/</filename> directory:
There is only one &tdevelop; specific default configuration file in the <filename class="directory">$<envar>TDEDIR</envar>/share/config/</filename> directory:
</para>
<variablelist>
<varlistentry>
<term><filename>tdeveloprc</filename></term>
<listitem><para>
This file contains the basic settings &tdevelop; needs to start. It will be copied to the user's <filename class="directory">$<envar>KDEHOME</envar>/share/config</filename> directory when &tdevelop; does not find a <filename>tdeveloprc</filename> file there on startup.
This file contains the basic settings &tdevelop; needs to start. It will be copied to the user's <filename class="directory">$<envar>TDEHOME</envar>/share/config</filename> directory when &tdevelop; does not find a <filename>tdeveloprc</filename> file there on startup.
</para></listitem>
</varlistentry>
</variablelist>
@ -52,11 +52,11 @@ There is only one &tdevelop; specific default configuration file in the <filenam
<title>Application Specific Defaults</title>
<para>
Most &tdevelop; features are provided by KParts. These are basically applications specially designed to run in the &tdevelop; framework (see the overview in the <link linkend="plugin-tools">Plugin Tools</link> appendix). Each KPart application has its own set of configuration files whose defaults will be stored in several subdirectories of the <filename class="directory">$<envar>KDEDIR</envar>/share/apps/</filename> installation directory.
Most &tdevelop; features are provided by KParts. These are basically applications specially designed to run in the &tdevelop; framework (see the overview in the <link linkend="plugin-tools">Plugin Tools</link> appendix). Each KPart application has its own set of configuration files whose defaults will be stored in several subdirectories of the <filename class="directory">$<envar>TDEDIR</envar>/share/apps/</filename> installation directory.
</para>
<para>
There are quite a lot of default configuration subdirectories in <filename class="directory">$<envar>KDEDIR</envar>/share/apps/</filename> whose names all start with a <filename>kdev</filename> sequence. Most of them are for &tdevelop; internal use only. They might be deliberately grouped for readability as:
There are quite a lot of default configuration subdirectories in <filename class="directory">$<envar>TDEDIR</envar>/share/apps/</filename> whose names all start with a <filename>kdev</filename> sequence. Most of them are for &tdevelop; internal use only. They might be deliberately grouped for readability as:
<simplelist>
<member><link linkend="app-files-default-apps-stdalone">Stand-alone Applications</link></member>
<member><link linkend="app-files-default-apps-task">Task Specific Parts</link></member>
@ -201,10 +201,10 @@ There are quite a lot of default configuration subdirectories in <filename class
<title>User Oriented Configuration</title>
<para>
All information about user defined settings is kept in two subdirectories of <filename class="directory">$<envar>KDEHOME</envar></filename>, namely:
All information about user defined settings is kept in two subdirectories of <filename class="directory">$<envar>TDEHOME</envar></filename>, namely:
<simplelist>
<member><link linkend="app-files-user-apps">Application Specific Configuration</link> in the <filename class="directory">$<envar>KDEHOME</envar>/share/apps/</filename> directory, and</member>
<member><link linkend="app-files-user-config">Resource Configuration File</link> in the <filename class="directory">$<envar>KDEHOME</envar>/share/config/</filename> directory.</member>
<member><link linkend="app-files-user-apps">Application Specific Configuration</link> in the <filename class="directory">$<envar>TDEHOME</envar>/share/apps/</filename> directory, and</member>
<member><link linkend="app-files-user-config">Resource Configuration File</link> in the <filename class="directory">$<envar>TDEHOME</envar>/share/config/</filename> directory.</member>
</simplelist>
</para>
@ -212,13 +212,13 @@ All information about user defined settings is kept in two subdirectories of <fi
<title>Application Specific Configuration</title>
<para>
Any user changes to the <link linkend="app-files-default">&tdevelop; Default Configuration</link> settings as well as user specific settings which are not kept in any of the <link linkend="app-files-user-config">Resource Configuration Files</link> are found in <filename>kdev...</filename> subdirectories of the <filename class="directory">$<envar>KDEHOME</envar>/share/apps/</filename> directory.
Any user changes to the <link linkend="app-files-default">&tdevelop; Default Configuration</link> settings as well as user specific settings which are not kept in any of the <link linkend="app-files-user-config">Resource Configuration Files</link> are found in <filename>kdev...</filename> subdirectories of the <filename class="directory">$<envar>TDEHOME</envar>/share/apps/</filename> directory.
</para>
<para>
Most of these configuration files are however used by various &tdevelop; plugins in order to provide some specific menu and/or toolbar entries. Thus they are of interest only in case something went really wrong with the user interface.
</para>
<note><para>
In case the contents of these directories mirror those of the Default Configuration settings, &tdevelop; will have copied them from <filename class="directory">$<envar>KDEDIR</envar>/apps/</filename> into the <filename class="directory">$<envar>KDEHOME</envar>/apps/</filename> directory on its initial start. Any subsequent changes will be made to these copies only. The Default Configuration settings remain unchanged in any case.
In case the contents of these directories mirror those of the Default Configuration settings, &tdevelop; will have copied them from <filename class="directory">$<envar>TDEDIR</envar>/apps/</filename> into the <filename class="directory">$<envar>TDEHOME</envar>/apps/</filename> directory on its initial start. Any subsequent changes will be made to these copies only. The Default Configuration settings remain unchanged in any case.
</para></note>
<itemizedlist>
@ -270,7 +270,7 @@ In case the contents of these directories mirror those of the Default Configurat
</listitem>
<listitem>
<para><filename class="directory">kdevdocumentation/</filename> &mdash; contains the actual files used by the <guilabel>Documentation</guilabel> plugin in addition to the <link linkend="app-files-default-kdevdoc"> default configuration files</link>. See there for more detail.</para>
<para>The directories in <filename class="directory">kdevdocumentation/</filename> mainly hold actual bookkeeping information. The actually set up documentation files are kept in <link linkend="app-files-user-config-doc"> <quote><filename>doc...pluginrc</filename></quote> files</link> in the <filename class="directory">$<envar>KDEHOME</envar>/share/config/</filename> directory.</para>
<para>The directories in <filename class="directory">kdevdocumentation/</filename> mainly hold actual bookkeeping information. The actually set up documentation files are kept in <link linkend="app-files-user-config-doc"> <quote><filename>doc...pluginrc</filename></quote> files</link> in the <filename class="directory">$<envar>TDEHOME</envar>/share/config/</filename> directory.</para>
<itemizedlist>
<listitem>
<para><filename class="directory">bookmarks/</filename> &mdash; maintains the entries in the <guilabel>Bookmarks</guilabel> tab of the &tdevelop; <guilabel>Documentation</guilabel> plugin.</para>
@ -345,7 +345,7 @@ In case the contents of these directories mirror those of the Default Configurat
<title>Resource Configuration Files</title>
<para>
There are two groups of &tdevelop; configuration files in the <filename class="directory">$<envar>KDEHOME</envar>/share/config/</filename> directory, distiguished by their surrounding character sequences:
There are two groups of &tdevelop; configuration files in the <filename class="directory">$<envar>TDEHOME</envar>/share/config/</filename> directory, distiguished by their surrounding character sequences:
<simplelist>
<member><quote><filename>doc...pluginrc</filename></quote> denotes <link linkend="app-files-user-config-doc">files used by the documentation plugin.</link></member>
<member><quote><filename>kdev...rc</filename></quote> denotes configuration <link linkend="app-files-user-config-kdev">files used by &tdevelop;</link> itself and its available plugins.</member>
@ -356,7 +356,7 @@ There are two groups of &tdevelop; configuration files in the <filename class="d
<title>Configuration Files Used by &tdevelop;</title>
<listitem>
<para><filename>kdevabbrevrc</filename> &mdash; holds the current state of the <guilabel>Abbreviations</guilabel> configuration provided by the <guilabel>Abbreviation Expansion</guilabel> plugin.</para>
<note><para>This only records whether the abbreviations will be used or not. The actual definitions of new abbreviations will go into the <filename>$<envar>KDEHOME</envar>/share/apps/kdevabbrev/templates/templates</filename> file.</para></note>
<note><para>This only records whether the abbreviations will be used or not. The actual definitions of new abbreviations will go into the <filename>$<envar>TDEHOME</envar>/share/apps/kdevabbrev/templates/templates</filename> file.</para></note>
</listitem>
<listitem>
<para><filename>kdevassistantrc</filename> &mdash; holds some configuration states specific of the stand-alone &tdevelop; Assistant documentation browser.</para>
@ -416,7 +416,7 @@ Both are &XML; coded files. They can be viewed and (cautiously) altered using an
</para>
<note><para>
There can be additional Persistant Code Store files be set up on the <guilabel>Code Completion</guilabel> tab of the <guilabel>C++ Specific</guilabel> project configuration page. Information about these additional <filename>.pcs</filename> is kept globally in the <filename class="directory">$<envar>KDEHOME</envar>/share/apps/kdevcppsupport/pcs/</filename> directory.
There can be additional Persistant Code Store files be set up on the <guilabel>Code Completion</guilabel> tab of the <guilabel>C++ Specific</guilabel> project configuration page. Information about these additional <filename>.pcs</filename> is kept globally in the <filename class="directory">$<envar>TDEHOME</envar>/share/apps/kdevcppsupport/pcs/</filename> directory.
</para></note>
</sect2>

4
doc/tdevelop/nutshell.docbook
Unescape View File

@ -43,7 +43,7 @@ Interface</guimenuitem></menuchoice>).</para>
may not be available. To change the toolview tabs display manually, place a
<option>MDIStyle</option> entry under the
<option>[UI]</option> tag in your
<filename>$KDEHOME/share/config/tdeveloprc</filename> configuration file as
<filename>$TDEHOME/share/config/tdeveloprc</filename> configuration file as
follows:</para>
<simplelist>
@ -65,7 +65,7 @@ this may help:</para>
<itemizedlist>
<listitem><para>In your
<filename>$<envar>KDEHOME</envar>/share/config/tdeveloprc</filename>
<filename>$<envar>TDEHOME</envar>/share/config/tdeveloprc</filename>
configuration file find the line containing
<quote><computeroutput>Style=Checked</computeroutput></quote> and remove
it. Then restart &tdevelop;.

6
doc/tdevelop/setup.docbook
Unescape View File

@ -1600,7 +1600,7 @@ In short, such an &API; documents the interface to certain library functions. Th
There are some structural constraints assumed when searching for &doxygen; generated &API; documentation. The directory in which the <filename>index.html</filename> file resides should contain subdirectories with separate documentation collections. Each of these subdirectories is assumed to contain a <filename>.tag</filename> file and a <filename class="directory">html/</filename> subdirectory.
</para>
<para>
You may have a look at <filename class="directory">$<envar>KDEDIR</envar>/share/doc/HTML/en/tdelibs-apidocs</filename> for an example of such a &doxygen; &API; documentation layout.
You may have a look at <filename class="directory">$<envar>TDEDIR</envar>/share/doc/HTML/en/tdelibs-apidocs</filename> for an example of such a &doxygen; &API; documentation layout.
</para>
<note><para>
@ -1621,7 +1621,7 @@ The older &kde; <ulink url="http://sirtaj.net/projects/kdoc/">KDoc</ulink> gener
Or the <command>configure</command> command did automatically find a &doxygen; generated &kde; Libraries &API; in one of several standard locations it knows of.
</para></listitem>
<listitem><para>
Or as a last resort the <filename class="directory">$<envar>KDEDIR</envar>/share/doc/HTML/en/tdelibs-apidocs/</filename> was found at the first &tdevelop; startup.
Or as a last resort the <filename class="directory">$<envar>TDEDIR</envar>/share/doc/HTML/en/tdelibs-apidocs/</filename> was found at the first &tdevelop; startup.
</para></listitem>
</itemizedlist>
@ -1720,7 +1720,7 @@ Such structured access is made possible through the use of special <quote>table
<term>Standard Directory of &tdevelop; TOC Files</term>
<listitem>
<para>
When &tdevelop; was installed usually a series of predefined <filename>.toc</filename> files has been put into the <filename class="directory">$KDEDIR/share/apps/kdevdocumentation/tocs</filename> directory. These are fairly simple, structured text files. You may look at them using a text editor or other text display facility.
When &tdevelop; was installed usually a series of predefined <filename>.toc</filename> files has been put into the <filename class="directory">$TDEDIR/share/apps/kdevdocumentation/tocs</filename> directory. These are fairly simple, structured text files. You may look at them using a text editor or other text display facility.
</para>
</listitem>
</varlistentry></variablelist>

36
doc/tdevelop/tdevelop-install.docbook
Unescape View File

@ -319,7 +319,7 @@ In order to successfully compile and use &tdevelop;, you need the following prog
</para>
<informalexample><simplelist>
<member><prompt>(your-tdevelop-directory)&gt; </prompt>
<userinput>ln -s $KDEDIR/share/apps/tdelibs/admin admin</userinput></member>
<userinput>ln -s $TDEDIR/share/apps/tdelibs/admin admin</userinput></member>
</simplelist></informalexample>
<para>
at the console. This causes &tdevelop; to use the standard settings in the &kde; <filename class="directory">admin</filename> directory instead.
@ -369,7 +369,7 @@ Once all requirements are met, you are ready to compile and install &tdevelop;.
<primary>preliminaries</primary>
<secondary>&tdevelop; installation</secondary></indexterm>
<indexterm zone="compile-and-install-preliminaries">
<primary>KDEDIR</primary></indexterm>
<primary>TDEDIR</primary></indexterm>
<indexterm zone="compile-and-install-preliminaries">
<primary>QTDIR</primary></indexterm>
<indexterm zone="compile-and-install-preliminaries">
@ -395,11 +395,11 @@ If you use the bash shell add the following lines:
</para>
<informalexample><simplelist>
<member><userinput>export KDEDIR=</userinput>(path to your KDE installation)</member>
<member><userinput>export TDEDIR=</userinput>(path to your KDE installation)</member>
<member><userinput>export QTDIR=</userinput>(path to your Qt library)</member>
<member><userinput>export LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib:$LD_LIBRARY_PATH</userinput></member>
<member><userinput>export LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib:$LIBRARY_PATH</userinput></member>
<member><userinput>export PATH=$QTDIR/bin:$KDEDIR/bin:$PATH</userinput></member>
<member><userinput>export LD_LIBRARY_PATH=$QTDIR/lib:$TDEDIR/lib:$LD_LIBRARY_PATH</userinput></member>
<member><userinput>export LIBRARY_PATH=$QTDIR/lib:$TDEDIR/lib:$LIBRARY_PATH</userinput></member>
<member><userinput>export PATH=$QTDIR/bin:$TDEDIR/bin:$PATH</userinput></member>
</simplelist></informalexample>
<para></para>
@ -413,11 +413,11 @@ If you use the tcsh shell add the following lines:
</para>
<para>
<informalexample><simplelist>
<member><userinput>setenv KDEDIR </userinput>(path to your KDE installation)</member>
<member><userinput>setenv TDEDIR </userinput>(path to your KDE installation)</member>
<member><userinput>setenv QTDIR </userinput>(path to your Qt library)</member>
<member><userinput>setenv LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib:$LD_LIBRARY_PATH</userinput></member>
<member><userinput>setenv LIBRARY_PATH $QTDIR/lib:$KDEDIR/lib:$LIBRARY_PATH</userinput></member>
<member><userinput>setenv PATH $QTDIR/bin:$KDEDIR/bin:$PATH</userinput></member>
<member><userinput>setenv LD_LIBRARY_PATH=$QTDIR/lib:$TDEDIR/lib:$LD_LIBRARY_PATH</userinput></member>
<member><userinput>setenv LIBRARY_PATH $QTDIR/lib:$TDEDIR/lib:$LIBRARY_PATH</userinput></member>
<member><userinput>setenv PATH $QTDIR/bin:$TDEDIR/bin:$PATH</userinput></member>
</simplelist></informalexample>
</para>
@ -539,7 +539,7 @@ If you want to build your own <link linkend="make-api">API documentation</link>
</para>
<informalexample><simplelist>
<member><prompt>~/trinitysrc/tdevelop&gt; </prompt>
<userinput>./configure --</userinput>(options-as-above) <userinput>\</userinput></member> <member><userinput>--with-tdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/tdelibs-apidocs</userinput></member>
<userinput>./configure --</userinput>(options-as-above) <userinput>\</userinput></member> <member><userinput>--with-tdelibsdoxy-dir=$TDEDIR/share/doc/HTML/en/tdelibs-apidocs</userinput></member>
</simplelist></informalexample>
</note>
</listitem>
@ -606,7 +606,7 @@ That's all. If you installed &tdevelop; in the default &kde; directory you may n
<indexterm zone="compile-and-install-options-dir">
<primary>non-default directory</primary></indexterm>
<indexterm zone="compile-and-install-options-dir">
<primary>KDEDIRS</primary></indexterm>
<primary>TDEDIRS</primary></indexterm>
<indexterm zone="compile-and-install-options-dir">
<primary>kbuildsycoca</primary></indexterm>
@ -625,13 +625,13 @@ Call up a shell and have the following commands executed before you start &tdeve
</para>
<note><para>
<emphasis>Take care to use the plural:</emphasis> It is <quote><envar>KDEDIRS</envar></quote>, not just <quote><envar>KDEDIR</envar></quote>)
<emphasis>Take care to use the plural:</emphasis> It is <quote><envar>TDEDIRS</envar></quote>, not just <quote><envar>TDEDIR</envar></quote>)
</para></note>
<informalexample><simplelist>
<member>
<prompt>~&gt; </prompt>
<userinput>export KDEDIRS=/usr/local/kde:/opt/trinity</userinput>
<userinput>export TDEDIRS=/usr/local/kde:/opt/trinity</userinput>
</member>
<member>
<prompt>~&gt; </prompt>
@ -647,7 +647,7 @@ Call up a shell and have the following commands executed before you start &tdeve
</simplelist></informalexample>
<note><simplelist>
<member>The <envar>KDEDIRS</envar> environment variable must be set to the <emphasis>list of active &kde; directories</emphasis> in your system. We use</member>
<member>The <envar>TDEDIRS</envar> environment variable must be set to the <emphasis>list of active &kde; directories</emphasis> in your system. We use</member>
<member><filename class="directory">/usr/local/kde</filename>:<filename class="directory">/opt/trinity</filename></member>
<member>as an example only.</member>
<member>The <filename class="directory">/usr/local/kde</filename> directory may for instance contain an incomplete &kde; version you compiled for debug purposes, and the <filename class="directory">/opt/trinity</filename> directory may in addition contain the standard &kde; version from your distribution that is used for everyday work.</member>
@ -658,7 +658,7 @@ In a tcsh shell you must set the environment variables using:
</para>
<informalexample><simplelist><member>
<prompt>~&gt; </prompt>
<userinput>setenv KDEDIRS /usr/local/kde:/opt/trinity</userinput>
<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&mdash;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.
@ -711,12 +711,12 @@ Alas, this version is best used read-only over the internet. If you do not alway
<userinput>./configure --</userinput>(options-as-usual)<userinput> \</userinput>
</member>
<member>
<userinput>--with-tdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/tdelibs-apidocs</userinput>
<userinput>--with-tdelibsdoxy-dir=$TDEDIR/share/doc/HTML/en/tdelibs-apidocs</userinput>
</member>
</simplelist></informalexample>
<para>
(<command>make</command> will replace the global <varname>$KDEDIR</varname> variable with the actual &kde; directory setting recorded therein.) Then issue a <command>make</command> command <link linkend="compile-and-install-make-basic">as usual</link>. After the &tdevelop; IDE has been built you have the option to build the API as well. For this you must issue
(<command>make</command> will replace the global <varname>$TDEDIR</varname> variable with the actual &kde; directory setting recorded therein.) Then issue a <command>make</command> command <link linkend="compile-and-install-make-basic">as usual</link>. After the &tdevelop; IDE has been built you have the option to build the API as well. For this you must issue
</para>
<informalexample><simplelist><member>
<prompt>~/trinitysrc/tdevelop&gt; </prompt>

2
doc/tdevelop/tdevelop-scripting.docbook
Unescape View File

@ -38,7 +38,7 @@ The next step is to create the actual script. For the above example the Type of
<para>The KDCOP tool allows script developers to browse and debug the current interfaces of the host application. KDCOP also provides a neat feature of allowing users to select a method and drag the current code to their text editor. This simplifies use for people who are not savvy to the DCOP methods of the host language. Currently KDCOP supports KJSEmbed, Python, and UNIX Shell method for accessing DCOP.</para>
<para>Once the script is complete it is ready to be installed. Application developers should document the location that will be scanned for scripts. In the case of the above example for Kate the scripts are located in "$KDEDIRS/share/apps/kate/scripts".</para>
<para>Once the script is complete it is ready to be installed. Application developers should document the location that will be scanned for scripts. In the case of the above example for Kate the scripts are located in "$TDEDIRS/share/apps/kate/scripts".</para>
<figure id="screenshot-scripts" float="1">
<title>&tdevelop; Scripts on the Filesystem</title>

2
languages/cpp/app_templates/kapp/README
Unescape View File

@ -69,7 +69,7 @@ http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.ht
http://public.kde.planetmirror.com/pub/kde/devel/gettext-kde/
2. Install that gettext in ~/bin/
3. cd ~/yourproject, export PATH=~/bin:$PATH, export
KDEDIR=/where_your_KDE3_is
TDEDIR=/where_your_KDE3_is
4. make -f admin/Makefile.common package-messages
5. make package-messages
6. Translate the po files (not the pot!!) with kbabel or xemacs

2
languages/cpp/app_templates/kconfig35/README
Unescape View File

@ -78,7 +78,7 @@ http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.ht
http://public.kde.planetmirror.com/pub/kde/devel/gettext-kde/
2. Install that gettext in ~/bin/
3. cd ~/yourproject, export PATH=~/bin:$PATH, export
KDEDIR=/where_your_KDE3_is
TDEDIR=/where_your_KDE3_is
4. make -f admin/Makefile.common package-messages
5. make package-messages
6. Translate the po files (not the pot!!) with kbabel or xemacs

8
languages/cpp/app_templates/kde4app/kde4app.tdevelop
Unescape View File

@ -118,8 +118,8 @@
<terminal>false</terminal>
<autocompile>false</autocompile>
<envvars>
<envvar value="" name="KDEDIRS" />
<envvar value="" name="KDEHOME" />
<envvar value="" name="TDEDIRS" />
<envvar value="" name="TDEHOME" />
<envvar value="" name="LD_LIBRARY_PATH" />
<envvar value="" name="PATH" />
<envvar value="" name="PKG_CONFIG_PATH" />
@ -147,8 +147,8 @@
<selectedenvironment>default</selectedenvironment>
<environments>
<default>
<envvar value="" name="KDEDIRS" />
<envvar value="" name="KDEHOME" />
<envvar value="" name="TDEDIRS" />
<envvar value="" name="TDEHOME" />
<envvar value="" name="LD_LIBRARY_PATH" />
<envvar value="" name="PATH" />
<envvar value="" name="PKG_CONFIG_PATH" />

2
languages/cpp/app_templates/kfileplugin/kfile_plugin.h
Unescape View File

@ -4,7 +4,7 @@
#define __KFILE_%{APPNAMEUC}_H__
/**
* Note: For further information look into <$KDEDIR/include/kfilemetainfo.h>
* Note: For further information look into <$TDEDIR/include/kfilemetainfo.h>
*/
#include <kfilemetainfo.h>

16
languages/cpp/app_templates/kofficepart/kde-configure.in.in
Unescape View File

@ -8,22 +8,22 @@ AC_C_BIGENDIAN
AC_CHECK_KDEMAXPATHLEN
dnl AC_DEFINE(USE_QFD, 1, [Define if you prefer the Qt provided file dialog])
KWMF_INCLUDES='-I$(KDEDIR)/lib/kwmf -I$(KDEDIR)/lib/kwmf'
KWMF_INCLUDES='-I$(TDEDIR)/lib/kwmf -I$(TDEDIR)/lib/kwmf'
AC_SUBST(KWMF_INCLUDES)
KSTORE_INCLUDES='-I$(KDEDIR)/include'
KSTORE_INCLUDES='-I$(TDEDIR)/include'
AC_SUBST(KSTORE_INCLUDES)
KOFFICECORE_INCLUDES='-I$(KDEDIR)/include'
KOFFICECORE_INCLUDES='-I$(TDEDIR)/include'
AC_SUBST(KOFFICECORE_INCLUDES)
KOFFICEUI_INCLUDES='-I$(KDEDIR)/include'
KOFFICEUI_INCLUDES='-I$(TDEDIR)/include'
AC_SUBST(KOFFICEUI_INCLUDES)
LIB_KOFFICEUI='$(KDEDIR)/lib/libkofficeui.la'
LIB_KOFFICECORE='$(KDEDIR)/lib/libkofficecore.la'
LIB_KSTORE='$(KDEDIR)/lib/libkstore.la'
LIB_KWMF='$(KDEDIR)/lib/libkwmf.la'
LIB_KOFFICEUI='$(TDEDIR)/lib/libkofficeui.la'
LIB_KOFFICECORE='$(TDEDIR)/lib/libkofficecore.la'
LIB_KSTORE='$(TDEDIR)/lib/libkstore.la'
LIB_KWMF='$(TDEDIR)/lib/libkwmf.la'
AC_SUBST(LIB_KOFFICEUI)
AC_SUBST(LIB_KOFFICECORE)
AC_SUBST(LIB_KSTORE)

2
languages/cpp/app_templates/kscons_kmdi/INSTALL
Unescape View File

@ -48,7 +48,7 @@ The installation scripts are relying on the kde-config program.
The programs kde-config, qmake, uic and moc must be accesssible
through your PATH.
Qt and kde may not be installed as expected (in QTDIR and KDEDIR)
Qt and kde may not be installed as expected (in QTDIR and TDEDIR)
So until kde-config is able to give that information, you may
have to give those paths. You may also want to tune the build.

2
languages/cpp/app_templates/kscons_kmdi/README
Unescape View File

@ -101,7 +101,7 @@ refer to the file po/SConscript and po/messages.sh
http://public.kde.planetmirror.com/pub/kde/devel/gettext-kde/
2. Install that gettext in ~/bin/
3. cd ~/yourproject, export PATH=~/bin:$PATH, export
KDEDIR=/where_your_KDE3_is
TDEDIR=/where_your_KDE3_is
4. make -f admin/Makefile.common package-messages
5. make package-messages
6. Translate the po files (not the pot!!) with kbabel or xemacs

2
languages/cpp/app_templates/kscons_kmdi/messages.sh
Unescape View File

@ -17,7 +17,7 @@
SRCDIR=../test1-kconfigxt # srcdir is the directory containing the source code
TIPSDIR=$SRCDIR # tipsdir is the directory containing the tips
KDEDIR=`kde-config --prefix`
TDEDIR=`kde-config --prefix`
EXTRACTRC=extractrc
KDEPOT=`kde-config --prefix`/include/kde.pot
XGETTEXT="xgettext -C -ki18n -ktr2i18n -kI18N_NOOP -ktranslate -kaliasLocale -x $KDEPOT "

2
languages/cpp/app_templates/kscons_kxt/INSTALL
Unescape View File

@ -48,7 +48,7 @@ The installation scripts are relying on the kde-config program.
The programs kde-config, qmake, uic and moc must be accesssible
through your PATH.
Qt and kde may not be installed as expected (in QTDIR and KDEDIR)
Qt and kde may not be installed as expected (in QTDIR and TDEDIR)
So until kde-config is able to give that information, you may
have to give those paths. You may also want to tune the build.

2
languages/cpp/app_templates/kscons_kxt/README
Unescape View File

@ -101,7 +101,7 @@ refer to the file po/SConscript and po/messages.sh
http://public.kde.planetmirror.com/pub/kde/devel/gettext-kde/
2. Install that gettext in ~/bin/
3. cd ~/yourproject, export PATH=~/bin:$PATH, export
KDEDIR=/where_your_KDE3_is
TDEDIR=/where_your_KDE3_is
4. make -f admin/Makefile.common package-messages
5. make package-messages
6. Translate the po files (not the pot!!) with kbabel or xemacs

2
languages/cpp/app_templates/kscons_kxt/messages.sh
Unescape View File

@ -17,7 +17,7 @@
SRCDIR=../test1-kconfigxt # srcdir is the directory containing the source code
TIPSDIR=$SRCDIR # tipsdir is the directory containing the tips
KDEDIR=`kde-config --prefix`
TDEDIR=`kde-config --prefix`
EXTRACTRC=extractrc
KDEPOT=`kde-config --prefix`/include/kde.pot
XGETTEXT="xgettext -C -ki18n -ktr2i18n -kI18N_NOOP -ktranslate -kaliasLocale -x $KDEPOT "

2
languages/cpp/app_templates/kxt/README
Unescape View File

@ -74,7 +74,7 @@ http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.ht
http://public.kde.planetmirror.com/pub/kde/devel/gettext-kde/
2. Install that gettext in ~/bin/
3. cd ~/yourproject, export PATH=~/bin:$PATH, export
KDEDIR=/where_your_KDE3_is
TDEDIR=/where_your_KDE3_is
4. make -f admin/Makefile.common package-messages
5. make package-messages
6. Translate the po files (not the pot!!) with kbabel or xemacs

12
languages/cpp/doc/kde2book.toc
Unescape View File

@ -903,7 +903,7 @@
<entry name="enabling, debugging, gdb debugger" url="ch18lev1sec6.html"/>
<entry name="endTransaction() method" url="ch13lev1sec5.html"/>
<entry name="enterEvent() event handler, widgets" url="ch04.html"/>
<entry name="environment variables, KDEDIR" url="ch02lev1sec2.html"/>
<entry name="environment variables, TDEDIR" url="ch02lev1sec2.html"/>
<entry name="environment variables, QTDIR" url="ch02lev1sec2.html"/>
<entry name="error() function" url="ch05lev1sec3.html"/>
<entry name="Ettrich, Matthias" url="ch01.html"/>
@ -1309,8 +1309,8 @@
<entry name="kde-common module (CVS)" url="ch17lev1sec2.html"/>
<entry name="kde-devel mailing list" url="ch01lev1sec3.html"/>
<entry name="KDE Developers' Web site" url="ch01lev1sec2.html"/>
<entry name="KDEDIR environment variable" url="ch02lev1sec2.html"/>
<entry name="$KDEDIR/share/appstext.txt (KResourceDemo widget)" url="ch07lev1sec4.html"/>
<entry name="TDEDIR environment variable" url="ch02lev1sec2.html"/>
<entry name="$TDEDIR/share/appstext.txt (KResourceDemo widget)" url="ch07lev1sec4.html"/>
<entry name="KDE, distributions" url="ch01lev1sec2.html"/>
<entry name="tdegames module (CVS)" url="ch17lev1sec2.html"/>
<entry name="tdegames package" url="ch01lev1sec5.html"/>
@ -1506,7 +1506,7 @@
<entry name="KRemoteDemo widget, main() function" url="ch07lev1sec5.html"/>
<entry name="kresourcedemo.cpp file (KResourceDemo widget)" url="ch07lev1sec4.html"/>
<entry name="kresourcedemo.h file (KResourceDemo widget)" url="ch07lev1sec4.html"/>
<entry name="KResourceDemo widget, $KDEDIR/share/appstext.txt contents" url="ch07lev1sec4.html"/>
<entry name="KResourceDemo widget, $TDEDIR/share/appstext.txt contents" url="ch07lev1sec4.html"/>
<entry name="KResourceDemo widget, kresourcedemo.cpp class definition" url="ch07lev1sec4.html"/>
<entry name="KResourceDemo widget, kresourcedemo.h class declaration" url="ch07lev1sec4.html"/>
<entry name="KResourceDemo widget, kresource.po translation template file" url="ch07lev1sec4.html"/>
@ -1709,7 +1709,7 @@
<entry name="listings, KRemoteDemo widget, kremotedemo.cpp class definition" url="ch07lev1sec5.html"/>
<entry name="listings, KRemoteDemo widget, kremotedemo.h class declaration" url="ch07lev1sec5.html"/>
<entry name="listings, KRemoteDemo widget, main() function" url="ch07lev1sec5.html"/>
<entry name="listings, KResourceDemo widget, $KDEDIR/share/appstext.txt contents" url="ch07lev1sec4.html"/>
<entry name="listings, KResourceDemo widget, $TDEDIR/share/appstext.txt contents" url="ch07lev1sec4.html"/>
<entry name="listings, KResourceDemo widget, kresourcedemo.cpp class definition" url="ch07lev1sec4.html"/>
<entry name="listings, KResourceDemo widget, kresourcedemo.h class declaration" url="ch07lev1sec4.html"/>
<entry name="listings, KResourceDemo widget, kresource.po translation template file" url="ch07lev1sec4.html"/>
@ -2739,7 +2739,7 @@
<entry name="utilities, make" url="ch02lev1sec2.html"/>
<entry name="utilities, xgettext" url="ch07lev1sec4.html"/>
<entry name="utility classes, (Qt)" url="ch03lev1sec5.html"/>
<entry name="variables, environment variables, KDEDIR" url="ch02lev1sec2.html"/>
<entry name="variables, environment variables, TDEDIR" url="ch02lev1sec2.html"/>
<entry name="variables, environment variables, QTDIR" url="ch02lev1sec2.html"/>
<entry name="Variable Viewer (VAR)" url="ch18.html"/>
<entry name="VAR (Variable Viewer)" url="ch18.html"/>

2
languages/cpp/kdevdriver.cpp
Unescape View File

@ -101,7 +101,7 @@ void KDevDriver::setup()
addMacro( Macro( "__cplusplus", "1" ) );
///@todo maybe remove the following? Is there any normal user who has his environment set up correctly so this is of any use?
TQString kdedir = getenv( "KDEDIR" );
TQString kdedir = getenv( "TDEDIR" );
if( !kdedir.isNull() )
addIncludePath( kdedir + "/include" );

2
languages/cpp/main.cpp
Unescape View File

@ -82,7 +82,7 @@ public:
// code provided by Reginald Stadlbauer <reggie@trolltech.com>
void setup()
{
TQString kdedir = getenv( "KDEDIR" );
TQString kdedir = getenv( "TDEDIR" );
if ( !kdedir.isNull() )
addIncludePath( kdedir + "/include" );

2
languages/ruby/app_templates/kapp/README
Unescape View File

@ -69,7 +69,7 @@ http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.ht
http://public.kde.planetmirror.com/pub/kde/devel/gettext-kde/
2. Install that gettext in ~/bin/
3. cd ~/yourproject, export PATH=~/bin:$PATH, export
KDEDIR=/where_your_KDE3_is
TDEDIR=/where_your_KDE3_is
4. make -f admin/Makefile.common package-messages
5. make package-messages
6. Translate the po files (not the pot!!) with kbabel or xemacs

4
lib/catalog/Mainpage.dox
Unescape View File

@ -3,8 +3,8 @@
This is the persistant symbol store library working with BerkeleyDb backend.
<b>Link with</b>: -lkdevcatalog \$(KDEDIR)/kdevbdb/libdb.a
<b>Link with</b>: -lkdevcatalog \$(TDEDIR)/kdevbdb/libdb.a
<b>Include path</b>: -I\$(kde_includes)/tdevelop/catalog -I\$(KDEDIR)/kdevbdb/include
<b>Include path</b>: -I\$(kde_includes)/tdevelop/catalog -I\$(TDEDIR)/kdevbdb/include
*/

6
parts/appwizard/common/scons/admin/kde.py
Unescape View File

@ -52,7 +52,7 @@ def detect_kde(env):
print "Make sure kde is installed properly"
print "(missing package tdebase-devel?)"
env.Exit(1)
env['KDEDIR'] = os.popen('kde-config -prefix').read().strip()
env['TDEDIR'] = os.popen('kde-config -prefix').read().strip()
print "Checking for kde version : ",
kde_version = os.popen("kde-config --version|grep KDE").read().strip().split()[1]
@ -371,7 +371,7 @@ ie: """+BOLD+"""scons configure libdir=/usr/local/lib qtincludes=/usr/include/qt
('QT_UIC', 'tqmoc directory'),
('QT_TQMOC', 'tqmoc executable command'),
('QTPLUGINS', 'uic executable command'),
('KDEDIR', 'root of kde directory'),
('TDEDIR', 'root of kde directory'),
('KDELIBPATH', 'path to the kde libs'),
('KDEINCLUDEPATH', 'path to the kde includes'),
@ -392,7 +392,7 @@ ie: """+BOLD+"""scons configure libdir=/usr/local/lib qtincludes=/usr/include/qt
opts.Update(env)
# reconfigure when things are missing
if not env['HELP'] and (env['_CONFIGURE'] or not env.has_key('QTDIR') or not env.has_key('KDEDIR')):
if not env['HELP'] and (env['_CONFIGURE'] or not env.has_key('QTDIR') or not env.has_key('TDEDIR')):
detect_kde(env)
# finally save the configuration to the cache file

2
parts/scripting/scriptingglobalconfigbase.ui
Unescape View File

@ -38,7 +38,7 @@
<cstring>textLabel2</cstring>
</property>
<property name="text">
<string>&lt;b&gt;NOTE&lt;/b&gt; These are directories to search in that are found in your KDE resource directories. So if you add the string "kate/scripts" to the list then KScript will look in "$KDEDIRS/data/kate/scripts" for scripts. This will allow you to get scripts in your home directory as well as system wide ones.</string>
<string>&lt;b&gt;NOTE&lt;/b&gt; These are directories to search in that are found in your KDE resource directories. So if you add the string "kate/scripts" to the list then KScript will look in "$TDEDIRS/data/kate/scripts" for scripts. This will allow you to get scripts in your home directory as well as system wide ones.</string>
</property>
</widget>
</vbox>

4
src/simplemainwindow.cpp
Unescape View File

@ -99,9 +99,9 @@ void SimpleMainWindow::init()
" properly.\nPlease make sure "
"that KDevelop is installed in your KDE directory; otherwise, you have "
"to add KDevelop's installation "
"path to the environment variable KDEDIRS and run kbuildsycoca. Restart "
"path to the environment variable TDEDIRS and run kbuildsycoca. Restart "
"KDevelop afterwards.\n"
"Example for BASH users:\nexport KDEDIRS=/path/to/tdevelop:$KDEDIRS && kbuildsycoca"),
"Example for BASH users:\nexport TDEDIRS=/path/to/tdevelop:$TDEDIRS && kbuildsycoca"),
i18n("Could Not Find Plugins") );
}

2
vcs/cvsservice/README.dox
Unescape View File

@ -2,7 +2,7 @@
This plugin integrates Cervisia (version >= 2.1) cvsservice DCOP service into tdevelop (read FAQ at the bottom
of this document): so, this part _does_ require cvsservice installed on your system: the configure script
in the main source directory should automagically detect the presence of Cervisia and build this plugin.
If Cervisia wasn't installed in $KDEDIR than you need to specify paths for lib and include
If Cervisia wasn't installed in $TDEDIR than you need to specify paths for lib and include
files, for example:
<code>
--with-extra-libs=$HOME/kde/lib --with-extra-includes=$HOME/kde/include

Write Preview
Loading…
Cancel
Save