From Develop

Jump to: navigation, search


These are relevant for Miro 3.1 or later! Prior to Miro 3.1, you should look at GTKX11BuildDocs instead.


Installing prerequisites

Miro has a set of build requirements and runtime requirements.

Build requirements:

Runtime requirements:

If you see other requirements that aren't listed, fill them in!

Supported systems

As of April 15, 2010, we have helper scripts in the git repository and source tarballs that install pre-requisite packages for some systems. Since those scripts are in version control along-side the code, use them before using below recipes.

Scripts are located in tv/linux/helperscripts/.

You can see these script for git master at:

Please help us write scripts for distribution/version systems that aren't yet covered!

Please help us maintain the ones that are.

Get up and running quickstart

  1. Install git.
  2. Do: git clone git://
  3. Do: cd miro/tv/linux/helperscripts/
  4. Run the helper script for your system. If your system doesn't have a helperscript, then look at the existing ones and install the dependencies manually. We'd love to add new helperscripts, so if you write a new one, please send it to us!
  5. Do: cd .. (this move up a directory so you're in miro/tv/linux/
  6. Run: ./

Running Miro from source

We have a script that compiles and runs Miro in place and does not install the program on your system. It does use the system Miro settings and does use the system Miro database.


If the source you're using has a database schema that is after the schema of the database you're using, then the database will be upgraded. If you want to go back, you have to manually restore the backup from ~/.miro/dbbackups/.

To run Miro from source:

cd linux

or if you're running from a git checkout:

cd tv/linux

There are two ways to run Miro in a test sandbox.

1. Set the "HOME" environment variable to switch where Miro saves database and other files:

mkdir /tmp/foo
HOME=/tmp/foo ./

This has the problem that it doesn't work if you're using KDE (it causes problems) and it uses your "production" Miro configuration.

2. Run Miro using the "--home" and "--gconf-name" arguments:

mkdir /tmp/foo --home=/tmp/foo --gconf-name=mirotest

This stores configuration in a different place and uses a different home without affecting the process environment.

See the README file in tv/linux/ for more information on running Miro.

Ubuntu packages

We maintain and build packages for Miro for the two most recent Ubuntu versions. Our build scripts are on git in the miro-packaging repository at .

We distribute our packages in the miro-releases PPA. More details at .

Related URLs

Personal tools