====== Installing the latest Rosegarden source from Subversion ======

**//OBSOLETE//**

These instructions have been superseded by [[dev:Building Rosegarden from Source]].

**//OBSOLETE//**

These instructions show how to install a development version of Rosegarden to use along with the version installed through your distro.  Many of these operations can be performed using graphical utilities, but it is much harder to describe point here click that across many different package managers and desktop environments, so these instructions assume you have some familiarity with the Linux command line.  You will want to go into a terminal using xterm, Konsole, GNOME Terminal or the like to enter these commands.

====== .deb-based Distros (Debian, Ubuntu, Mint and Derivatives) ======

These instructions were tested with Ubuntu 12.04, but the same general process should work on all .deb-based distros, with some minor variations.


===== Install Distro Rosegarden =====

First, install your distro's version of Rosegarden.  It will be out of date, but this is a quick and easy way to pull in all the run-time dependencies that Rosegarden needs.

<code>
  sudo apt-get install rosegarden subversion
</code>

===== Enable Source Repositories =====

Have a look to make sure you have source packages enabled in ''/etc/sources.list''  Lines that start with ''#'' are comments.  Lines that start with ''deb'' are for packages, and lines that start with ''deb-src'' are for source packages.  If you see lines starting with ''#deb-src'' you should remove the ''#'' to enable source repositories.  You should be left with a number of entries that resemble this short sample:

<code>
  deb http://us.archive.ubuntu.com/ubuntu/ precise multiverse
  deb-src http://us.archive.ubuntu.com/ubuntu/ precise multiverse
</code>

If you changed ''sources.list'' then you'll need to do an update to pull in all the new information:

<code>
  sudo apt-get update
</code>

===== Install Build Dependencies =====

Having done that, the next step is to use ''apt-get buid-dep'' to install all the build dependencies.  These rarely change, and the build dependencies for any version of Rosegarden within the last couple of years should be good enough to get the current development source up and running.

<code>
  sudo apt-get build-dep rosegarden
</code>

===== Create Build Directory (Folder) =====

Now you need to decide where you want to build Rosegarden.  Michael always creates a ''~/SVN'' directory for this purpose, but you can put it anywhere you have write and execute permissions, and if you intend to use [[dev:eclipse|Eclipse]] there may be special naming considerations.  I assume you have no better ideas but to follow my lead, so:

<code>
  mkdir ~/SVN
</code>


===== Get the Source =====

With that done you will want to change to your build directory.  I assume ~/SVN; please adjust to suit your local situation, and check out the source:

<code>
  cd ~/SVN
</code>

If you have a SourceForge account and think you might want to contribute patches, check out the source using your SourceForge ID:

<code>
  svn checkout --username=[YOUR USERID] https://svn.code.sf.net/p/rosegarden/code/trunk/rosegarden rosegarden-svn
</code>

Otherwise, just check out a read-only copy:

<code>
  svn checkout svn://svn.code.sf.net/p/rosegarden/code/trunk/rosegarden rosegarden-svn
</code>

===== Run CMake =====

Once you've got the source to ''rosegarden-svn'' under the directory of your choice, move into it, and create a build directory:

<code>
  cd rosegarden-svn
  mkdir build
</code>

Now you need to run CMake:

<code>
  cmake .. -DCMAKE_INSTALL_PREFIX=[PREFIX] [-DCMAKE_BUILD_TYPE=Debug]
</code>

**-DCMAKE_INSTALL_PREFIX** sets the installation prefix, such as /usr
If you set the **-DCMAKE_BUILD_TYPE=Debug** then you will compile a debug build instead of the default release build.

Finally, you are ready to compile:

<code>
  make
</code>

Since you have a system version of Rosegarden installed, there is probably no need to install the one you just compiled.  Run it out of the directory where you just compiled it.  All the install target does is set up system icons and MIME types and so forth, and these change very infrequently.
===== Build and Run =====

Now that you've gotten the source bootstrapped and configured, the next step is to build and run.

<code>
  make && ./rosegarden
</code>

If all went well, your computer bogged down pretty hard for 10-15 minutes, and then your shiny new development version of Rosegarden started up.  You can help us test bug fixes and new features ahead of releases, and we are happy to have the help!  (In the future, you can run with ''./rosegarden'' or you can modify an icon on your desktop to run ''~/SVN/rosegarden-svn/rosegarden'' instead of the usual ''/usr/bin/rosegarden''.)

If something went wrong, don't hesitate to send an email to [[mailto:michael.mcintyre@rosegardenmusic.com|Michael]] and ask for help.  He will be glad to help you along, and will usually reply within three days.

Good luck!

===== Update =====

You will need to keep your development source refreshed, and compile it from time to time.  If a developer fixes a bug or adds a feature, you will need to update in order to obtain the newest code:

<code>
  svn update
  make && ./rosegarden
</code>

Occasionally an update may break things.  Let's just cross that bridge when we come to it.


====== Other Distros ======

Nothing here yet.  I've been using Ubuntu since 2005 or so, and I'm very satisfied with it.  Other people can write the instructions for other distros.  Sorry.

(Note, due to high amounts of spamming, it is necessary to ask Michael for a wiki account.  He will be happy to get one set up for you in a day or two.)