https://community.kde.org/api.php?action=feedcontributions&user=Mr.+Anderson&feedformat=atomKDE Community Wiki - User contributions [en]2024-03-29T14:01:50ZUser contributionsMediaWiki 1.40.2https://community.kde.org/index.php?title=Kubuntu/PPAs&diff=41860Kubuntu/PPAs2015-03-14T09:51:06Z<p>Mr. Anderson: /* Weeekly Snapshot (pretty stable) */ Weeekly -> Weekly</p>
<hr />
<div>While Ubuntu does have a wide selection of software in their [https://help.ubuntu.com/community/Repositories/Ubuntu official apt repositories], as well as what is available in the official (but unsupported) Backports repository, providing packages for newer KDE SC versions (as well as some major applications) is often beyond the scope of these official software channels.<br />
<br />
This is why Kubuntu use the [https://launchpad.net/ubuntu/+ppas Launchpad PPA system] for their KDE technology upgrades.<br />
<br />
= Standard Ubuntu Repository Overview =<br />
== Important Security Updates ==<br />
This is where all your security fixes come from.<br />
== Recommended Updates ==<br />
Normal package updates come from here. Note that you will not always get every new KDE version.<br />
== Unsupported Updates ==<br />
This is the official Ubuntu [https://help.ubuntu.com/community/UbuntuBackports Backports] repository. this ''unsupported'' channel mostly contains individual packages "backported' from a newer Ubuntu release, but will usually provide a minor KDE SC "point" release if it provides significant bug fixes and stability.<br />
<br />
= Kubuntu's PPA Repositories =<br />
<br />
[[File:KubuntuPPAs.png]]<br />
<br />
=== Kubuntu Updates ===<br />
Updates for Kubuntu releases which are due to go to Ubuntu Updates. Mostly KDE '''point''' releases.<br />
<br />
Example:<br />
Kubuntu Intrepid 8.10 users would be able to test out upgrading from KDE SC 4.1.'''2''' to 4.1.'''4''' before those packages were moved to Ubuntu Updates.<br />
<br />
Use Case:<br />
* Releases that are supposed and qualify to go to Ubuntu Updates<br />
* Releases that do not qualify for Ubuntu Updates but have low risk of regression<br />
* KDE Applications ''point releases'' <br />
* Amarok ''point releases''<br />
* Calligra ''point releases''<br />
<br />
=== Kubuntu Backports ===<br />
Backports of new '''major''' versions of KDE SC and major KDE apps for Kubuntu which are not yet tested enough to go to Ubuntu Backports.<br />
<br />
Example:<br />
Karmic users would be able to try out upgrading Kubuntu Karmic's KDE SC from 4.'''3'''.x to 4.'''4'''.0 without having to wait for Lucid's release.<br />
<br />
Use Case:<br />
* Releases of new major versions<br />
* Releases that are tested but still bare a considerable risk of regression (for example due to a large change in the dependency stack, such as requirement bump from Qt 4.5 to 4.6)<br />
* KDE SC major releases and such that imply major stack changes<br />
* Amarok major releases and such that imply major stack changes<br />
* KOffice major releases and such that imply major stack changes<br />
<br />
=== Kubuntu Beta Backports ===<br />
Backports of '''pre-release''' versions of KDE SC, Plasma and major KDE apps, not suitable for production environments but good for those wishing to help test upcoming KDE features and software.<br />
<br />
Use Case:<br />
* Any kind of pre-release that is suited for general testing<br />
* Any kind of release that is expected to be imperfect and requires (more) testing<br />
* KDE SC alpha/beta/rc releases<br />
* Amarok alpha/beta/rc releases<br />
* KOffice alpha/beta/rc releases<br />
* Note that backports also suites pre-release software that cannot be included in the current dev series (so for example if lucid is in feature freeze, kdevelop's unstable version would land for both karmic and lucid in beta-backports)<br />
<br />
=== Kubuntu Experimental ===<br />
Experimental software or experimental packages, not suitable for production environments nor for those wishing to help doing regular testing. This PPA should only be used by people who know how to recover a system and are well instructed by the developers.<br />
<br />
Example:<br />
The Kubuntu tool software-properties gets ported to C++, for initial testing it gets published to Kubuntu Experimental to ensure there are no grave issues that render sources.list unusable.<br />
<br />
Use Case:<br />
* Any kind of untested software that might break the system gravely<br />
* Packages that might break the system gravely<br />
* Anything that is endangering the user's system and does not fit any other PPA<br />
<br />
=== Kubuntu Package Staging ===<br />
'''DO NOT USE THIS PPA!'''<br />
<br />
The staging PPA is a build ground for new packages and whole package stacks (such as KDE SC), once they are ''staged'' they get moved to the most appropriate PPA from above. In consequence this means that staging can contain anything from an update to an experimental package and thus might very easily break your system.<br />
<br />
Example:<br />
Before a new KDE SC gets published to the Kubuntu Backports PPA, it gets built in the clean environment of the staging PPA, once all packages are built and upgrade testing is done, all of staging gets moved to Kubuntu Backports.<br />
<br />
Use Case:<br />
* Staging only (PPA must be cleaned first to ensure coherent stacks)<br />
<br />
== Kubuntu Continuous Integration (CI) ==<br />
<br />
[[Image:Kubuntu-ci.png]]<br />
<br />
The Kubuntu CI system does builds from KDE Git master along with Kubuntu packaging. It is useful for developing and testing KDE software as well as Kubuntu packaging. ''It replaces Project Neon 5.'' Builds of KDE stable branches are due to be added in the future.<br />
<br />
Supported Kubuntu versions are limited to: 14.10 and 15.04 (development version).<br />
<br />
=== Weekly Snapshot (pretty stable) ===<br />
[https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable-weekly Kubuntu CI Unstable Weekly] packages from unstable-daily are moved here after manual weekly testing. These packages are used to build the Kubuntu CI images. <br />
<br />
To use this run:<br />
<pre><br />
sudo add-apt-repository ppa:kubuntu-ppa/next<br />
sudo add-apt-repository ppa:kubuntu-ci/unstable-weekly<br />
sudo apt update<br />
sudo apt install kubuntu-plasma5-desktop <br />
sudo apt dist-upgrade<br />
</pre><br />
<br />
=== Daily Snapshot (somewhat stable) ===<br />
[https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable-daily Kubuntu CI Unstable Daily] daily builds of KDE Git master with Kubuntu packaging. Packages are moved here from unstable if they build properly, can be installed over the previous build and if they can be purged again. This makes daily a suitable choice for most people who are not afraid of the odd breakage every now and then.<br />
<br />
To use this run:<br />
<pre><br />
sudo add-apt-repository ppa:kubuntu-ppa/next<br />
sudo add-apt-repository ppa:kubuntu-ci/unstable-daily<br />
sudo apt update<br />
sudo apt install kubuntu-plasma5-desktop <br />
sudo apt dist-upgrade<br />
</pre><br />
<br />
=== Live (might eat kittens) ===<br />
[https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable Kubuntu CI Unstable] daily builds of KDE Git master, also updated every time Kubuntu packaging is updated. This is the closest you can get to the tip of development. Also unfortunately the most unreliable as things break on a daily basis.<br />
<br />
To use this run:<br />
<pre><br />
sudo add-apt-repository ppa:kubuntu-ppa/next<br />
sudo add-apt-repository ppa:kubuntu-ci/unstable<br />
sudo apt update<br />
sudo apt install kubuntu-plasma5-desktop <br />
sudo apt dist-upgrade<br />
</pre><br />
<br />
=== Package Build Reports ===<br />
[http://kci.pangea.pub/ Kubuntu CI Jenkins] has the output from the builds along with their status, useful for packagers and to catch compiler problems that are not caught by KDE CI such as symbol changes.<br />
<br />
=== Kubuntu CI Unstable Weekly ISO Installable Images ===<br />
<br />
[http://files.kde.org/snapshots/ Kubuntu CI Weekly ISO Installable Images] use the packages from Kubuntu CI Unstable Weekly to give you an installable image with packages made from KDE Git. These images have been tested manually as well as with automated checks. Download '''unstable-i386-latest.iso'''. They replace the Neon5 weekly images.</div>Mr. Andersonhttps://community.kde.org/index.php?title=Schedules/Applications/14.12_Release_Schedule&diff=47846Schedules/Applications/14.12 Release Schedule2014-09-13T11:50:10Z<p>Mr. Anderson: s/2014/2015/g, s/2013/2014/g</p>
<hr />
<div>THIS IS WORK IN PROGRESS<br />
<br />
All deadlines are due 23:59 UTC, but if you need a few more hours, notify someone from the release team.<br />
<br />
You can also add http://www.kde.org/releaseschedule.ics as remote calendar to korganizer so you always have the release schedule near you.<br />
<br />
=== Wednesday, October 29, 2014: KDE Applications 14.12 Message Freeze ===<br />
All translated messages (GUI strings) are frozen on this date. Only previously untranslated strings or clear errors in strings can be fixed. No major new strings changes should be done. You cannot add new strings, if you really need one ask kde-i18n-doc for an exception. It is ok to remove strings.<br />
<br />
=== Wednesday, October 29, 2014: KDE Applications 14.12 API Freeze ===<br />
To allow the bindings people to have proper time to do their work in preparation to the final release, the API should now be fixed. Changing API is allowed, but commits have to be cc'ed to the kde-bindings mailinglist. This is including older APIs and newly introduced libraries/APIs.<br />
<br />
=== Wednesday, October 29, 2014: KDE Applications 14.12 Dependency Freeze ===<br />
From this moment on it is not allowed to add new dependencies or bump dependencies versions. It is possible to get an exception for this. Post the patch to reviewboard and add the release-team as reviewer. We will check if the dependency is needed and is available on all platforms.<br />
<br />
In other words: If you have a feature that requires a new dependency or a version of a dependency that is higher than currently checked for in the build system, you need to have committed this change before this date.<br />
<br />
=== Wednesday, October 29, 2014: KDE Applications 14.12 Feature Freeze ===<br />
Trunk is frozen for all feature commits. Only bug fixes are allowed.<br />
<br />
=== Wednesday, October 29, 2014: KDE Applications 14.12 Artwork and Bindings Freeze ===<br />
All artwork is frozen on this date. No new artwork should be added. Existing artwork can continue to be tweaked and fixed.<br />
<br />
No new additions to the language bindings, except optional bindings as permitting by the kde-bindings team.<br />
<br />
=== Wednesday, November 5, 2014: KDE Applications 14.12 Beta 1 Tagging and Release ===<br />
Beta is tagged from trunk. As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released<br />
<br />
=== Wednesday, November 12, 2014: KDE Applications 14.12 Beta 2 Tagging and Release ===<br />
Beta is tagged from trunk. As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released<br />
<br />
=== Wednesday, November 19, 2014: KDE Applications 14.12 Documentation Freeze ===<br />
No more changes to documentation or handbooks after this date. For typos, spelling and simple grammar changes you have to mail kde-i18n-doc for approval.<br />
<br />
=== Wednesday, November 19, 2014: KDE Applications 14.12 Beta 3 Tagging and Release ===<br />
Beta is tagged from trunk. As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released<br />
<br />
=== Wednesday, November 26, 2014: KDE Applications 14.12 Release Candidate Tagging and Release ===<br />
The release candidate is tagged from the branch. As soon as the tarballs have been confirmed to build and the Release Team thinks they meet enough quality it will be released<br />
<br />
=== Wednesday, December 10, 2014: KDE Applications 14.12 Final Tag ===<br />
The branch is frozen for final release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. <br />
<br />
=== Wednesday, December 17, 2014: KDE Applications 14.12 Release ===<br />
Final release is released for general consumption.<br />
<br />
=== Thursday, January 8, 2015: KDE Applications 14.12.1 tagging ===<br />
Minor release is tagged and made available to the packagers.<br />
<br />
=== Tuesday, January 13 2015: KDE Applications 14.12.1 release ===<br />
Minor release is released to the public.<br />
<br />
=== Thursday, January 29, 2015: KDE Applications 14.12.2 tagging ===<br />
Minor release is tagged and made available to the packagers.<br />
<br />
=== Tuesday, February 3, 2015: KDE Applications 14.12.2 release ===<br />
Minor release is released to the public.<br />
<br />
=== Thursday, February 26, 2015: KDE Applications 14.12.3 tagging ===<br />
Minor release is tagged and made available to the packagers.<br />
<br />
=== Tuesday, March 3, 2015: KDE Applications 14.12.3 release ===<br />
Minor release is released to the public.</div>Mr. Andersonhttps://community.kde.org/index.php?title=Calligra/Building/Building_Calligra&diff=12330Calligra/Building/Building Calligra2011-05-21T00:10:27Z<p>Mr. Anderson: /* Get the source code for the development version */ update repository link</p>
<hr />
<div>These instructions are for Unix and similar operating systems.<br />
<br />
See also:<br />
*[[../Nightly Builds/]]<br />
*[[../Developing With KDevelop/]]<br />
*[[../Developing With QtCreator/]]<br />
*[http://techbase.kde.org/Projects/KDE_on_Windows Pages about compiling KDE software for Windows]<br />
*[http://techbase.kde.org/Getting_Started/Build/KDE4/Mac_OS_X Pages about compiling KDE software for Mac OS X]<br />
*[https://wiki.kubuntu.org/CompilingKoffice2 Community HOWTO dedicated to building for Kubuntu]<br />
*[http://community.kde.org/Sysadmin/GitKdeOrgManual kde's git infrastructure manual]<br />
*[http://techbase.kde.org/Development/Tutorials/Git KDE and Git for developers]<br />
*[http://git.or.cz/course/svn.html git crash course]<br />
*[http://forum.kde.org/viewtopic.php?f=139&t=92880 script for building Calligra (build only krita by default, but easilly configurable)]<br />
<br />
<br />
Note: if you want to build FreOffice using the Nokia Qt SDK, please check out the [http://techbase.kde.org/index.php?title=User:Kumarafaque&oldid=54703 build instructions on techbase].<br />
<br />
<br />
= Preparation =<br />
{{Warning|First, to avoid conflicting copies of software, '''make sure you do not have other copy of Calligra or Calligra software''' either installed through the package manager of your distribution or installed in any other way. Calligra and Calligra are mutually exclusive!}}<br />
<br />
== Recommended setup ==<br />
Here is recommendation of a directory structure:<br />
;$HOME/kde4/src/:source code<br />
;$HOME/kde4/build/calligra:directory that Calligra will be built in<br />
;$HOME/kde4/inst:directory that Calligra will be installed in<br />
<br />
The ''build'' directory is needed because you cannot (or should not) build Calligra inside the source directory; the source and build directory have to be separated. <br />
<br />
'''Advantages of this setup:'''<br />
*It is possible to have different builds (e.g. with different options out of the same source code)<br />
*[http://techbase.kde.org/Getting_Started/Increased_Productivity_in_KDE4_with_Scripts David Faure's scripts] can be used to make development easier. With those scripts "make" can be typed in the source directory and building will happen in the right (build) directory automatically. <br />
<br />
Also, check the [http://techbase.kde.org/Getting_Started/Build/KDE4 Techbase instructions on setting up a build environment]. That contains some useful scripts and functions.<br />
<br />
== Geting the source code ==<br />
There are two options: to get the source code for the latest stable version or for the for the development version. The later option is needed to test, check and give feedback about features that is in development and have not been released yet. If unsure pick the stable version.<br />
<br />
=== Geting the source code for the latest stable version ===<br />
<br />
The latest stable Calligra version is '''{{Calligra/Stable}}'''.<br />
* Visit download.kde.org for the latest source code: [http://download.kde.org/download.php?url=stable/calligra-{{Calligra/Stable}}/calligra-{{Calligra/Stable}}.tar.bz2 calligra-{{Calligra/Stable}}.tar.bz2]<br />
* Check release notes on [http://www.calligra-suite.org/ calligra.org]<br />
<br />
<br />
=== Get the source code for the development version ===<br />
<br />
{{Warning|You cannot convert your KOffice SVN checkout to a Calligra git checkout. You will need to get the Calligra source code using git and manually apply your changes again.}}<br />
<br />
The latest development version of Calligra is '''{{Calligra/Unstable}}''' {{Calligra/Stage}}; developers always refer to it as to '''Master'''. Once tested and released, it will become the new current stable version {{Calligra/UnstableBranch}}.<br />
<br />
XXX: Here we should explain local branches, staging and always-release-ready Master, if we have that setup. XXX<br />
<br />
*'''Option 1: directly from git'''<br />
<br />
To retrieve the source code from Git you have to use the following setup:<br />
<br />
Add the following text to your ~/.gitconfig: <br />
<br />
[url "git://anongit.kde.org/"]<br />
insteadOf = kde:<br />
[url "ssh://git@git.kde.org/"]<br />
pushInsteadOf = kde:<br />
<br />
Then execute<br />
<br />
$ git clone kde:calligra<br />
<br />
By using the kde: prefix, read access will automatically happen over Git, and authenticated SSH is only required for pushes.<br />
<br />
Note that pushing your changes will only work if you have a KDE developer identity (https://identity.kde.org/register.php).<br />
<br />
The $HOME/kde4/src/calligra directory will be created regardless of the way how the source code has been downloaded.<br />
<br />
*'''Option 2: download a repository tarball'''<br />
<br />
Go to https://projects.kde.org/projects/calligra/repository. Press the "Tarball" button. Copy the url text and paste it on your command line. It will look like:<br />
<br />
wget -c http://anongit.kde.org/calligra/calligra-latest.tar.gz<br />
<br />
Unpack and cd into directory, then run <br />
<br />
$ ./initrepo.sh<br />
<br />
From now on, you can run<br />
<br />
$ git pull<br />
<br />
to update, or<br />
<br />
$ git rebase origin/master<br />
<br />
if you have local changes<br />
<br />
<br />
*'''Option 3: if beta or rc version was released''', the source code for the latest beta can be found on KDE's ftp [ftp://ftp.kde.org/pub/kde/unstable/calligra-latest/ calligra-latest]. Uncompress the code so that $HOME/kde4/src/calligra is created.<br />
<br />
= Build requirements =<br />
This section provides information about '''hard''' (required) and '''optional''' software packages needed to build the Calligra software.<br />
<br />
== Hard dependencies ==<br />
<br />
{{Note|'''A note for developers:''' to add (or remove) a hard dependency, an explanation of the reason, and possibly a discussion must be posted in advance on calligra-devel@kde.org. The new dependency need to be packaged in the most widely used distributions (Debian, Fedora Core, OpenSuSE, (K)ubuntu). First try to make your new feature optional.}}<br />
<br />
Following are the general must-have dependencies for Calligra:<br />
* Qt 4.6.0<br />
* kdelibs, the minimal requirement is currently 4.3.0. But Calligra should build fine with either kdelibs from svn (see [http://techbase.kde.org/Getting_Started/Build/KDE4 techbase] for an explanation on how to compile kdelibs from svn), or any 4.3, 4.4 or 4.5 release packaged in your distribution (4.4.x is recommended) Parts of Calligra build with the Mobile Frameworks Profile of the KDE platform (kword, kspread, kpresenter, krita)<br />
* kdebase/runtime 4.3 (4.4.x is recommended)<br />
* kdepimlibs 4.3 (4.4.x is recommended)<br />
* cmake 2.6.2<br />
* lcms 1.18<br />
<br />
For KSpread:<br />
* libeigen 2.0<br />
<br />
For Krita:<br />
* libeigen 2.0<br />
* libexiv2 >= 0.16<br />
* libqimageblitz<br />
<br />
For KPresenter:<br />
<br />
* boost<br />
<br />
For Kexi:<br />
* sqlite and sqlite-devel packages (package names can differ on various distributions), version >= 3.6.16<br />
<br />
== Optional dependencies ==<br />
<br />
All optional dependencies are logged at the end of the cmake run, so it is easy to figure out what is missing. The buildsystem also reports what component will bot be built because given missing dependency.<br />
<br />
== Simplified installation of dependencies on various distributions ==<br />
{{Note|Most distribution don't ship calligra yet, so you may replace it by "koffice" or "koffice2" in those command lines}}<br />
*'''deb-based distributions (Debian, Ubuntu...):''' All the dependencies used for the packages can be installed by running<br />
apt-get build-dep {packagename}<br />
for instance on Ubuntu:<br />
sudo apt-get build-dep calligra<br />
<br />
*'''OpenSuSE:''' All the dependencies used for building Calligra can be installed by running:<br />
zypper si -d calligra<br />
<br />
*'''Fedora:''' All the dependencies used for building Calligra can be installed by running:<br />
yum-builddep calligra<br />
<br />
*'''ArchLinux:''' All the dependencies used for building Calligra can be installed by running:<br />
sudo pacman -S docbook-xml docbook-xsl exiv2 glew graphicsmagick gsl kdebase-runtime kdepimlibs lcms libwpd poppler-qt pstoedit qca qimageblitz shared-mime-info wv2 xdg-utils<br />
<br />
= Build Calligra =<br />
{{Note|It is '''not''' possible to build Calligra in the source directory. Set up your directories as described in the [[#Recommended_setup|Recommended setup]] section above}}<br />
<br />
Type:<br />
mkdir -p $HOME/kde4/build/calligra<br />
mkdir -p $HOME/kde4/inst<br />
cd $HOME/kde4/build/calligra<br />
cmake -DCMAKE_INSTALL_PREFIX=$HOME/kde4/inst $HOME/kde4/src/calligra -DCMAKE_BUILD_TYPE=RelWithDebInfo<br />
<br />
''cmakekde'' tool can be used as explained on [http://techbase.kde.org/Getting_Started/Build/KDE4 the build instructions for KDE4].<br />
<br />
Then type:<br />
make<br />
<br />
Note that on dual-core machines compilation can be '''greatly speed up''' with the -j parameter of the ''make'' program, for example for dual-core:<br />
make -j4<br />
and for quad-core:<br />
make -j8<br />
<br />
Then type this command to install the software:<br />
make install<br />
<br />
'''Debugging options.''' Instead of setting CMAKE_BUILD_TYPE to "RelWithDebInfo" for cmake which gives an optimized Calligra with debug information, useful for bug reporting, one can set CMAKE_BUILD_TYPE to "Debug" to get a slower Calligra but with even more interesting debuggong (backtrace) information. For this replace ''-DCMAKE_BUILD_TYPE=RelWithDebInfo'' in the above cmake command with ''-DCMAKE_BUILD_TYPE=Debug''.<br />
<br />
Please follow the [[Building/Building_Calligra#Running_Calligra_applications|Running Calligra Applications]] instructions before trying to run an application.<br />
<br />
= Updating the already built software =<br />
If the source code has been checked out Subversion from trunk or a branch, it is possible to update the source code with newly added changes and build again. Usually only changing parts will be built, so this operation would be faster than building the source code from scratch.<br />
<br />
Type:<br />
cd $HOME/kde4/src/calligra<br />
git pull<br />
cd $HOME/kde4/build/calligra<br />
make<br />
make install<br />
<br />
{{Note|''make -j4'' or ''make -j8'' can be used instead of ''make'' to speedup the build on multicore machines}}<br />
<br />
{{Note|The above recipe will not work if the source code has not been obtained from Subversion}}<br />
<br />
= Build only selected applications from Calligra =<br />
CMake comes with a command-line tool ''ccmake'' that lets you configure build options. You can use it after executing cmake and before executing make. To use it, go to the build directory and issue the following commands:<br />
cd $HOME/kde4/build/calligra<br />
ccmake .<br />
<br />
For applications that you do '''not''' want to compile, set the corresponding BUILD_{application} variable to "off", replacing {application} by the app's name. For instance, setting ''BUILD_krita'' to ''off'' will prevent Krita from being built.<br />
<br />
Alternatively you can run "-DBUILD_{application}=off" from the cmake command line.<br />
<br />
= Running Calligra applications =<br />
There are two options to make the Calligra applications available for running.<br />
<br />
*'''Option 1: Being able to run Calligra applications from the command line.''' If you have installed Calligra in a different prefix than KDElibs (which was recommended in this document), you may want to set the following environment variable: <br />
<br />
export KDEDIRS=/path/to/install:$KDEDIRS<br />
export PATH=/path/to/install/bin:$PATH<br />
export KDEHOME=/path/to/a/config/dir<br />
<br />
And then you need to execute:<br />
kbuildsycoca4<br />
<br />
For example for the recommended directory structure:<br />
export KDEDIRS=$HOME/kde4/inst:$KDEDIRS<br />
export PATH=$HOME/kde4/inst/bin:$PATH<br />
export KDEHOME=$HOME/kde4/.kde<br />
<br />
It is important to set KDEHOME to a directory different of $HOME/.kde, and if the directory does not exist, it will be created automatically.<br />
<br />
*'''Option 2: Being able to run Calligra applications from the menu or by clicking on desktop icons.''' Instead of using ''KDEDIRS'', you can add these lines to $HOME/.kde/share/config/kdeglobals file using text editor:<br />
<br />
[Directories]<br />
prefixes=/path/to/install<br />
<br />
And then you need to execute:<br />
kbuildsycoca4<br />
<br />
The advantage of this is that KDE4 will always look for the services where Calligra is installed. <br />
For example for the recommended directory structure:<br />
<br />
[Directories]<br />
prefixes=$HOME/kde4/inst.<br />
<br />
= Executing unit tests =<br />
To be able to execute unit tests, you need to explicitely enable them in the build configuration. To do so, set the KDE4_BUILD_TESTS variable to "ON", either by issuing the command <code>cmake -DKDE4_BUILD_TESTS=ON</code>, or by running <code>ccmake .</code>. Both commands must be executed in the build directory.<br />
<br />
You can then run the test by executing:<br />
<br />
make test<br />
<br />
or individually in the tests directories.<br />
<br />
It is recommended to execute<br />
<br />
make install<br />
<br />
before running tests.<br />
<br />
= CMake Build Options =<br />
When you enter your build directory, you can type "ccmake ." to see many build options, e.g. you can turn off compilation of apps you don't want - you can save time when compiling.<br />
<br />
Here is list for Krita related options:<br />
* HAVE_MEMORY_LEAK_TRACKER [On/Off] - You can turn on compilation of the tool in krita which detects memory leak. If you want to help debug Krita memory usage, it is useful. Otherwise you just slow down your Krita.<br />
* HAVE_BACKTRACE_SUPPORT [On/Off] - It is related to the memory leak tool. If you activate, you will be able to see code path which leads to memory leak.<br />
<br />
= Resources =<br />
*[[DeveloperInfo|Useful hints for who wants to hack on Calligra]]<br />
*[http://wiki.opengtl.org/libraries:developers-resources opengtl debugging, or turning it off]<br />
*[http://winkde.org/pub/kde/ports/win32/dashboard/ Status of Calligra build on Windows (msvc 2008, mingw)]<br />
<br />
= Possible issues =<br />
<br />
If you get errors when running an application like:<br />
<br />
krita(8565)/calligra (lib komain) KoPluginLoader::load: Loading plugin "Animation Tool" failed, <br />
"Cannot load library /home/michael/kde4/inst/lib/kde4/kpresentertoolanimation.so: <br />
(/home/michael/kde4/inst/lib/libkopageapp.so.7: undefined symbol:<br />
_ZN28KoShapeContainerDefaultModel3addEP7KoShape)" ( 1 ) <br />
<br />
or crashes when starting an application, then you very likely have a version of Calligra installed through your package manager. '''As emphasized earlier in this document, you can only have one version of Calligra, and you should uninstall your packaged Calligra'''.</div>Mr. Andersonhttps://community.kde.org/index.php?title=Schedules/KDE4/4.1_Release_Schedule&diff=49379Schedules/KDE4/4.1 Release Schedule2008-05-13T00:34:18Z<p>Mr. Anderson: </p>
<hr />
<div>KDE 4.1 is the first feature release for KDE 4. All dates given here are subject to revision, but we will try our best to stick to them if possible. The KDE Release Team is acting as the coordinator for the 4.1 release.<br />
<br />
== KDE 4.1 ==<br />
<br />
<br />
=== April 20th, 2008: Soft Feature Freeze ===<br />
Trunk is frozen for feature commits that are not listed in the [[Schedules/KDE4/4.1_Feature_Plan | planned feature document]]. Only bugfixes and the code implementing the listed features are to be committed. The feature list also closes today.<br />
<br />
Features not already finished or listed on the planned features page will have to wait until KDE 4.2.<br />
<br />
=== April 22nd, 2008: Tag KDE 4.1 Alpha 1 ===<br />
Trunk is frozen for Alpha 1 release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.<br />
<br />
Alpha 1 will be source only - without translations.<br />
<br />
=== April 29th, 2008: Release KDE 4.1 Alpha 1 ===<br />
Alpha 1 becomes available for general consumption.<br />
<br />
=== May 19th, 2008: Hard Feature Freeze ===<br />
Trunk is frozen for all feature commits, even those listed in the planned feature document. Only bug fixes are allowed. Binary compatibility for new API is not yet required.<br />
<br />
=== May 20th, 2008: Message Freeze. ===<br />
All translated messages are frozen on this date. Only previously untranslated strings or clear errors in strings can be fixed. <b>No major new strings changes should be done.</b> It is ok to remove strings.<br />
<br />
=== May 20th, 2008: Tag KDE 4.1 Beta 1 ===<br />
Trunk is frozen for Beta 1 release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. The usual beta rules apply as soon as the Beta tarballs have been generated. <br />
<br />
=== May 27th, 2008: Release KDE 4.1 Beta 1 ===<br />
Beta 1 becomes available for general consumption.<br />
<br />
=== June 17th, 2008: Tag KDE 4.1 Beta 2 ===<br />
Trunk is frozen for Beta 2 release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.<br />
<br />
=== June 24th, 2008: Release KDE 4.1 Beta 2 ===<br />
Beta 2 becomes available for general consumption.<br />
<br />
=== July 8th, 2008: Artwork Freeze ===<br />
All artwork is frozen on this date. <b>No new artwork should be added.</b> Existing artwork can continue to be tweaked and fixed. <br />
<br />
=== July 8th, 2008: Tag KDE 4.1 RC 1 ===<br />
Trunk is frozen for RC 1 release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.<br />
<br />
=== July 15th, 2008: Release KDE 4.1 RC 1 ===<br />
RC 1 becomes available for general consumption. Incoming bugs will be reviewed for their severity. Additional release candidates will be created as needed.<br />
<br />
=== July 22nd, 2008: Tag KDE 4.1 ===<br />
Assuming there is only one release candidate, trunk is frozen for KDE 4.1 tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.<br />
<br />
=== July 29th, 2008: Release KDE 4.1 ===<br />
KDE 4.1 becomes available for general consumption.</div>Mr. Anderson