GMPC DEVELOPMENT

Documentation[]

Tasks looking for developers.
Versioning
Why are there no tabs in gmpc (Sort of tabs added in git)
Road map
Debian Packaging
How to write a plugin
Metadata Plugins version 2
Log domains
Todo list for 0.19.1

Development Repository[]

Development of Libmpd,gmpc and Plugins is done in git. Hosted on http://repo.or.cz.

See a list here: http://repo.or.cz/?by_tag=gmpc

Easy checkout script[]

If you want to checkout libmpd,GMPC and all the Plugins you can use the following script http://random.sarine.nl/build_gmpc.sh Run:

bash ./build_gmpc.sh

This will checkout the stable plugin. If you run it again, it will add new plugins and update the existing checkouts.

Building[]

To build gmpc you need to following installed:

* Git
* gcc compiler
* libtool
* intltool Version 0.21 or higher
* glib
* libcurl
* gobject
* gtk+-2.0
* gmodule
* libglade
* gthreads
* libmpd( >=0.20.5 )
* gob 2.0
* valac( 0.9.x )

Tip On a Debian based system, to install all the dependencies use :

# aptitude build-dep gmpc

# aptitude build-dep gmpc-plugins ( optionally, for building plugins )

However you may have to install some packages from source if the version available in your repository is old. I am using Debian squeeze and had to install libmpd from source and valac from the experimental branch( install from source if you do not have apt-pinning set up ).

The basic steps are then:

Make sure you have the latest revision : git pull
Run autogen.sh, this will generate all the needed autotools files : ./autogen.sh. If you get syntax errors during autogen.sh, check that all the needed modules are installed. If a dependency is missing, autogen.sh cannot add the correct check and you don't get a nice error message.
Compile it : make.
Install it : make install.

Warning A user reported that git pull does not always correctly update all the files. Removing the previously pulled files and then doing a fresh git pull should fix this.

Extra compile options for developers[]

If you work on gmpc, you might want to compile gmpc with the following extra option for autogen.sh or configure:

--enable-maintainermode

This makes gcc more strict and stop on all warnings.

Build system[]

If you change gmpc's build system, make sure that it still passes make distcheck.

Tips & Tricks[]

If you want to replace the running gmpc with your freshly compiled version run

./gmpc --replace

If you want to test the memory usage in f.e. massif, but withouth all the plugins run it like:

./gmpc --disable-plugins

You can check the revision of a git build by looking in the about dialog or running gmpc --version.

== Getting Involved/Contact the Developers :== See the GMPC HELP page.