Developers Info
From Emma
Developers can get updated access to the Emma source code directly from the Emma SVN server. This affords read-only access to the current Emma source tree.
Viewing the latest source code:
You can browse the Emma source tree at:
http://svn.sourceforge.net/emma3d
Getting the Subversion client:
Download and track the Emma source, using Subversion. Get the latest Subversion client here:
http://subversion.tigris.org/
Or you can use TortoiseSVN.
Getting mainline of the Emma source code from the Emma SVN server:
Normally you will only need to access the mainline of the Emma source tree for building and developing Emma. To get the mainline, create a directory called 'emma' and a subdirectory of it called 'mainline' and change to that directory, for example on Linux:
mkdir -p emma cd emma mkdir -p mainline cd mainline
then type the command:
svn co https://svn.sourceforge.net/svnroot/emma3d/mainline .
Getting all of the Emma source code from the Emma SVN server:
The whole Emma source tree consists of mainline, all of the branches and big asset files. To get all of the source tree, create a directory called, for instance, 'emma' in which you have write permission, then change to that directory; for example on Linux
mkdir -p emma cd emma
then type the command:
svn co https://svn.sourceforge.net/svnroot/emma3d .
Updating your local copy of the Emma source tree:
Type the command
svn update .
in the 'emma' or 'emma/mainline' directory to update the local copy of the tree to the latest revision.
Developing components, plugins, and extensions for Emma:
Here is a quick guide to getting started with Emma :
/emma/mainline/emma/docs/GettingStarted.htm.
We encourage developers to create extensions and plugins for Emma. Each extension developer can get write-access to a part of the Emma source tree so that their development can procede in parallel with Emma development. Please contact us in the forums or email us for more information.
Submitting patches to Emma:
You can submit your changes to the Emma source code by creating a patch in subversion and then submitting that difference file at SourceForge:
https://sourceforge.net/tracker/?func=add&group_id=141171&atid=748722
