Fusion Developers Corner

This is the spot for a lot of developer-related information.

Committers

Committers are people with valid ​OSGeo User IDs that have permission to commit changes to the SVN repository. Any existing committer can visit ​this page to add or remove committers. You will need the ​OSGeo User ID to add users. The reference for this is ​here.

A list of Fusion Committers is available here.

Patches

Patches are text files that contain the difference between a locally checked out version of fusion and the version in the SVN repository. See CreatingPatches for instructions on how to create a patch and ApplyingPatches for applying a patch to your local working version.

SVN

​Subversion (SVN) is a tool for helping developers manage a code base. The Fusion code base is stored in an SVN repository hosted at OSGeo. You can view the source in your web browser ​directly or use the built in trac browser for a more enjoyable experience.

The Fusion SVN repository is organized into several main folders.

There are different ways of using SVN to work with a repository including a command line svn tool and several standalone and integrated graphical tools. We will typically describe the command-line use of SVN and it is up to you to find the equivalent functionality in your fancy graphical tool. See the following resources for more information on working with SVN:

• Get a working copy of the Fusion code
• Update a working copy of the Fusion code
• Submit changes to the Fusion repository
• Using SVN to create patches

Using SVN

To check out a copy of trunk, a branch, a tagged version, or a sandbox, you need to know the URL and use svn checkout <url>. For instance:

• svn co http://svn.osgeo.org/fusion/trunk - check out trunk
• svn co http://svn.osgeo.org/fusion/branches/fusion-1.0 - check out the branch for version 1.0
• svn co http://svn.osgeo.org/fusion/tags/fusion-1.0.0 - check out the 1.0.0 released version
• svn co http://svn.osgeo.org/fusion/sandbox/pagameba - check out pagameba's sandbox

Once you have a checked out copy, this is called a working copy. To update a working copy to the latest version, you use the update command with no arguments:

• svn update

To move the working copy to a specific revision number, you can add the revision parameter:

• svn update -r <revision>

To see if you have changes in your working copy against the current revision:

• svn status

To see the differences between your working copy and the current revision:

• svn diff
• svn diff > diff.patch redirects the output to a file that is suitable for using with the patch command

The Build Process

Creating a binary build