Difference between revisions of "Development Docs"

From Armagetron
m (added links for Linux and Mac OS)
m (moved stuff around)
Line 28: Line 28:
  
 
* [[Windows Development System]]
 
* [[Windows Development System]]
* [[Working with SVN]]
 
 
* [[Cross-compiler]]
 
* [[Cross-compiler]]
 
* [[Used Libraries]]
 
* [[Used Libraries]]
 +
* [http://wrtlprnft.ath.cx/doxy/html/ Doxy]
 +
 +
== Source Control ==
 +
 +
* [[Working with SVN]]
 +
* [[Bazaar]] and how we use it
 
* [[Working with SVK]]
 
* [[Working with SVK]]
* [http://wrtlprnft.ath.cx/doxy/html/ Doxy]
 
  
 
== Stuff That's Current ==
 
== Stuff That's Current ==
Line 62: Line 66:
 
* [[Resource System]]
 
* [[Resource System]]
 
* [[Statistical Collections Database]] (fancy way of saying "stat files")
 
* [[Statistical Collections Database]] (fancy way of saying "stat files")
 
== Source Control ==
 
 
* [[Bazaar]] and how we use it
 
  
 
== Stuff That's Real but doesn't fit above ==
 
== Stuff That's Real but doesn't fit above ==

Revision as of 12:00, 17 September 2008


Sections: Installing the Game | Playing the Game | Competition Hub | Server Administration | Extending Armagetron Advanced | Development Docs


This is documentation for developers or for people who just want to hack on the code. It is not intended to replace the automatic API documentation generated by doxygen (we do have a doxyfile, right?), but is intended to supplement those documents with additional information that may not necessarily appear in the API docs. It is also not intended as a substitute for good commenting tactics. And finally, it is a place to put planning documentation (like the stuff Philippe writes), proposals, RFC-type material, and so forth. But not the roadmap, we use Sourceforge's tracker for that.

Documentation

Building the Game

Building Armagetron Advanced boils down to 4 basic steps. The steps themselves are each highly platform-dependent, but the four steps are the same everywhere. Each step differs further in whether or not you're building from a branch or the trunk, and each branch may differ. Finally, each step differs depending on if you're building a source release or from version control. Here we'll concern ourselves with building the trunk only. Releases should include their own build instructions.

  1. Install the development environment
  2. Satisfy dependencies
  3. Unpackage source/source checkout from version control
  4. Build a distribution

Platform-specific instructions (they should all follow the four step structure given, that's why it's there!):

todo: the linux and mac os x pages

Other useful hacker documentation

Source Control

Stuff That's Current

Stuff in SVN HEAD

Data File Handling

Stuff That's Real but doesn't fit above

Wishlist, or Stuff that's planned

(Might not be planned, but this is it)

History

This is stuff that's of historical significance to the project. It's very difficult to remember where you're going if you don't remember where you came from, right? This is technical stuff. Community history should have its own section.


Sections: Installing the Game | Playing the Game | Competition Hub | Server Administration | Extending Armagetron Advanced | Development Docs


Information about the current Armagetron Advanced Development. How to compile the game or current working in progress.