Difference between revisions of "Obtaining the library source from Subversion"
Crazyeddie (Talk | contribs) |
Crazyeddie (Talk | contribs) m (Couple of minor things (useless git)) |
||
| Line 1: | Line 1: | ||
| − | + | All the code for CrazyEddie's GUI System (and the layout editor) is kept in a revision control system known as Subversion (SVN). This is a tool that allows us to easily track changes to the code (who did what, and when), to maintain multiple different versions (branches) for the code, and, where necessary, undo, revert, or merge code changes. | |
| − | All the code for CrazyEddie's GUI System (and the layout editor) is kept in a revision control system known as Subversion (SVN). This is a tool that allows us to easily track changes to the code (who did what, and when), to maintain multiple different versions (branches) for the code, and, where necessary, undo, revert, or merge | + | |
Generally speaking, each stable release series has a seperate branch, and any changes made on those branches are largely bug-fixes and non-breaking (where possible) changes. The main 'trunk' code is where the latest and greatest code can be found, although this version of the code is generally to be considered as unstable / testing code. On the whole, we maintain two branches at once; whichever is the latest 'stable' branch, and the main trunk code. When a new release is made, previous release branches are generally considered obsolete (this will continue at least until we reach version 1.0.0 - at this stage we may consider maintaining support for multiple released versions). | Generally speaking, each stable release series has a seperate branch, and any changes made on those branches are largely bug-fixes and non-breaking (where possible) changes. The main 'trunk' code is where the latest and greatest code can be found, although this version of the code is generally to be considered as unstable / testing code. On the whole, we maintain two branches at once; whichever is the latest 'stable' branch, and the main trunk code. When a new release is made, previous release branches are generally considered obsolete (this will continue at least until we reach version 1.0.0 - at this stage we may consider maintaining support for multiple released versions). | ||
| Line 7: | Line 6: | ||
| − | + | = Getting the Code = | |
To obtain the code you use the Subversion client command 'svn', and the command is to get the trunk code is simply: | To obtain the code you use the Subversion client command 'svn', and the command is to get the trunk code is simply: | ||
| Line 24: | Line 23: | ||
| − | + | = Compiling = | |
Now that you have the code, you probably want to compile it ;) | Now that you have the code, you probably want to compile it ;) | ||
Revision as of 18:21, 3 April 2006
All the code for CrazyEddie's GUI System (and the layout editor) is kept in a revision control system known as Subversion (SVN). This is a tool that allows us to easily track changes to the code (who did what, and when), to maintain multiple different versions (branches) for the code, and, where necessary, undo, revert, or merge code changes.
Generally speaking, each stable release series has a seperate branch, and any changes made on those branches are largely bug-fixes and non-breaking (where possible) changes. The main 'trunk' code is where the latest and greatest code can be found, although this version of the code is generally to be considered as unstable / testing code. On the whole, we maintain two branches at once; whichever is the latest 'stable' branch, and the main trunk code. When a new release is made, previous release branches are generally considered obsolete (this will continue at least until we reach version 1.0.0 - at this stage we may consider maintaining support for multiple released versions).
It is possible to browse the SVN repository online by visiting http://svn.sourceforge.net/viewcvs.cgi/crayzedsgui/cegui_mk2/
Getting the Code
To obtain the code you use the Subversion client command 'svn', and the command is to get the trunk code is simply:
svn co https://svn.sourceforge.net/svnroot/crayzedsgui/cegui_mk2/trunk cegui_mk2-trunk
This will 'checkout' the code from SVN, and place it in the directory 'cegui_mk2-trunk'
If you want to obtain the latest code in from one of the stable branches, then the command you should issue is:
svn co https://svn.sourceforge.net/svnroot/crayzedsgui/cegui_mk2/branches/v0-4 cegui_mk2-0-4
This will get you the latest code from the stable 'v0-4' branch (release series 0.4.x), and place it in the directory 'cegui_mk2-0-4'
Compiling
Now that you have the code, you probably want to compile it ;)
The first thing to do is change the current directory and make the bootsrap file executable (minor glitch):
cd ~/cegui_mk2-trunk chmod +x bootstrap
Now you want to run bootstrap, which will run automake, autoconf, and various other tools to initialise the build environment and create the main configure script.
./bootstrap
Now you should be on familiar territorty. To configure the build, run configure:
./configure
There are various things you can change about the way the system is built, to get information about these options, pass the --help option to configure like so:
./configure --help
Once configure has run successfully, you need to run make as usual:
make
And finall, install as root:
su <and enter password ;) > make install
CrazyEddie 11:13, 3 April 2006 (PDT)
