From ab257225f82696202bf13962be1926f7bbdad243 Mon Sep 17 00:00:00 2001 From: tpearson Date: Sun, 21 Aug 2011 01:43:11 +0000 Subject: Convert remaining references to kde3 (e.g. in paths) to trinity git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdevelop@1248408 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- doc/kdevelop/applicationwizard.docbook | 2 +- doc/kdevelop/kdevelop-install.docbook | 60 ++++++++++++++++----------------- doc/kdevelop/project-management.docbook | 2 +- 3 files changed, 32 insertions(+), 32 deletions(-) (limited to 'doc/kdevelop') diff --git a/doc/kdevelop/applicationwizard.docbook b/doc/kdevelop/applicationwizard.docbook index 9ffea830..6370cb12 100644 --- a/doc/kdevelop/applicationwizard.docbook +++ b/doc/kdevelop/applicationwizard.docbook @@ -598,7 +598,7 @@ When any information of all these is wrong &kdevelop; usually will not know abou * cd '/home/devel/test' && cvs -d '/home/devel/mycvsroot' \ import -m 'new project' '' 'vendor' 'start' &&\ - sh /opt/kde3/share/apps/kdevcvs/buildcvs.sh . '' \ + sh /opt/trinity/share/apps/kdevcvs/buildcvs.sh . '' \ '/home/devel/mycvsroot' * cvs [import aborted]: /home/devel/mycvsroot/CVSROOT: No such file or directory diff --git a/doc/kdevelop/kdevelop-install.docbook b/doc/kdevelop/kdevelop-install.docbook index 1ff5982c..028f5e10 100644 --- a/doc/kdevelop/kdevelop-install.docbook +++ b/doc/kdevelop/kdevelop-install.docbook @@ -73,7 +73,7 @@ To obtain an initial version of &kdevelop; you must download it from anonymous s -We assume you want to put your &kdevelop; copy into the kde3src subdirectory of your home directory (~). +We assume you want to put your &kdevelop; copy into the trinitysrc subdirectory of your home directory (~). @@ -82,18 +82,18 @@ We assume you want to put your &kdevelop; copy into the update -After you checked out (and successfully compiled) &kdevelop; from svn as shown above, you'll want to keep it up to date in order to get all the patches. Follow these steps. (We again assume you have put your &kdevelop; copy into the kde3src directory.) +After you checked out (and successfully compiled) &kdevelop; from svn as shown above, you'll want to keep it up to date in order to get all the patches. Follow these steps. (We again assume you have put your &kdevelop; copy into the trinitysrc directory.) Note the up (= update) command instead of the co (which stands for checkout). @@ -132,14 +132,14 @@ Note the up (= update) command instead o ~> - cd kde3src + cd trinitysrc - ~/kde3src> + ~/trinitysrc> cd kdevelop - ~/kde3src> + ~/trinitysrc> svn up @@ -436,7 +436,7 @@ If you use the tcsh shell add the following lines: &kdevelop; -In the following discussion we assume that you have put your &kdevelop; sources in the ~/kde3src/kdevelop directory. +In the following discussion we assume that you have put your &kdevelop; sources in the ~/trinitysrc/kdevelop directory. @@ -455,7 +455,7 @@ You must initialize the make system after a fresh checkout. - ~/kde3src/kdevelop> + ~/trinitysrc/kdevelop> make -f admin/Makefile.common svn-clean @@ -484,7 +484,7 @@ U /some_directory_path/Makefile.am or if you just did a full checkout, you must enter: - ~/kde3src/kdevelop> + ~/trinitysrc/kdevelop> make -f Makefile.svn @@ -515,8 +515,8 @@ If you want to keep track of what your &kdevelop; application does at run-time y - ~/kde3src/kdevelop> - ./configure --enable-debug=full --prefix=(where-your-kde3-is) + ~/trinitysrc/kdevelop> + ./configure --enable-debug=full --prefix=(where-your-trinity-is) @@ -529,8 +529,8 @@ running) release version suffices. configure defaults to this. - ~/kde3src/kdevelop> - ./configure --prefix=(where-your-kde3-is) + ~/trinitysrc/kdevelop> + ./configure --prefix=(where-your-trinity-is) @@ -538,7 +538,7 @@ this. If you want to build your own API documentation for &kdevelop; you must include yet another option in the configure command: - ~/kde3src/kdevelop> + ~/trinitysrc/kdevelop> ./configure --(options-as-above) \ --with-kdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/kdelibs-apidocs @@ -553,21 +553,21 @@ If you want to build your own API documentation - ~/kde3src/kdevelop> + ~/trinitysrc/kdevelop> make suffices. If necessary, now gain root user rights using the command - ~/kde3src/kdevelop> + ~/trinitysrc/kdevelop> su and entering the root password. Then install the application: - ~/kde3src/kdevelop> + ~/trinitysrc/kdevelop> make install @@ -614,8 +614,8 @@ That's all. If you installed &kdevelop; in the default &kde; directory you may n By default configure prepares the IDE to be installed in the default &kde; directory. This is necessary because &kdevelop; assumes direct access to some tools and parts which reside there. If want to use your own installation directory, you must tell configure this by the option: - ~/kde3src/kdevelop> - ./configure --prefix=(where-your-kde3-is) + ~/trinitysrc/kdevelop> + ./configure --prefix=(where-your-trinity-is) There is a caveat if you do so. You must provide a means for &kdevelop; to access the needed tools and parts in the &kde; directory when running. (You can still use the IDE without doing so, but with very restrained capabilities.) @@ -631,7 +631,7 @@ Call up a shell and have the following commands executed before you start &kdeve ~> - export KDEDIRS=/usr/local/kde:/opt/kde3 + export KDEDIRS=/usr/local/kde:/opt/trinity ~> @@ -648,9 +648,9 @@ Call up a shell and have the following commands executed before you start &kdeve The KDEDIRS environment variable must be set to the list of active &kde; directories in your system. We use - /usr/local/kde:/opt/kde3 + /usr/local/kde:/opt/trinity as an example only. - The /usr/local/kde directory may for instance contain an incomplete &kde; version you compiled for debug purposes, and the /opt/kde3 directory may in addition contain the standard &kde; version from your distribution that is used for everyday work. + The /usr/local/kde directory may for instance contain an incomplete &kde; version you compiled for debug purposes, and the /opt/trinity directory may in addition contain the standard &kde; version from your distribution that is used for everyday work. @@ -658,7 +658,7 @@ In a tcsh shell you must set the environment variables using: ~> - setenv KDEDIRS /usr/local/kde:/opt/kde3 + setenv KDEDIRS /usr/local/kde:/opt/trinity The kbuildsycoca command (build system control cache) looks around for libraries and caches their location and version, so that &kdevelop; 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 &kdevelop; from a non-default directory. You may want to put the above commands into a shell script to reduce the typing effort. @@ -707,7 +707,7 @@ Alas, this version is best used read-only over the internet. If you do not alway - ~/kde3src/kdevelop> + ~/trinitysrc/kdevelop> ./configure --(options-as-usual) \ @@ -719,7 +719,7 @@ Alas, this version is best used read-only over the internet. If you do not alway (make will replace the global $KDEDIR variable with the actual &kde; directory setting recorded therein.) Then issue a make command as usual. After the &kdevelop; IDE has been built you have the option to build the API as well. For this you must issue - ~/kde3src/kdevelop> + ~/trinitysrc/kdevelop> make apidocs @@ -728,7 +728,7 @@ This will build a Doxyfile in your &kdevelop; base director - ~/kde3src/kdevelop> + ~/trinitysrc/kdevelop> su @@ -737,7 +737,7 @@ and entering the root password. Then install the API files: - ~/kde3src/kdevelop> + ~/trinitysrc/kdevelop> make install-apidox diff --git a/doc/kdevelop/project-management.docbook b/doc/kdevelop/project-management.docbook index 38a3ff8d..eb0aebce 100644 --- a/doc/kdevelop/project-management.docbook +++ b/doc/kdevelop/project-management.docbook @@ -639,7 +639,7 @@ CXX = @CXX@ -prefix = /home/bernd/kde3 +prefix = /home/bernd/trinity INSTALL = /usr/bin/ginstall -c -p build_triplet = i686-pc-linux-gnu CXX = g++ -- cgit v1.2.1