[https://launchpad.net/project-neon Project Neon] is a nightly build of the latest KDE trunk for Ubuntu. It is an easy way for new contributors to KDE to get started without having to download and build the entire KDE source code tree. Additionally, dependencies are automatically handled and updated. This is suitable for new developers, translators, usability designers, documenters, promoters, bug triagers, etc. This process makes the steps detailed on [[Getting_Started/Build|this page]].

−

{{Note | Project Neon can help you with builds current as of --FIXME--}}

+

However, for developers, it may at some point become necessary to build more components from source code as you become more involved in the project. The [[Getting_Started/Build/kdesrc-build|kdesrc-build]] script is an easy way to build all or parts of KDE from its source code repositories.

−

+

−

{{Warning | This Page is currently being reworked for the new Project Neon archive - Please disregard the content as long as this note is here!}}

+

−

+

−

[https://edge.launchpad.net/project-neon Project Neon] is a nightly build of the latest KDE trunk. It is an easy way for new contributors to KDE to get started without having to build the entire KDE-SVN tree and maintain the checkout. Additionally, dependencies are automatically handled and updated. This is suitable for new developers, translators, usability designers, documenters, promoters, bug triagers etc. This process makes the steps detailed on [[Getting_Started/Build/KDE4|this page]], including changes to your [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]] unnecessary.

+

−

+

−

However, for developers, it may at some point become necessary to build more components from SVN as you become more involved in the project. The [[Getting_Started/Build/kdesvn-build|kdesrc-build]] script is an easy way to build all or parts of KDE SVN.

+

== Requirements ==

== Requirements ==

−

Project neon always requires the latest stable Kubuntu release or development release. Previous versions of Kubuntu are not supported. It is possible to port Project Neon to other distributions, though there are currently no maintainers for other distributions working on the project. OpenSuse provides their own weekly build of KDE trunk. Find instructions on how to use it [[Getting Started/Using OpenSuse KDE unstable packages for development|here]].

+

Project Neon always requires either the latest stable Kubuntu release or the development release. Previous versions of Kubuntu are not supported.

== Installing Project Neon ==

== Installing Project Neon ==

Line 17:

Line 11:

To use Project Neon, add the following PPA (Personal Package Archive) to your <tt>sources.list</tt> using your preferred method:

To use Project Neon, add the following PPA (Personal Package Archive) to your <tt>sources.list</tt> using your preferred method:

After that, you can simply install the nightly package of whichever modules you want to work on. The Packages are named project-neon-<git/svn module name>.

+

Now you need to synchronize the package index files. Run

−

You can install all of the packages or just the ones you are interested in, depending on what you want to use them for. For example if you want to install the KDE Workspace with the extra plasmoids, you would install the <tt>project-neon-kdeplasma-addons</tt> and <tt>project-neon-session</tt> so you get KDM support for Project Neon.

+

<syntaxhighlight lang="bash">

+

sudo apt-get update

+

</syntaxhighlight>

−

<code bash>

+

After that, you can simply install the nightly package of whichever modules you want to work on. The packages are named project-neon-<git/svn module name>. The packages are installed in /opt/project-neon/ and won't affect your stable KDE install.

You can install all of the packages or just the ones you are interested in, depending on what you want to use them for.

+

+

=== Using Project Neon version of KDE Workspace ===

+

+

To use Project Neon version of KDE Workspace, install the <tt>project-neon-base</tt> package. You can then log out, select the "Project Neon" session in KDM session list and log in.

+

+

<syntaxhighlight lang="bash">

+

sudo apt-get install project-neon-base

+

</syntaxhighlight>

+

+

You can also install other KDE Workspace goodies, such as extra plasmoids, with:

+

+

<syntaxhighlight lang="bash">

+

sudo apt-get install project-neon-kdeplasma-addons

+

</syntaxhighlight>

+

+

=== Testing individual applications ===

If you are only interested in application development in another module, you can install just the module package.

If you are only interested in application development in another module, you can install just the module package.

−

<code bash>

+

First install <tt>project-neon-utils</tt>. This package contains a number of utilities among which <tt>neon-env</tt>, which is needed to run Project Neon applications:

−

sudo apt-get install project-neon-kdepim

+

−

</code>

+

−

That command will also install the <tt>kdelibs</tt>, <tt>kdepimlibs</tt> and other dependencies too. In your regular (stable) KDE session you can then run the nightly version of your chosen application after setting up the environment.

+

<syntaxhighlight lang="bash">

+

sudo apt-get install project-neon-utils

+

</syntaxhighlight>

−

<code bash>

+

You can then install the package for the module you are interested in. For example to test the latest version of kdepim applications:

−

. /opt/project-neon/share/project-neon/environment.rc

+

−

kmail

+

−

</code>

+

−

Instead of sourcing the settings by hand every time, you could add this to your .bashrc:

+

<syntaxhighlight lang="bash">

+

sudo apt-get install project-neon-kdepim

+

</syntaxhighlight>

−

<code>

+

That command will also install the <tt>kdelibs</tt>, <tt>kdepimlibs</tt> and other dependencies too. In your regular (stable) KDE session you can now set up Project Neon environment and run the nightly version of your chosen application.

−

function switchtonightly {

+

−

. /opt/project-neon/share/project-neon/environment.rc

+

−

}

+

−

</code>

+

−

You'll need to close the terminal session for the settings to be undone.

+

<syntaxhighlight lang="bash">

+

neon-env

+

kmail

+

</syntaxhighlight>

+

<tt>neon-env</tt> will setup the environment and start a subshell from which you can work with your project neon installation.

This will correctly use the nightly version of libraries instead of using the stable versions, so no other changes are necessary to your library path etc.

This will correctly use the nightly version of libraries instead of using the stable versions, so no other changes are necessary to your library path etc.

+

You'll need to close the terminal session for the settings to be undone.

Note that settings for applications that you run from project neon do not conflict with your regular application settings and data. <tt>.project-neon-kde/</tt> is used instead of <tt>.kde/</tt>

Note that settings for applications that you run from project neon do not conflict with your regular application settings and data. <tt>.project-neon-kde/</tt> is used instead of <tt>.kde/</tt>

−

== Using Project Neon for development ==

+

=== Installing everything ===

−

If you are joining one of the development teams in KDE, you will need a real SVN/GIT checkout in order to contribute your code back to the project and create patches easily.

+

If you want to install all packages that are provided by Project Neon in one go, you can use the <tt>project-neon-all</tt> package which will install all provided packages. To install all debugging symbols (Warning: takes a lot of disk space) <tt>project-neon-all-dbg</tt> can be used.

+

+

== Using Project Neon for development ==

−

Some extra tools are provided for this purpose in the package <tt>project-neon-utils</tt>:

+

If you are joining one of the development teams in KDE, you will need a real SVN/GIT checkout in order to contribute your code back to the project and create patches easily. If you only code for KDE every now and then, Project Neon provides some extra tools for this purpose in the package <tt>project-neon-utils</tt>:

* <tt>neon-cmake</tt> - cmake wrapper with neon environment settings for cmake, same synopsis as cmake and passes arguments to cmake

+

* <tt>neonmake</tt> - convenience script which will create a build folder, configure the source, build it and install it in /opt/project-neon/ so you can test your changes.

+

* <tt>neon-clean</tt> - script that resets any changes you made to /opt/project-neon after installing the packages. Since this script reinstalls the packages it might require a working internet connection.

+

* <tt>neonbuild</tt> - pbuilder/pdebuild wrapper to rebuild a neon package in a chroot. Takes the same options as pbuilder. If no pbuilder action is given pdebuild is run instead.

−

<tt>neon-cmake</tt>:

+

=== Options for cmake/make ===

−

cmake wrapper with neon environment settings for cmake, same synopsis as cmake and passes arguments to cmake

+

You can change the cmake and make options used by setting these variables in ~/.neonrc:

−

<tt>neonmake</tt>:

+

* <tt>NEON_CMAKE_OPTS=""</tt> - Here you can add additional cmake options that should be used together with the default neon options.

−

convenience script which will create a build folder, configure the source, build it and install it in /opt/project-neon/ so you can test your changes.

+

* <tt>NEON_CMAKE_OVERRIDE=""</tt> - If you set this variable cmake will ignore the default neon options and only use the ones in NEON_CMAKE_OVERRIDE.

+

* <tt>NEON_MAKE_OVERRIDE=""</tt> - If you set this variable make in neonmake will only use your options. By default make uses '-j CPUs+1'

−

<tt>neon-clean</tt>:

+

=== Debugging symbols ===

−

This script will reset all changes you did to /opt/project-neon after installing the packages. Since this script reinstalls the packages it might require a working internet connection.

+

The debugging symbols for every package are in its corresponding <code>-dbg</code> package, so to install the debugging symbols for kdelibs you can use

−

+

<syntaxhighlight lang="bash">

−

Debugging Symbols:

+

−

The debugging symbols for every package are in it's corresponding -dbg package, so to install the debugging symbols for kdelibs you can use

+

−

<code bash>

+

sudo apt-get install project-neon-kdelibs-dbg

sudo apt-get install project-neon-kdelibs-dbg

−

</code>

+

</syntaxhighlight>

−

If you are already using a nightly package of the module you want to develop for, you should remove that, and checkout the development version. For example:

+

If you are already using a nightly package of the module you want to develop for, you should remove that and checkout the development version. For example:

−

<code bash>

+

<pre>

# Remove the packaged nightly version

# Remove the packaged nightly version

sudo apt-get purge project-neon-kdepim

sudo apt-get purge project-neon-kdepim

Line 107:

Line 122:

git clone git://anongit.kde.org/kdepim

git clone git://anongit.kde.org/kdepim

cd kdepim

cd kdepim

+

# Set up neon environment

+

neon-env

# Shortcut provided by Project Neon to make the module

# Shortcut provided by Project Neon to make the module

# and install it to the prefix /opt/project-neon/

# and install it to the prefix /opt/project-neon/

neonmake

neonmake

−

</code>

+

</pre>

Note that you should usually checkout a module from KDE, not an application. Most modules contain libraries shared within the module and which are necessary to build the applications in the module.

Note that you should usually checkout a module from KDE, not an application. Most modules contain libraries shared within the module and which are necessary to build the applications in the module.

+

Also note that when using apt-get build-dep it will always get all build-depends, so watch out that it doesn't install a component you want to build yourself as that would overwrite your changes should you install the packages after installing your build.

−

== Using Project Neon for translation ==

−

-- FIXME: OLD INSTRUCTIONS

+

== Using Project Neon for translation ==

The Project Neon nightly packages include English language strings only. Translated packages are not available. However, if you are translating KDE applications, you can install the translations from KDE SVN in your normal workflow.

The Project Neon nightly packages include English language strings only. Translated packages are not available. However, if you are translating KDE applications, you can install the translations from KDE SVN in your normal workflow.

−

<code bash>

+

<syntaxhighlight lang="bash">

cd ~

cd ~

cd Translations

cd Translations

Line 131:

Line 148:

# Get the German translations

# Get the German translations

svn up de

svn up de

−

# Generate the build files for the German language pack

+

# Generate the build files for the German language pack - if you get a message

+

# that revpath couldn't be found you need to install the xutils-dev package

./scripts/autogen.sh de

./scripts/autogen.sh de

cd de

cd de

+

neon-env

neonmake

neonmake

−

</code>

+

</syntaxhighlight>

After building the translations it is possible to either change the language in system settings, or run applications in another language using the environment variable <tt>KDE_LANG</tt>.

After building the translations it is possible to either change the language in system settings, or run applications in another language using the environment variable <tt>KDE_LANG</tt>.

−

<code bash>

+

<syntaxhighlight lang="bash">

−

switchtonightly

+

switchtonightly # or neon-env

KDE_LANG=de kmail

KDE_LANG=de kmail

−

switchtostable

+

</syntaxhighlight>

−

</code>

+

+

Exit the shell to reset the settings.

== Using Project Neon for documentation ==

== Using Project Neon for documentation ==

Line 159:

Line 179:

Here is a shortcut to get all available modules from the PPA:

Here is a shortcut to get all available modules from the PPA:

−

<code bash>

+

<syntaxhighlight lang="bash">

sudo apt-get install project-neon-all

sudo apt-get install project-neon-all

−

</code>

+

</syntaxhighlight>

The application [http://ariya.blogspot.com/2008/06/creating-fancy-screenshots-with.html screenie] is provided since Kubuntu 8.10 as <tt>screenie-qt</tt>.

The application [http://ariya.blogspot.com/2008/06/creating-fancy-screenshots-with.html screenie] is provided since Kubuntu 8.10 as <tt>screenie-qt</tt>.

−

<code bash>

+

<syntaxhighlight lang="bash">

sudo apt-get install screenie-qt

sudo apt-get install screenie-qt

−

</code>

+

</syntaxhighlight>

+

+

+

== Using Project Neon 5 for Frameworks 5 Development ==

+

+

Project Neon 5 is the codename for the KDE Frameworks 5-based version of Project Neon. It offers regularly updated, precompiled packages for KDE Frameworks 5 ("KF5") libraries, the Plasma components that make up the workspace. These packages are useful to ease the setup of a KF5 environment for developing and porting applications and add-on components. They are also useful in order to get an idea of the state of development.

+

+

Please note the following:

+

* These packages are *NOT* suitable for day-to-day use, they contain major bugs and are just development snapshots

+

* The packages might break at any point, since the packages closely follow the development of KDE Frameworks 5 and Plasma 2

+

* Packages get installed into /opt/project-neon5, they are built to not contaminate your production environment

+

+

=== Installing Project Neon 5 ===

+

+

In order to install Neon5, you have to add the download repository, then you can install the packages.

+

+

Add the Neon5 repository:

+

<syntaxhighlight lang="bash">

+

sudo apt-add-repository ppa:neon/kf5-snapshot-weekly

+

sudo apt-get update

+

</syntaxhighlight>

+

(If you would like more frequent updates, (which also bear the risk of breaking more often!), use "ppa:neon/kf5-snapshot-daily" or "ppa:neon/kf" for the most frequent updates.

+

To install Project Neon 5, issue the command

+

+

<syntaxhighlight lang="bash">

+

sudo apt-get install project-neon5-session project-neon5-utils \

+

project-neon5-konsole

+

</syntaxhighlight>

+

+

=== Running Project Neon 5 ===

+

+

The LightDM login screen will now offer a Project Neon 5 session. You can also run neon5-env, and start plasma-shell from there. By default, we start an xterm with the environment set up. In order to start plasma, run "plasma-shell", for Konsole, start "konsole".

+

If you want to keep your current session running (which is probably most convenient), you can run

+

<syntaxhighlight lang="bash">

+

neon5-env

+

plasma-shell --windowed

+

</syntaxhighlight>

+

to start Plasma in a window (not as desktop or root window).

+

+

=== Status of Builds ===

+

On the following pages, you can find the update status of the different packages:

by mail at <syntaxhighlight lang="text">neon@lists.launchpad.net</syntaxhighlight>

−

</code>

+

−

by mail at

+

−

<code>

+

−

neon@lists.launchpad.net

+

−

</code>

+

or you can ask a question on [https://answers.launchpad.net/project-neon launchpad]

or you can ask a question on [https://answers.launchpad.net/project-neon launchpad]

Revision as of 11:54, 24 September 2013

Project Neon is a nightly build of the latest KDE trunk for Ubuntu. It is an easy way for new contributors to KDE to get started without having to download and build the entire KDE source code tree. Additionally, dependencies are automatically handled and updated. This is suitable for new developers, translators, usability designers, documenters, promoters, bug triagers, etc. This process makes the steps detailed on this page.

However, for developers, it may at some point become necessary to build more components from source code as you become more involved in the project. The kdesrc-build script is an easy way to build all or parts of KDE from its source code repositories.

After that, you can simply install the nightly package of whichever modules you want to work on. The packages are named project-neon-<git/svn module name>. The packages are installed in /opt/project-neon/ and won't affect your stable KDE install.

You can install all of the packages or just the ones you are interested in, depending on what you want to use them for.

Using Project Neon version of KDE Workspace

To use Project Neon version of KDE Workspace, install the project-neon-base package. You can then log out, select the "Project Neon" session in KDM session list and log in.

sudo apt-get install project-neon-base

You can also install other KDE Workspace goodies, such as extra plasmoids, with:

sudo apt-get install project-neon-kdeplasma-addons

Testing individual applications

If you are only interested in application development in another module, you can install just the module package.

First install project-neon-utils. This package contains a number of utilities among which neon-env, which is needed to run Project Neon applications:

sudo apt-get install project-neon-utils

You can then install the package for the module you are interested in. For example to test the latest version of kdepim applications:

sudo apt-get install project-neon-kdepim

That command will also install the kdelibs, kdepimlibs and other dependencies too. In your regular (stable) KDE session you can now set up Project Neon environment and run the nightly version of your chosen application.

neon-env
kmail

neon-env will setup the environment and start a subshell from which you can work with your project neon installation.
This will correctly use the nightly version of libraries instead of using the stable versions, so no other changes are necessary to your library path etc.
You'll need to close the terminal session for the settings to be undone.

Note that settings for applications that you run from project neon do not conflict with your regular application settings and data. .project-neon-kde/ is used instead of .kde/

Installing everything

If you want to install all packages that are provided by Project Neon in one go, you can use the project-neon-all package which will install all provided packages. To install all debugging symbols (Warning: takes a lot of disk space) project-neon-all-dbg can be used.

Using Project Neon for development

If you are joining one of the development teams in KDE, you will need a real SVN/GIT checkout in order to contribute your code back to the project and create patches easily. If you only code for KDE every now and then, Project Neon provides some extra tools for this purpose in the package project-neon-utils:

NOTE: both neon-cmake and neonmake require neon-env to be run first!

neon-env - sets up the necessary environment settings for project neon builds and opens a subshell.

neon-cmake - cmake wrapper with neon environment settings for cmake, same synopsis as cmake and passes arguments to cmake

neonmake - convenience script which will create a build folder, configure the source, build it and install it in /opt/project-neon/ so you can test your changes.

neon-clean - script that resets any changes you made to /opt/project-neon after installing the packages. Since this script reinstalls the packages it might require a working internet connection.

neonbuild - pbuilder/pdebuild wrapper to rebuild a neon package in a chroot. Takes the same options as pbuilder. If no pbuilder action is given pdebuild is run instead.

Options for cmake/make

You can change the cmake and make options used by setting these variables in ~/.neonrc:

NEON_CMAKE_OPTS="" - Here you can add additional cmake options that should be used together with the default neon options.

NEON_CMAKE_OVERRIDE="" - If you set this variable cmake will ignore the default neon options and only use the ones in NEON_CMAKE_OVERRIDE.

NEON_MAKE_OVERRIDE="" - If you set this variable make in neonmake will only use your options. By default make uses '-j CPUs+1'

Debugging symbols

The debugging symbols for every package are in its corresponding -dbg package, so to install the debugging symbols for kdelibs you can use

sudo apt-get install project-neon-kdelibs-dbg

If you are already using a nightly package of the module you want to develop for, you should remove that and checkout the development version. For example:

# Remove the packaged nightly version
sudo apt-get purge project-neon-kdepim
# Add below Project Neon source code repository to sources.list if you didn't use add-apt-repository
deb-src http://ppa.launchpad.net/neon/ppa/ubuntu maverick main
# Get the dependencies for building kdepim
sudo apt-get build-dep project-neon-kdepim
cd ~
# You may choose to do your development in a different folder.
cd Development
# Gets the latest version of the kdepim module.
git clone git://anongit.kde.org/kdepim
cd kdepim
# Set up neon environment
neon-env
# Shortcut provided by Project Neon to make the module
# and install it to the prefix /opt/project-neon/
neonmake

Note that you should usually checkout a module from KDE, not an application. Most modules contain libraries shared within the module and which are necessary to build the applications in the module.

Also note that when using apt-get build-dep it will always get all build-depends, so watch out that it doesn't install a component you want to build yourself as that would overwrite your changes should you install the packages after installing your build.

Using Project Neon for translation

The Project Neon nightly packages include English language strings only. Translated packages are not available. However, if you are translating KDE applications, you can install the translations from KDE SVN in your normal workflow.

cd ~
cd Translations
# The -N switch checks out only the top level directory from svn.
svn co -N svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4
cd l10n-kde4
# scripts necessary to build translations.
svn up scripts
# Get the German translations
svn up de
# Generate the build files for the German language pack - if you get a message# that revpath couldn't be found you need to install the xutils-dev package
./scripts/autogen.sh de
cd de
neon-env
neonmake

After building the translations it is possible to either change the language in system settings, or run applications in another language using the environment variable KDE_LANG.

switchtonightly # or neon-envKDE_LANG=de kmail

Exit the shell to reset the settings.

Using Project Neon for documentation

The Project Neon nightly source packages include the official KDE User Documentation in English.

TODO: How to build user docs from SVN.

Using Project Neon for promotion

If you are creating screenshots or screencasts of the latest version of KDE, project Neon is a simple and fast way of getting a default KDE4 session.

The KDE Promotion team recommends using the default background, theme, icons etc when preparing official promotional materials (unless the feature you are showing is related to configuring KDE artwork). Project Neon uses the default artwork that comes with KDE4, so it is useful for creating promo materials.

Here is a shortcut to get all available modules from the PPA:

sudo apt-get install project-neon-all

The application screenie is provided since Kubuntu 8.10 as screenie-qt.

sudo apt-get install screenie-qt

Using Project Neon 5 for Frameworks 5 Development

Project Neon 5 is the codename for the KDE Frameworks 5-based version of Project Neon. It offers regularly updated, precompiled packages for KDE Frameworks 5 ("KF5") libraries, the Plasma components that make up the workspace. These packages are useful to ease the setup of a KF5 environment for developing and porting applications and add-on components. They are also useful in order to get an idea of the state of development.

Please note the following:

These packages are *NOT* suitable for day-to-day use, they contain major bugs and are just development snapshots

The packages might break at any point, since the packages closely follow the development of KDE Frameworks 5 and Plasma 2

Packages get installed into /opt/project-neon5, they are built to not contaminate your production environment

Installing Project Neon 5

In order to install Neon5, you have to add the download repository, then you can install the packages.

(If you would like more frequent updates, (which also bear the risk of breaking more often!), use "ppa:neon/kf5-snapshot-daily" or "ppa:neon/kf" for the most frequent updates.
To install Project Neon 5, issue the command

Running Project Neon 5

The LightDM login screen will now offer a Project Neon 5 session. You can also run neon5-env, and start plasma-shell from there. By default, we start an xterm with the environment set up. In order to start plasma, run "plasma-shell", for Konsole, start "konsole".
If you want to keep your current session running (which is probably most convenient), you can run

neon5-env
plasma-shell --windowed

to start Plasma in a window (not as desktop or root window).

Status of Builds

On the following pages, you can find the update status of the different packages: