Spring - User contributions [en]

Building Spring on MacOSX

2010-03-28T20:38:41Z

Patmo98: /* Using CMake (2.6 or newer) (patmo98's method) */

[[Engine_Development|Development]] < [[Building_spring|Building Spring]] < {{FULLPAGENAME}}

= Duplicate and missing information =

This page is a partial duplicate of [[Spring_on_MacOSX]] but both have unique information.

=Build from source on MacOSX=

'''Guide is for x86/Intel based OSX installs'''

I am hoping that with our efforts on the forum that we can have an .app bundle released everytime spring is updated and that will save most people needing to go through the headache of compiling from source code. But if you must try, then here's the steps to help!

I cannot stress enough that this will most likely only work on Intel based systems at this stage. With my understanding of how unitsync works, it seems like online play will not be possible between PPC and x86 architecture.

=Obtaining the Source=
{{Obtaining_The_Source_Code}}

=Get Dependencies=

You will need to install some development packages Spring depends on. Most of these are available using [http://http://www.macports.org/ Macports] (similar to portage / apt-get etc available on various linux distro's)

You will also need to install the [http://developer.apple.com/TOOLS/Xcode/ Xcode developers package] (this requires a free membership to apple's ADC website)

==Full list==

*Programs necessary to build
**Xcode
**cmake (or scons)
**zip
**The usual build toolchain
***gcc ''(comes with Xcode tools)''
***make ''(comes with Xcode tools)''
*Libraries
**SDL
**boost (version 1.35 or later recommended)
***threads
***regex
***signals
***system
**DeviL (IL, ILU)
**OpenAL ''Please check the OpenAL section for MacOSX specific info''
**OpenGL headers (mesa, glew, etc.) ''(comes with Xcode tools)''
**zlib
**freetype
**ogg,vorbis and vorbisfile
*Optional, for bindings and Ais
**Python (2.5)
**Java-SDK ''(pre-installed on OSX)''

==Using Macports==

Once you have downloaded and configured Macports use these commands to download / compile and install the required dependencies :

sudo port install cmake 
sudo port install libsdl 
sudo port install libsdl-framework 
sudo port install boost 
sudo port install boost-jam 
sudo port install libpng #These image libraries might not be needed, but ma save you some headaches 
sudo port install jpeg 
sudo port install tiff 
sudo port install libogg 
sudo port install libvorbis 
sudo port install python25 
sudo port install libdevil # as of October 12th 2009 the Macports install of libdevil (1.6.8-rc2_0) is broken for some people. If you get errors like /opt/local/include/IL/il.h:505: error: â€˜<anonymous>â€™ has incomplete type while building spring, you'll probably need to install it from source. ) 


If all was successful, you are very close to being able to compile Spring naively!

==Installing libdevil from source==

Make sure that all the other port packages are installed first!
Download the source. Right now 1.6.8-rc2_0 has the bug we're trying to work around, so don't use that one, or earlier versions.

Extract the source code.

Configure it. I used this command.
./configure --enable-png --enable-ILU --enable-ILUT --enable-x86_64 CPPFLAGS="-I/opt/local/include/ -L/opt/local/lib/" LDFLAGS=-L/opt/local/lib/

Make sure you have support for png, jpg, dds, and tga

Make it with "make"

Part way through you'll get an error about malloc.h not being found. To fix it, replace <malloc.h> with <sys/malloc.h>

install with sudo make install

==OpenAL==

After having mountains of problems myself with the OpenAL pre-installed with the Xcode tools, I discovered that it is version 1.0 of OpenAL (not the correct version we want).

Head to your /System/Library/Framework/ folder and delete any trace of OpenAL framework / folders that are there.

[http://kcat.strangesoft.net/openal-releases/openal-soft-1.8.466.tar.bz2 Now download this copy of OpenAL]

Using the terminal, go into the folder where you downloaded openal-soft and pass these commands

bzip2 -d openal-soft-xxxx.tar.bz2 | tar xvf - 
cd openal-soft-xxxx 
cmake . 
make 
make install

All done, now you will have no problems compiling the Sound.cpp file in spring!

=Build And Install=

The build will spew out warnings like the following, which you can safely ignore: 
warning: division by zero 
warning: 'q' may be used uninitialized in this function 

==Removing duplicate libraries==

Make sure that you remove all extra libraries before the first time you call cmake. If not, cmake will make your life a living hell. Check in /usr /usr/local /opt/local and /Library/Frameworks. Also, don't change the location of the source directory, librarys, or includes after calling cmake. If you do change any of the locations you can't just call cmake again. The only way I know to tell it to recompute everything from scratch is this:
*Change to the root of the git tree
*Remove every single visible file.
*Run git reset --hard

==Using CMake (2.6 or newer) (Adso's method)==
This is the only way I have compiled spring successfully so far :

(could someone please add a better way? As I cannot workout how to get xcodebuild to run the "install portion of the make file")

<code><pre>cmake .
make
make install</pre></code>

This will install spring in all the right places to be run from a command line (but don't yet, it compiles an unusable executable, we just needed to get the makefile to install everything to the right place)

Now pass these commands

<code><pre>cmake -G Xcode
xcodebuild</pre></code>

This will have made a folder called "Debug" and will contain a command line program Spring, and Libunitsync.dylib

now to make sure the correct copy of spring runs when you are using the terminal pass the following command

<code><pre>sudo cp spring /usr/local/bin</pre></code>

Now you are ready to ready to play Spring on your MacOSX system!
Enjoy!

==Using CMake (2.6 or newer) (patmo98's method)==
The worst problem I ran into while trying to use Adso's method was getting the include and library paths to work.
'''This probably won't be needed unless you you been installing libraries from source or using fink.'''

Make sure before you start that you don't have any extra copies of libraries laying around.

Get the dependencies and source code.

<code><pre>ccmake .
</pre></code>

If you see a list of options here, you've already run (c)cmake before and that may cause you trouble. Press 'c' to have it auto configure. Press 't' to switch to advanced mode. Manually add the following includes and librarys. Yes, this is an ugly hack that should be instead fixed in the build system, but I don't know enough about cmake to fix it.

CMAKE_CXX_FLAGS -I/usr/local/include -I/opt/local/include
CMAKE_C_FLAGS -I/usr/local/include -I/opt/local/include
CMAKE_EXE_LINKER_FLAGS -L/usr/local/lib -L/opt/local/lib

You may need to add more directories.

<code><pre>make
</pre></code>

If the build finishes successfully, you will now have the spring executable, unitsync.dylib and some other assorted things.

Spring will search for Libunitsync.dylib in the same directory as the executable (and possibly other places), and search for the data files in ~/.spring/.
If you have access to a working windows install, just copy the windows install to ~/.spring and run the executable from where ever you like.

Now you are ready to ready to play Spring on your MacOSX system!
Enjoy!

=Finalizing installation=

Will update later once I update the Springlobby wiki with all my OSX information!

If you need to contact me, send a PM to '''adso''' on the forums, or catch me in #sy or #springlobby in the lobby chat :)

--[[User:Adso|Adso]] 06:23, 29 August 2009 (UTC)

[[Category:Compiling]]

Spring on MacOSX

2010-03-28T00:02:50Z

Patmo98: /* Installing the Dependencies */ Fixing wording

Because all needed libraries are available for OSX as well, you can compile a working version of Spring for Mac. But Unitsync will only work between Intel Macs and PCs, but not between those and PPC, and due to Apple's switch from PPC to Intel and due to the astronomical amount of effort it would take to to make them sync, there is no PPC port under development.

There's also a working lobby client for Mac OSX, follow the instruction below to compile it.

=Install Spring from source on an Intel Mac=
The following guide was created and tested in a 2,53 Ghz 13" MacBook Pro, 4 GB RAM Nvidia GeForce 9400M and a MacPro Xenon Quadcore ATI Radeon HD 4870, both with Snow Leopard (10.6).

==Dependencies:==
You will need the following dependencies to compile:
Programs necessary to build
* Xcode Tools
* cmake (included in Xcode tools)
* zip
* p7zip

Libraries
* SDL
* boost (version 1.35 or later recommended)
* DeviL (IL, ILU)
* OpenAL (comes with Xcode tools)
* OpenGL headers (mesa, glew, etc.) (comes with Xcode tools)
* zlib
* freetype
* ogg,vorbis and vorbisfile
* Python (2.5)
* glew

==Installing the Dependencies==

Firstly, download the Xcode Development Tools from Apple or install them from your OSX DVD: http://developer.apple.com/technology/xcode.html (you will need to register, but its free of charge)

Then download and install Macports (http://www.macports.org)
You need to be administrator to complete the following.
Open the Terminal and copy and paste the first command and wait until it is completed, continue one-by-one with the others (you may be asked for the admin password each time).

sudo port install cmake
sudo port install libsdl
sudo port install libsdl-framework
sudo port install boost
sudo port install glew
sudo port install boost-jam
sudo port install libpng
sudo port install jpeg
sudo port install tiff
sudo port install libogg
sudo port install libvorbis
sudo port install python25
sudo port install libdevil
sudo port install p7zip

This will take some time and disk space, but should complete without problems. If you experience any errors, download the dependencies' source and compile it.

==Fixes==
Download the latest spring source from the download page.
If you try to compile now, you will experience some errors, and therefore you will have to apply theseÂ patchÂ files:

https://trac.macports.org/attachment/ticket/23556/patch-file-extension.diff
https://trac.macports.org/attachment/ticket/23556/platform-misc-cpp.diff

cdÂ intoÂ theÂ sourceÂ directoryÂ andÂ execute

<code>patchÂ -pÂ 0Â <Â patch-file-extension.diff

patchÂ -pÂ 0Â <Â platform-misc-cpp.diff</code>

==Compiling:==
Open the Terminal, change into the Spring source folder (e.g.: "cd Desktop/spring_0_80_5_2/") and follow the instructions below:
(You will be asked for the admin password)

type "cmake ." (the dot and the gap is important)
type "make" (this will take some time)
type "sudo make install"

After the above commands have finished, check "/usr/local/share/games/spring/AI/Interfaces/C/0.1/" to see if the files there end with '.so' or '.dylib'. If they are named .so you will get an error message when using AI bots. Run this command to rename all .so files to .dylib:

for X in `find /usr/local/share/games/spring/ -name "*.so"`; do sudo mv $X ${X/.so/.dylib}; done;

==Result==
Now, you have a a Unix Executable File called "spring" in your source directory and a "spring" directory in "usr/local/share/games/" (you need to make hidden folders visible to see it).
Create a folder called "maps" and a folder called "mods" there. (This is where Spring will check for maps/mods).
You can double click on the spring file (mod+map needed) and test if everything is alright.

=Compiling the Lobby=
You will need to get a lobby client (e.g.: SpringLobby: http://springlobby.info) and the dependencies to compile it from source following this guide: http://springlobby.info/projects/springlobby/wiki/InstallFromSource
This Chapter will be extended soon.

--[[User:Grapefruit|Grapefruit]] 11:08, 4 December 2009 (UTC)
[[Category: Mac]]

SpringEngineTODO

2010-03-25T20:06:58Z

Patmo98:

A collection of ideas which could improve Spring.

* clean up, sanitize, and make consistent the error handling in the engine
* add general serializing to the engine, which touches the following:
** Implement saving/loading. There are a lot of direct LoadSave() functions in the game code, but the easier way would probably to finish the serialization in the class registration type interfaces (rts/System/creg), so everything can be serialized automatically.
*** Requires: C/C++
*** Time: ~3 months
*** Level of difficulty: medium - hard
** [[Syncing System|Implement re-sync]]. After a sync problem is detected, and a re-sync of the random seed does not fix it the game would pause and use the rsync to adjust game state (current plan if for float3 data) to resync. After using rsync on it should be able to continue normally until the next sync error is detected.
*** Requires: C/C++, network programming
*** Time: ~3< months
*** Level of difficulty: Hard
** Joining the game while it is running (probably need one of those 2 mentioned above: save/load or resync)
*** Requires: C/C++, network programming
*** Time: ~3< months
*** Level of difficulty: Hard

* Implement a general sensor system replacing the radars, as described in http://taspring.clan-sy.com/phpbb/viewtopic.php?t=6105
** Requires: C/C++, 3D/2D math (Lua knowledge not required, but prefered)
** Time: ~2 months
** Level of difficulty: Medium

* Add a dynamic-lighting system: Allow units to have dynamic lights on them that affect lighting of other units and landscape, with sort of "approximating lights" for cases where a lot of units get close together. This is a big thing, but it would improve spring graphics a lot if done well. Or Deferred Lighting/Shading?
** Requires: C/C++, 3D math(, GLSL) (Lua knowledge not required, but prefered)
** Time: ~3 months
** Level of difficulty: Medium-hard

* Get a mac version working. Contact the developers on the forums for this, as there are people who build and run it successfully. Still need proper packaging and maintaining,
** Requires: C/C++, CMake and MacOS
** Time: < 1 month
** Level of difficulty: Medium
** More information at http://springrts.com/wiki/Spring_on_MacOSX

* Extending the resource system to allow more than two resources (metal/energy)
** Requires: C/C++ (Lua knowledge not required, but prefered)
** Time: ~1-3 months
** Level of difficulty: Easy-Medium

* Expand Springs script abilities by extending the lua interface (commandAIs,MoveTypes,LOS,Pathing,..).
** Requires: C/C++, lua
** Time: ~3< months
** Level of difficulty: Medium

* Exposing more Spring functions to the Lua world (command AIs, move types) or/and small frameworks
** Requires: basic C/C++, Lua
** Time: ~1-3< months (depends on the goal)
** Level of difficulty: Easy-medium

* Implement MD5 as a model format or add other model formats.
** Requires: C/C++, 3D math (Lua knowledge not required, but prefered)
** Time: ~1-3 months
** Level of difficulty: Medium

* Fix SM3 or develop a new mapping format
** Requires: C/C++, 3D math
** Time: ~1-3 months
** Level of difficulty: Medium

* Add p2p/round-robin for hosting (so host exit doesn't stop the game)
** Requires: C/C++, network programming
** Time: ~3< months
** Level of difficulty: Medium

* Proper GUI for spring.exe with extended singleplayer abilities, better map/mod browsing, adding Bots (AIs), selecting start positions, choosing color, selecting map/mod options.
** Requires: C/C++, 3D math, GUI programming, OpenGL programming, Lua
** Time: ~1-3 moths (depends on the amount of functions)
** Level of difficulty: Medium

* Fix bugs, extend and improve functionality, etc.

Even though this isn't really about the Spring engine:

* SpringLobby is a cross-platform lobby client, implemented in C++ and wxWidgets. We encourage you to look into our todo list on http://springlobby.info and see what you could do for it.

Lua:

* Create a Mission Development Kit: ie, do whatever it takes to make it easy to create campaign missions, eg create a gui tool that makes it easy to place units on the map, create triggers, and so on.

[[Category:Source development]]

Spring on MacOSX

2009-10-18T14:19:47Z

Patmo98: /* Notes */

Building Spring on MacOSX

2009-10-16T17:30:46Z

Patmo98: Added the way that I built spring for Mac

[[Engine_Development|Development]] < [[Building_spring|Building Spring]] < {{FULLPAGENAME}}

= Duplicate and missing information =

This page is a partial duplicate of [[Spring_on_MacOSX]] but both have unique information.

=Build from source on MacOSX=

'''Guide is for x86/Intel based OSX installs'''

I am hoping that with our efforts on the forum that we can have an .app bundle released everytime spring is updated and that will save most people needing to go through the headache of compiling from source code. But if you must try, then here's the steps to help!

I cannot stress enough that this will most likely only work on Intel based systems at this stage. With my understanding of how unitsync works, it seems like online play will not be possible between PPC and x86 architecture.

=Obtaining the Source=
{{Obtaining_The_Source_Code}}

=Get Dependencies=

You will need to install some development packages Spring depends on. Most of these are available using [http://http://www.macports.org/ Macports] (similar to portage / apt-get etc available on various linux distro's)

You will also need to install the [http://developer.apple.com/TOOLS/Xcode/ Xcode developers package] (this requires a free membership to apple's ADC website)

==Full list==

*Programs necessary to build
**Xcode
**cmake (or scons)
**zip
**The usual build toolchain
***gcc ''(comes with Xcode tools)''
***make ''(comes with Xcode tools)''
*Libraries
**SDL
**boost (version 1.35 or later recommended)
***threads
***regex
***signals
***system
**DeviL (IL, ILU)
**OpenAL ''Please check the OpenAL section for MacOSX specific info''
**OpenGL headers (mesa, glew, etc.) ''(comes with Xcode tools)''
**zlib
**freetype
**ogg,vorbis and vorbisfile
*Optional, for bindings and Ais
**Python (2.5)
**Java-SDK ''(pre-installed on OSX)''

==Using Macports==

Once you have downloaded and configured Macports use these commands to download / compile and install the required dependencies :

sudo port install cmake 
sudo port install libsdl 
sudo port install libsdl-framework 
sudo port install boost 
sudo port install boost-jam 
sudo port install libpng #These image libraries might not be needed, but ma save you some headaches 
sudo port install jpeg 
sudo port install tiff 
sudo port install libogg 
sudo port install libvorbis 
sudo port install python25 
sudo port install libdevil # as of October 12th 2009 the Macports install of libdevil (1.6.8-rc2_0) is broken for some people. If you get errors like /opt/local/include/IL/il.h:505: error: â€˜<anonymous>â€™ has incomplete type while building spring, you'll probably need to install it from source. ) 


If all was successful, you are very close to being able to compile Spring naively!

==Installing libdevil from source==

Make sure that all the other port packages are installed first!
Download the source. Right now 1.6.8-rc2_0 has the bug we're trying to work around, so don't use that one, or earlier versions.

Extract the source code.

Configure it. I used this command.
./configure --enable-png --enable-ILU --enable-ILUT --enable-x86_64 CPPFLAGS="-I/opt/local/include/ -L/opt/local/lib/" LDFLAGS=-L/opt/local/lib/

Make sure you have support for png, jpg, dds, and tga

Make it with "make"

Part way through you'll get an error about malloc.h not being found. To fix it, replace <malloc.h> with <sys/malloc.h>

install with sudo make install

==OpenAL==

After having mountains of problems myself with the OpenAL pre-installed with the Xcode tools, I discovered that it is version 1.0 of OpenAL (not the correct version we want).

Head to your /System/Library/Framework/ folder and delete any trace of OpenAL framework / folders that are there.

[http://kcat.strangesoft.net/openal-releases/openal-soft-1.8.466.tar.bz2 Now download this copy of OpenAL]

Using the terminal, go into the folder where you downloaded openal-soft and pass these commands

bzip2 -d openal-soft-xxxx.tar.bz2 | tar xvf - 
cd openal-soft-xxxx 
cmake . 
make 
make install

All done, now you will have no problems compiling the Sound.cpp file in spring!

=Build And Install=

The build will spew out warnings like the following, which you can safely ignore: 
warning: division by zero 
warning: 'q' may be used uninitialized in this function 

==Removing duplicate libraries==

Make sure that you remove all extra libraries before the first time you call cmake. If not, cmake will make your life a living hell. Check in /usr /usr/local /opt/local and /Library/Frameworks. Also, don't change the location of the source directory, librarys, or includes after calling cmake. If you do change any of the locations you can't just call cmake again. The only way I know to tell it to recompute everything from scratch is this:
*Change to the root of the git tree
*Remove every single visible file.
*Run git reset --hard

==Using CMake (2.6 or newer) (Adso's method)==
This is the only way I have compiled spring successfully so far :

(could someone please add a better way? As I cannot workout how to get xcodebuild to run the "install portion of the make file")

<code><pre>cmake .
make
make install</pre></code>

This will install spring in all the right places to be run from a command line (but don't yet, it compiles an unusable executable, we just needed to get the makefile to install everything to the right place)

Now pass these commands

<code><pre>cmake -G Xcode
xcodebuild</pre></code>

This will have made a folder called "Debug" and will contain a command line program Spring, and Libunitsync.dylib

now to make sure the correct copy of spring runs when you are using the terminal pass the following command

<code><pre>sudo cp spring /usr/local/bin</pre></code>

Now you are ready to ready to play Spring on your MacOSX system!
Enjoy!

==Using CMake (2.6 or newer) (patmo98's method)==
The worst problem I ran into while trying to use Adso's meathod was getting the include and library paths to work.

Make sure before you start that you don't have any extra copies of libraries laying around.

Get the dependencies and source code.

<code><pre>ccmake .
</pre></code>

If you see a list of options here, you've already run (c)cmake before and that may cause you trouble. Press 'c' to have it auto configure. Press 't' to switch to advanced mode. Manually add the following includes and librarys. Yes, this is an ugly hack that should be instead fixed in the build system, but I don't know enough about cmake to fix it.

CMAKE_CXX_FLAGS -I/usr/local/include -I/opt/local/include
CMAKE_C_FLAGS -I/usr/local/include -I/opt/local/include
CMAKE_EXE_LINKER_FLAGS -L/usr/local/lib -L/opt/local/lib

You may need to add more directories.

<code><pre>make
</pre></code>

If the build finishes successfully, you will now have the spring executable, unitsync.dylib and some other assorted things.

Spring will search for Libunitsync.dylib in the same directory as the executable (and possibly other places), and search for the data files in ~/.spring/.
If you have access to a working windows install, just copy the windows install to ~/.spring and run the executable from where ever you like.

Now you are ready to ready to play Spring on your MacOSX system!
Enjoy!

=Finalizing installation=

Will update later once I update the Springlobby wiki with all my OSX information!

If you need to contact me, send a PM to '''adso''' on the forums, or catch me in #sy or #springlobby in the lobby chat :)

--[[User:Adso|Adso]] 06:23, 29 August 2009 (UTC)

[[Category:Compiling]]

Building Spring on MacOSX

2009-10-16T17:06:36Z

Patmo98: Reworded something confusing

[[Engine_Development|Development]] < [[Building_spring|Building Spring]] < {{FULLPAGENAME}}

= Duplicate and missing information =

This page is a partial duplicate of [[Spring_on_MacOSX]] but both have unique information.

=Build from source on MacOSX=

'''Guide is for x86/Intel based OSX installs'''

I am hoping that with our efforts on the forum that we can have an .app bundle released everytime spring is updated and that will save most people needing to go through the headache of compiling from source code. But if you must try, then here's the steps to help!

I cannot stress enough that this will most likely only work on Intel based systems at this stage. With my understanding of how unitsync works, it seems like online play will not be possible between PPC and x86 architecture.

=Obtaining the Source=
{{Obtaining_The_Source_Code}}

=Get Dependencies=

You will need to install some development packages Spring depends on. Most of these are available using [http://http://www.macports.org/ Macports] (similar to portage / apt-get etc available on various linux distro's)

You will also need to install the [http://developer.apple.com/TOOLS/Xcode/ Xcode developers package] (this requires a free membership to apple's ADC website)

==Full list==

*Programs necessary to build
**Xcode
**cmake (or scons)
**zip
**The usual build toolchain
***gcc ''(comes with Xcode tools)''
***make ''(comes with Xcode tools)''
*Libraries
**SDL
**boost (version 1.35 or later recommended)
***threads
***regex
***signals
***system
**DeviL (IL, ILU)
**OpenAL ''Please check the OpenAL section for MacOSX specific info''
**OpenGL headers (mesa, glew, etc.) ''(comes with Xcode tools)''
**zlib
**freetype
**ogg,vorbis and vorbisfile
*Optional, for bindings and Ais
**Python (2.5)
**Java-SDK ''(pre-installed on OSX)''

==Using Macports==

Once you have downloaded and configured Macports use these commands to download / compile and install the required dependencies :

sudo port install cmake 
sudo port install libsdl 
sudo port install libsdl-framework 
sudo port install boost 
sudo port install boost-jam 
sudo port install libpng #These image libraries might not be needed, but ma save you some headaches 
sudo port install jpeg 
sudo port install tiff 
sudo port install libogg 
sudo port install libvorbis 
sudo port install python25 
sudo port install libdevil # as of October 12th 2009 the Macports install of libdevil (1.6.8-rc2_0) is broken for some people. If you get errors like /opt/local/include/IL/il.h:505: error: â€˜<anonymous>â€™ has incomplete type while building spring, you'll probably need to install it from source. ) 


If all was successful, you are very close to being able to compile Spring naively!

==Installing libdevil from source==

Make sure that all the other port packages are installed first!
Download the source. Right now 1.6.8-rc2_0 has the bug we're trying to work around, so don't use that one, or earlier versions.

Extract the source code.

Configure it. I used this command.
./configure --enable-png --enable-ILU --enable-ILUT --enable-x86_64 CPPFLAGS="-I/opt/local/include/ -L/opt/local/lib/" LDFLAGS=-L/opt/local/lib/

Make sure you have support for png, jpg, dds, and tga

Make it with "make"

Part way through you'll get an error about malloc.h not being found. To fix it, replace <malloc.h> with <sys/malloc.h>

install with sudo make install

==OpenAL==

After having mountains of problems myself with the OpenAL pre-installed with the Xcode tools, I discovered that it is version 1.0 of OpenAL (not the correct version we want).

Head to your /System/Library/Framework/ folder and delete any trace of OpenAL framework / folders that are there.

[http://kcat.strangesoft.net/openal-releases/openal-soft-1.8.466.tar.bz2 Now download this copy of OpenAL]

Using the terminal, go into the folder where you downloaded openal-soft and pass these commands

bzip2 -d openal-soft-xxxx.tar.bz2 | tar xvf - 
cd openal-soft-xxxx 
cmake . 
make 
make install

All done, now you will have no problems compiling the Sound.cpp file in spring!

=Build And Install=

The build will spew out warnings like the following, which you can safely ignore: 
warning: division by zero 
warning: 'q' may be used uninitialized in this function 

==Removing duplicate libraries==

Make sure that you remove all extra libraries before the first time you call cmake. If not, cmake will make your life a living hell. Check in /usr /usr/local /opt/local and /Library/Frameworks. Also, don't change the location of the source directory, librarys, or includes after calling cmake. If you do change any of the locations you can't just call cmake again. The only way I know to tell it to recompute everything from scratch is this:
*Change to the root of the git tree
*Remove every single visible file.
*Run git reset --hard

==Using CMake (2.6 or newer)==
This is the only way I have compiled spring successfully so far :

(could someone please add a better way? As I cannot workout how to get xcodebuild to run the "install portion of the make file")

<code><pre>cmake .
make
make install</pre></code>

This will install spring in all the right places to be run from a command line (but don't yet, it compiles an unusable executable, we just needed to get the makefile to install everything to the right place)

Now pass these commands

<code><pre>cmake -G Xcode
xcodebuild</pre></code>

This will have made a folder called "Debug" and will contain a command line program Spring, and Libunitsync.dylib

now to make sure the correct copy of spring runs when you are using the terminal pass the following command

<code><pre>sudo cp spring /usr/local/bin</pre></code>

Now you are ready to ready to play Spring on your MacOSX system!
Enjoy!

=Finalizing installation=

Will update later once I update the Springlobby wiki with all my OSX information!

If you need to contact me, send a PM to '''adso''' on the forums, or catch me in #sy or #springlobby in the lobby chat :)

--[[User:Adso|Adso]] 06:23, 29 August 2009 (UTC)

[[Category:Compiling]]

Building Spring on MacOSX

2009-10-16T17:04:59Z

Patmo98: typo

[[Engine_Development|Development]] < [[Building_spring|Building Spring]] < {{FULLPAGENAME}}

= Duplicate and missing information =

This page is a partial duplicate of [[Spring_on_MacOSX]] but both have unique information.

=Build from source on MacOSX=

'''Guide is for x86/Intel based OSX installs'''

I am hoping that with our efforts on the forum that we can have an .app bundle released everytime spring is updated and that will save most people needing to go through the headache of compiling from source code. But if you must try, then here's the steps to help!

I cannot stress enough that this will most likely only work on Intel based systems at this stage. With my understanding of how unitsync works, it seems like online play will not be possible between PPC and x86 architecture.

=Obtaining the Source=
{{Obtaining_The_Source_Code}}

=Get Dependencies=

You will need to install some development packages Spring depends on. Most of these are available using [http://http://www.macports.org/ Macports] (similar to portage / apt-get etc available on various linux distro's)

You will also need to install the [http://developer.apple.com/TOOLS/Xcode/ Xcode developers package] (this requires a free membership to apple's ADC website)

==Full list==

*Programs necessary to build
**Xcode
**cmake (or scons)
**zip
**The usual build toolchain
***gcc ''(comes with Xcode tools)''
***make ''(comes with Xcode tools)''
*Libraries
**SDL
**boost (version 1.35 or later recommended)
***threads
***regex
***signals
***system
**DeviL (IL, ILU)
**OpenAL ''Please check the OpenAL section for MacOSX specific info''
**OpenGL headers (mesa, glew, etc.) ''(comes with Xcode tools)''
**zlib
**freetype
**ogg,vorbis and vorbisfile
*Optional, for bindings and Ais
**Python (2.5)
**Java-SDK ''(pre-installed on OSX)''

==Using Macports==

Once you have downloaded and configured Macports use these commands to download / compile and install the required dependencies :

sudo port install cmake 
sudo port install libsdl 
sudo port install libsdl-framework 
sudo port install boost 
sudo port install boost-jam 
sudo port install libpng #These image libraries might not be needed, but ma save you some headaches 
sudo port install jpeg 
sudo port install tiff 
sudo port install libogg 
sudo port install libvorbis 
sudo port install python25 
sudo port install libdevil # as of October 12th 2009 the Macports install of libdevil (1.6.8-rc2_0) can be broken. If you get errors like /opt/local/include/IL/il.h:505: error: â€˜<anonymous>â€™ has incomplete type while building spring, you'll probably need to install it from source. ) 


If all was successful, you are very close to being able to compile Spring natively!

==Installing libdevil from source==

Make sure that all the other port packages are installed first!
Download the source. Right now 1.6.8-rc2_0 has the bug we're trying to work around, so don't use that one, or earlier versions.

Extract the source code.

Configure it. I used this command.
./configure --enable-png --enable-ILU --enable-ILUT --enable-x86_64 CPPFLAGS="-I/opt/local/include/ -L/opt/local/lib/" LDFLAGS=-L/opt/local/lib/

Make sure you have support for png, jpg, dds, and tga

Make it with "make"

Part way through you'll get an error about malloc.h not being found. To fix it, replace <malloc.h> with <sys/malloc.h>

install with sudo make install

==OpenAL==

After having mountains of problems myself with the OpenAL pre-installed with the Xcode tools, I discovered that it is version 1.0 of OpenAL (not the correct version we want).

Head to your /System/Library/Framework/ folder and delete any trace of OpenAL framework / folders that are there.

[http://kcat.strangesoft.net/openal-releases/openal-soft-1.8.466.tar.bz2 Now download this copy of OpenAL]

Using the terminal, go into the folder where you downloaded openal-soft and pass these commands

bzip2 -d openal-soft-xxxx.tar.bz2 | tar xvf - 
cd openal-soft-xxxx 
cmake . 
make 
make install

All done, now you will have no problems compiling the Sound.cpp file in spring!

=Build And Install=

The build will spew out warnings like the following, which you can safely ignore: 
warning: division by zero 
warning: 'q' may be used uninitialized in this function 

==Removing duplicate libraries==

Make sure that you remove all extra libraries before the first time you call cmake. If not, cmake will make your life a living hell. Check in /usr /usr/local /opt/local and /Library/Frameworks. Also, don't change the location of the source directory, librarys, or includes after calling cmake. If you do change any of the locations you can't just call cmake again. The only way I know to tell it to recompute everything from scratch is this:
*Change to the root of the git tree
*Remove every single visible file.
*Run git reset --hard

==Using CMake (2.6 or newer)==
This is the only way I have compiled spring successfully so far :

(could someone please add a better way? As I cannot workout how to get xcodebuild to run the "install portion of the make file")

<code><pre>cmake .
make
make install</pre></code>

This will install spring in all the right places to be run from a command line (but don't yet, it compiles an unusable executable, we just needed to get the makefile to install everything to the right place)

Now pass these commands

<code><pre>cmake -G Xcode
xcodebuild</pre></code>

This will have made a folder called "Debug" and will contain a command line program Spring, and Libunitsync.dylib

now to make sure the correct copy of spring runs when you are using the terminal pass the following command

<code><pre>sudo cp spring /usr/local/bin</pre></code>

Now you are ready to ready to play Spring on your MacOSX system!
Enjoy!

=Finalizing installation=

Will update later once I update the Springlobby wiki with all my OSX information!

If you need to contact me, send a PM to '''adso''' on the forums, or catch me in #sy or #springlobby in the lobby chat :)

--[[User:Adso|Adso]] 06:23, 29 August 2009 (UTC)

[[Category:Compiling]]

Building Spring on MacOSX

2009-10-16T17:04:34Z

Patmo98: /* Removing duplicate libraries */

[[Engine_Development|Development]] < [[Building_spring|Building Spring]] < {{FULLPAGENAME}}

= Duplicate and missing information =

This page is a partial duplicate of [[Spring_on_MacOSX]] but both have unique information.

=Build from source on MacOSX=

'''Guide is for x86/Intel based OSX installs'''

I am hoping that with our efforts on the forum that we can have an .app bundle released everytime spring is updated and that will save most people needing to go through the headache of compiling from source code. But if you must try, then here's the steps to help!

I cannot stress enough that this will most likely only work on Intel based systems at this stage. With my understanding of how unitsync works, it seems like online play will not be possible between PPC and x86 architecture.

=Obtaining the Source=
{{Obtaining_The_Source_Code}}

=Get Dependencies=

You will need to install some development packages Spring depends on. Most of these are available using [http://http://www.macports.org/ Macports] (similar to portage / apt-get etc available on various linux distro's)

You will also need to install the [http://developer.apple.com/TOOLS/Xcode/ Xcode developers package] (this requires a free membership to apple's ADC website)

==Full list==

*Programs necessary to build
**Xcode
**cmake (or scons)
**zip
**The usual build toolchain
***gcc ''(comes with Xcode tools)''
***make ''(comes with Xcode tools)''
*Libraries
**SDL
**boost (version 1.35 or later recommended)
***threads
***regex
***signals
***system
**DeviL (IL, ILU)
**OpenAL ''Please check the OpenAL section for MacOSX specific info''
**OpenGL headers (mesa, glew, etc.) ''(comes with Xcode tools)''
**zlib
**freetype
**ogg,vorbis and vorbisfile
*Optional, for bindings and Ais
**Python (2.5)
**Java-SDK ''(pre-installed on OSX)''

==Using Macports==

Once you have downloaded and configured Macports use these commands to download / compile and install the required dependencies :

sudo port install cmake 
sudo port install libsdl 
sudo port install libsdl-framework 
sudo port install boost 
sudo port install boost-jam 
sudo port install libpng #These image libraries might not be needed, but ma save you some headaches 
sudo port install jpeg 
sudo port install tiff 
sudo port install libogg 
sudo port install libvorbis 
sudo port install python25 
sudo port install libdevil # as of October 12th 2009 the Macports install of libdevil (1.6.8-rc2_0) can be broken. If you get errors like /opt/local/include/IL/il.h:505: error: â€˜<anonymous>â€™ has incomplete type while building spring, you'll probably need to install it from source. ) 


If all was successful, you are very close to being able to compile Spring natively!

==Installing libdevil from source==

Make sure that all the other port packages are installed first!
Download the source. Right now 1.6.8-rc2_0 has the bug we're trying to work around, so don't use that one, or earlier versions.

Extract the source code.

Configure it. I used this command.
./configure --enable-png --enable-ILU --enable-ILUT --enable-x86_64 CPPFLAGS="-I/opt/local/include/ -L/opt/local/lib/" LDFLAGS=-L/opt/local/lib/

Make sure you have support for png, jpg, dds, and tga

Make it with "make"

Part way through you'll get an error about malloc.h not being found. To fix it, replace <malloc.h> with <sys/malloc.h>

install with sudo make install

==OpenAL==

After having mountains of problems myself with the OpenAL pre-installed with the Xcode tools, I discovered that it is version 1.0 of OpenAL (not the correct version we want).

Head to your /System/Library/Framework/ folder and delete any trace of OpenAL framework / folders that are there.

[http://kcat.strangesoft.net/openal-releases/openal-soft-1.8.466.tar.bz2 Now download this copy of OpenAL]

Using the terminal, go into the folder where you downloaded openal-soft and pass these commands

bzip2 -d openal-soft-xxxx.tar.bz2 | tar xvf - 
cd openal-soft-xxxx 
cmake . 
make 
make install

All done, now you will have no problems compiling the Sound.cpp file in spring!

=Build And Install=

The build will spew out warnings like the following, which you can safely ignore: 
warning: division by zero 
warning: 'q' may be used uninitialized in this function 

==Removing duplicate libraries==

Make sure that you remove all extra libraries before the first time you call cmake. If not, cmake will make your life a living hell. Check in /usr /usr/local /opt/local and /Library/Frameworks. Also, don't change the location of the source directory, librarys, or includes after calling cmake. If you do change any of the locations you can't just call cmake again. The only way I know to tell it to recompute everything from scratch is this:
*Change to the root of the git tree
*Remove every single visible file.
*Run git reset --HARD

==Using CMake (2.6 or newer)==
This is the only way I have compiled spring successfully so far :

(could someone please add a better way? As I cannot workout how to get xcodebuild to run the "install portion of the make file")

<code><pre>cmake .
make
make install</pre></code>

This will install spring in all the right places to be run from a command line (but don't yet, it compiles an unusable executable, we just needed to get the makefile to install everything to the right place)

Now pass these commands

<code><pre>cmake -G Xcode
xcodebuild</pre></code>

This will have made a folder called "Debug" and will contain a command line program Spring, and Libunitsync.dylib

now to make sure the correct copy of spring runs when you are using the terminal pass the following command

<code><pre>sudo cp spring /usr/local/bin</pre></code>

Now you are ready to ready to play Spring on your MacOSX system!
Enjoy!

=Finalizing installation=

Will update later once I update the Springlobby wiki with all my OSX information!

If you need to contact me, send a PM to '''adso''' on the forums, or catch me in #sy or #springlobby in the lobby chat :)

--[[User:Adso|Adso]] 06:23, 29 August 2009 (UTC)

[[Category:Compiling]]

Spring on MacOSX

2009-10-16T16:57:52Z

Patmo98: Tobi said 32bit builds will sync with 64-bit builds. Cool

Building Spring on MacOSX

2009-10-15T06:15:33Z

Patmo98: Dire warnings about cmake

[[Engine_Development|Development]] < [[Building_spring|Building Spring]] < {{FULLPAGENAME}}

= Duplicate and missing information =

This page is a partial duplicate of [[Spring_on_MacOSX]] but both have unique information.

=Build from source on MacOSX=

'''Guide is for x86/Intel based OSX installs'''

I am hoping that with our efforts on the forum that we can have an .app bundle released everytime spring is updated and that will save most people needing to go through the headache of compiling from source code. But if you must try, then here's the steps to help!

I cannot stress enough that this will most likely only work on Intel based systems at this stage. With my understanding of how unitsync works, it seems like online play will not be possible between PPC and x86 architecture.

=Obtaining the Source=
{{Obtaining_The_Source_Code}}

=Get Dependencies=

You will need to install some development packages Spring depends on. Most of these are available using [http://http://www.macports.org/ Macports] (similar to portage / apt-get etc available on various linux distro's)

You will also need to install the [http://developer.apple.com/TOOLS/Xcode/ Xcode developers package] (this requires a free membership to apple's ADC website)

==Full list==

*Programs necessary to build
**Xcode
**cmake (or scons)
**zip
**The usual build toolchain
***gcc ''(comes with Xcode tools)''
***make ''(comes with Xcode tools)''
*Libraries
**SDL
**boost (version 1.35 or later recommended)
***threads
***regex
***signals
***system
**DeviL (IL, ILU)
**OpenAL ''Please check the OpenAL section for MacOSX specific info''
**OpenGL headers (mesa, glew, etc.) ''(comes with Xcode tools)''
**zlib
**freetype
**ogg,vorbis and vorbisfile
*Optional, for bindings and Ais
**Python (2.5)
**Java-SDK ''(pre-installed on OSX)''

==Using Macports==

Once you have downloaded and configured Macports use these commands to download / compile and install the required dependencies :

sudo port install cmake 
sudo port install libsdl 
sudo port install libsdl-framework 
sudo port install boost 
sudo port install boost-jam 
sudo port install libpng #These image libraries might not be needed, but ma save you some headaches 
sudo port install jpeg 
sudo port install tiff 
sudo port install libogg 
sudo port install libvorbis 
sudo port install python25 
sudo port install libdevil # as of October 12th 2009 the Macports install of libdevil (1.6.8-rc2_0) can be broken. If you get errors like /opt/local/include/IL/il.h:505: error: â€˜<anonymous>â€™ has incomplete type while building spring, you'll probably need to install it from source. ) 


If all was successful, you are very close to being able to compile Spring natively!

==Installing libdevil from source==

Make sure that all the other port packages are installed first!
Download the source. Right now 1.6.8-rc2_0 has the bug we're trying to work around, so don't use that one, or earlier versions.

Extract the source code.

Configure it. I used this command.
./configure --enable-png --enable-ILU --enable-ILUT --enable-x86_64 CPPFLAGS="-I/opt/local/include/ -L/opt/local/lib/" LDFLAGS=-L/opt/local/lib/

Make sure you have support for png, jpg, dds, and tga

Make it with "make"

Part way through you'll get an error about malloc.h not being found. To fix it, replace <malloc.h> with <sys/malloc.h>

install with sudo make install

==OpenAL==

After having mountains of problems myself with the OpenAL pre-installed with the Xcode tools, I discovered that it is version 1.0 of OpenAL (not the correct version we want).

Head to your /System/Library/Framework/ folder and delete any trace of OpenAL framework / folders that are there.

[http://kcat.strangesoft.net/openal-releases/openal-soft-1.8.466.tar.bz2 Now download this copy of OpenAL]

Using the terminal, go into the folder where you downloaded openal-soft and pass these commands

bzip2 -d openal-soft-xxxx.tar.bz2 | tar xvf - 
cd openal-soft-xxxx 
cmake . 
make 
make install

All done, now you will have no problems compiling the Sound.cpp file in spring!

=Build And Install=

The build will spew out warnings like the following, which you can safely ignore: 
warning: division by zero 
warning: 'q' may be used uninitialized in this function 

==Removing duplicate libraries==

Make sure that you remove all extra libraries before the first time you call cmake. If not it will make your life a living hell. Check in /usr /usr/local /opt/local and /Library/Frameworks. Also, don't change the location of the source directory, librarys, or includes after calling cmake. If you do change any of the locations you can't just call cmake again. There is probably a way to tell t to recompute everything from scratch, but if there is, I haven't found it yet.

==Using CMake (2.6 or newer)==
This is the only way I have compiled spring successfully so far :

(could someone please add a better way? As I cannot workout how to get xcodebuild to run the "install portion of the make file")

<code><pre>cmake .
make
make install</pre></code>

This will install spring in all the right places to be run from a command line (but don't yet, it compiles an unusable executable, we just needed to get the makefile to install everything to the right place)

Now pass these commands

<code><pre>cmake -G Xcode
xcodebuild</pre></code>

This will have made a folder called "Debug" and will contain a command line program Spring, and Libunitsync.dylib

now to make sure the correct copy of spring runs when you are using the terminal pass the following command

<code><pre>sudo cp spring /usr/local/bin</pre></code>

Now you are ready to ready to play Spring on your MacOSX system!
Enjoy!

=Finalizing installation=

Will update later once I update the Springlobby wiki with all my OSX information!

If you need to contact me, send a PM to '''adso''' on the forums, or catch me in #sy or #springlobby in the lobby chat :)

--[[User:Adso|Adso]] 06:23, 29 August 2009 (UTC)

[[Category:Compiling]]

Template:Obtaining The Source Code

2009-10-15T05:51:55Z

Patmo98: Another typo

=== Current (0.80.4) ===
'''(For playing Spring online)'''
{{Template:Tarballs}}

=== Development Sources from Git ===
'''(Bleeding-edge, unstable code for Development and Testing)'''

'''[http://github.com/spring/spring/tree/master Spring project page at github]'''

Git clone URL for the master repo: '''git://github.com/spring/spring.git'''

For serious developers. This will also allow you to make a patch out of the changes you make to the code, and send it to one of the developers with repository access.

Assuming the GIT-commandline client is installed, you can clone the repository with

<code><pre>git clone git://github.com/spring/spring.git</pre></code>

and update it with

<code><pre>git pull</pre></code>

If github is unavailable or slow, there is a mirror (updated twice a day):
'''git://springrts.com/spring'''

'''There's a branch that's for MacOS development. You can find it at git://github.com/yokosou/spring/spring.git. If you want to include the recent changes in the main branch, you can checkout and merge both like this'''

<code><pre>git clone git://github.com/yokosou/spring.git
cd spring
git pull
git remote add official git://github.com/spring/spring.git
git fetch official
git pull official master</pre></code>

Building Spring on MacOSX

2009-10-14T21:39:57Z

Patmo98: Minor formatting fixes

[[Engine_Development|Development]] < [[Building_spring|Building Spring]] < {{FULLPAGENAME}}

= Duplicate and missing information =

This page is a partial duplicate of [[Spring_on_MacOSX]] but both have unique information.

=Build from source on MacOSX=

'''Guide is for x86/Intel based OSX installs'''

I am hoping that with our efforts on the forum that we can have an .app bundle released everytime spring is updated and that will save most people needing to go through the headache of compiling from source code. But if you must try, then here's the steps to help!

I cannot stress enough that this will most likely only work on Intel based systems at this stage. With my understanding of how unitsync works, it seems like online play will not be possible between PPC and x86 architecture.

=Obtaining the Source=
{{Obtaining_The_Source_Code}}

=Get Dependencies=

You will need to install some development packages Spring depends on. Most of these are available using [http://http://www.macports.org/ Macports] (similar to portage / apt-get etc available on various linux distro's)

You will also need to install the [http://developer.apple.com/TOOLS/Xcode/ Xcode developers package] (this requires a free membership to apple's ADC website)

==Full list==

*Programs necessary to build
**Xcode
**cmake (or scons)
**zip
**The usual build toolchain
***gcc ''(comes with Xcode tools)''
***make ''(comes with Xcode tools)''
*Libraries
**SDL
**boost (version 1.35 or later recommended)
***threads
***regex
***signals
***system
**DeviL (IL, ILU)
**OpenAL ''Please check the OpenAL section for MacOSX specific info''
**OpenGL headers (mesa, glew, etc.) ''(comes with Xcode tools)''
**zlib
**freetype
**ogg,vorbis and vorbisfile
*Optional, for bindings and Ais
**Python (2.5)
**Java-SDK ''(pre-installed on OSX)''

==Using Macports==

Once you have downloaded and configured Macports use these commands to download / compile and install the required dependencies :

sudo port install cmake 
sudo port install libsdl 
sudo port install libsdl-framework 
sudo port install boost 
sudo port install boost-jam 
sudo port install libpng #These image libraries might not be needed, but ma save you some headaches 
sudo port install jpeg 
sudo port install tiff 
sudo port install libogg 
sudo port install libvorbis 
sudo port install python25 
sudo port install libdevil # as of October 12th 2009 the Macports install of libdevil (1.6.8-rc2_0) can be broken. If you get errors like /opt/local/include/IL/il.h:505: error: â€˜<anonymous>â€™ has incomplete type while building spring, you'll probably need to install it from source. ) 


If all was successful, you are very close to being able to compile Spring natively!

==Installing libdevil from source==

Make sure that all the other port packages are installed first!
Download the source. Right now 1.6.8-rc2_0 has the bug we're trying to work around, so don't use that one, or earlier versions.

Extract the source code.

Configure it. I used this command.
./configure --enable-png --enable-ILU --enable-ILUT --enable-x86_64 CPPFLAGS="-I/opt/local/include/ -L/opt/local/lib/" LDFLAGS=-L/opt/local/lib/

Make sure you have support for png, jpg, dds, and tga

Make it with "make"

Part way through you'll get an error about malloc.h not being found. To fix it, replace <malloc.h> with <sys/malloc.h>

install with sudo make install

==OpenAL==

After having mountains of problems myself with the OpenAL pre-installed with the Xcode tools, I discovered that it is version 1.0 of OpenAL (not the correct version we want).

Head to your /System/Library/Framework/ folder and delete any trace of OpenAL framework / folders that are there.

[http://kcat.strangesoft.net/openal-releases/openal-soft-1.8.466.tar.bz2 Now download this copy of OpenAL]

Using the terminal, go into the folder where you downloaded openal-soft and pass these commands

bzip2 -d openal-soft-xxxx.tar.bz2 | tar xvf - 
cd openal-soft-xxxx 
cmake . 
make 
make install

All done, now you will have no problems compiling the Sound.cpp file in spring!

=Build And Install=

The build will spew out warnings like the following, which you can safely ignore: 
warning: division by zero 
warning: 'q' may be used uninitialized in this function 

==Using CMake (2.6 or newer)==
This is the only way I have compiled spring successfully so far :

(could someone please add a better way? As I cannot workout how to get xcodebuild to run the "install portion of the make file")

<code><pre>cmake .
make
make install</pre></code>

This will install spring in all the right places to be run from a command line (but don't yet, it compiles an unusable executable, we just needed to get the makefile to install everything to the right place)

Now pass these commands

<code><pre>cmake -G Xcode
xcodebuild</pre></code>

This will have made a folder called "Debug" and will contain a command line program Spring, and Libunitsync.dylib

now to make sure the correct copy of spring runs when you are using the terminal pass the following command

<code><pre>sudo cp spring /usr/local/bin</pre></code>

Now you are ready to ready to play Spring on your MacOSX system!
Enjoy!

=Finalizing installation=

Will update later once I update the Springlobby wiki with all my OSX information!

If you need to contact me, send a PM to '''adso''' on the forums, or catch me in #sy or #springlobby in the lobby chat :)

--[[User:Adso|Adso]] 06:23, 29 August 2009 (UTC)

[[Category:Compiling]]

Building Spring on MacOSX

2009-10-14T21:36:05Z

Patmo98: Lots of changes

[[Engine_Development|Development]] < [[Building_spring|Building Spring]] < {{FULLPAGENAME}}

= Duplicate and missing information =

This page is a partial duplicate of [[Spring_on_MacOSX]] but both have unique information.

=Build from source on MacOSX=

'''Guide is for x86/Intel based OSX installs'''

I am hoping that with our efforts on the forum that we can have an .app bundle released everytime spring is updated and that will save most people needing to go through the headache of compiling from source code. But if you must try, then here's the steps to help!

I cannot stress enough that this will most likely only work on Intel based systems at this stage. With my understanding of how unitsync works, it seems like online play will not be possible between PPC and x86 architecture.

=Obtaining the Source=
{{Obtaining_The_Source_Code}}

=Get Dependencies=

You will need to install some development packages Spring depends on. Most of these are available using [http://http://www.macports.org/ Macports] (similar to portage / apt-get etc available on various linux distro's)

You will also need to install the [http://developer.apple.com/TOOLS/Xcode/ Xcode developers package] (this requires a free membership to apple's ADC website)

==Full list==

*Programs necessary to build
**Xcode
**cmake (or scons)
**zip
**The usual build toolchain
***gcc ''(comes with Xcode tools)''
***make ''(comes with Xcode tools)''
*Libraries
**SDL
**boost (version 1.35 or later recommended)
***threads
***regex
***signals
***system
**DeviL (IL, ILU)
**OpenAL ''Please check the OpenAL section for MacOSX specific info''
**OpenGL headers (mesa, glew, etc.) ''(comes with Xcode tools)''
**zlib
**freetype
**ogg,vorbis and vorbisfile
*Optional, for bindings and Ais
**Python (2.5)
**Java-SDK ''(pre-installed on OSX)''

==Using Macports==

Once you have downloaded and configured Macports use these commands to download / compile and install the required dependencies :

sudo port install cmake 
sudo port install libsdl 
sudo port install libsdl-framework 
sudo port install boost 
sudo port install boost-jam 
sudo port install libpng #These image libraries might not be needed, but ma save you some headaches 
sudo port install jpeg 
sudo port install tiff 
sudo port install libogg 
sudo port install libvorbis 
sudo port install python25 
sudo port install libdevil # as of October 12th 2009 the Macports install of libdevil (1.6.8-rc2_0) can be broken. If you get errors like /opt/local/include/IL/il.h:505: error: â€˜<anonymous>â€™ has incomplete type while building spring, you'll probably need to install it from source. ) 


If all was successful, you are very close to being able to compile Spring natively!

==Installing libdevil from source==

Make sure that all the other port packages are installed first!
Download the source. Right now 1.6.8-rc2_0 has the bug we're trying to work around, so don't use that one, or earlier versions.

Extract the source code.

Configure it. I used this command.
./configure --enable-png --enable-ILU --enable-ILUT --enable-x86_64 CPPFLAGS="-I/opt/local/include/ -L/opt/local/lib/" LDFLAGS=-L/opt/local/lib/

Make sure you have support for png, jpg, dds, and tga

Make it with "make"

Part way through you'll get an error about malloc.h not being found. To fix it, replace <malloc.h> with <sys/malloc.h>

install with sudo make install

==OpenAL==

After having mountains of problems myself with the OpenAL pre-installed with the Xcode tools, I discovered that it is version 1.0 of OpenAL (not the correct version we want).

Head to your /System/Library/Framework/ folder and delete any trace of OpenAL framework / folders that are there.

[http://kcat.strangesoft.net/openal-releases/openal-soft-1.8.466.tar.bz2 Now download this copy of OpenAL]

Using the terminal, go into the folder where you downloaded openal-soft and pass these commands

bzip2 -d openal-soft-xxxx.tar.bz2 | tar xvf - 
cd openal-soft-xxxx 
cmake . 
make 
make install

All done, now you will have no problems compiling the Sound.cpp file in spring!

=Build And Install=

The build will spew out warnings like the following, which you can safely ignore:
warning: division by zero
warning: 'q' may be used uninitialized in this function

==Using CMake (2.6 or newer)==
This is the only way I have compiled spring successfully so far :

(could someone please add a better way? As I cannot workout how to get xcodebuild to run the "install portion of the make file")

<code><pre>cmake .
make
make install</pre></code>

This will install spring in all the right places to be run from a command line (but don't yet, it compiles an unusable executable, we just needed to get the makefile to install everything to the right place)

Now pass these commands

<code><pre>cmake -G Xcode
xcodebuild</pre></code>

This will have made a folder called "Debug" and will contain a command line program Spring, and Libunitsync.dylib

now to make sure the correct copy of spring runs when you are using the terminal pass the following command

<code><pre>sudo cp spring /usr/local/bin</pre></code>

Now you are ready to ready to play Spring on your MacOSX system!
Enjoy!

=Finalizing installation=

Will update later once I update the Springlobby wiki with all my OSX information!

If you need to contact me, send a PM to '''adso''' on the forums, or catch me in #sy or #springlobby in the lobby chat :)

--[[User:Adso|Adso]] 06:23, 29 August 2009 (UTC)

[[Category:Compiling]]

Building Spring on MacOSX

2009-10-14T21:26:55Z

Patmo98: Reformatting

Mac

2009-10-14T20:57:44Z

Patmo98: Evedently I don't know how to make links either

[[Spring_on_MacOSX]] 

If you know how to make a redirect in a wiki, please change this into one.

[[Category:Source development]]

Mac

2009-10-14T20:57:03Z

Patmo98: Way too old to bother saving. Should be a redirect, but I don't know how to do that.

[[http://springrts.com/wiki/Spring_on_MacOSX]] 

If you know how to make a redirect in a wiki, please change this into one.

[[Category:Source development]]

Template:Obtaining The Source Code

2009-10-12T21:35:48Z

2006-01-15T04:15:37Z

Patmo98:

The following pages discuss or disclose tips, strategy & tactics.

'''General TA Spring'''

[[Rushing]]

[[Spring guide!]]

[[Base building tips]]

[[Spring for RTS Players]]

[[Spring Replays]]

[[Mods, and their strategies/tactics]]

[[Advanced_Strategy_Discussion]]

Return to [[Main_Page]]

AI:NTAI

2005-12-21T06:10:01Z

Patmo98: Spelling

[http://img434.imageshack.us/img434/6500/screen0898vk.jpg http://img432.imageshack.us/img432/8080/thumb0896lz.jpg][http://img393.imageshack.us/img393/536/screen0920qb.jpg http://img432.imageshack.us/img432/7251/thumb0924ca.jpg][http://img393.imageshack.us/img393/8756/screen0903up.jpg http://img432.imageshack.us/img432/5011/thumb0903nl.jpg]

NTAI is an [[AI]] being developed by [http://taspring.clan-sy.com/phpbb/profile.php?mode=viewprofile&u=73 Alantai Firestar]. It is arguably better that [[AI:JCAI|JCAI]], with less crashes and a better performance when the two AI's battle each other.

NTAI shares several components in collaboration with ZcAIn, most noticeably the metal extractor algorithm. NTAI is also the successor to the fabled attempt to create TAI. In time NTAI will become the TAI describe at darkstars.co.uk. Of all the AI's TAI+NTAI has the most theory and speculation available to read.

While NTAI works, it may not be as effective as it could be due to the fact it was initially created in a 30 hour all nighter coding/playtesting session.

Current version: 2.0

=== Links ===
* [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2487 NTAI Forum Thread]
* [http://sourceforge.net/project/showfiles.php?group_id=141993 NTAI Downloads (Sourceforge)]
* [http://www.darkstars.co.uk NTAI site]

Back to [[AI]]

Using Spring

2005-12-21T00:54:23Z

Patmo98: /* Cloak(K) */

More Exaustive Decription of Contols, Interface and Features. For Basic information, check the most current [http://cvs.sourceforge.net/viewcvs.py/*checkout*/springrts/taspring/README.html README.html] (should be mirrored [[Readme|here]])or [[Getting_Started]]. For an introduction to the srategy and overall gameplay in XTA (and most mods based on the orriginal Cavedog units) check out the [[Spring_guide%21]]

For more advanced/current information check the most recent [http://taspring.clan-sy.com/changelog.txt changelog] or the [http://taspring.clan-sy.com/phpbb/ taspring/spring forums].

=Camera Controls=
There are four camera modes in Spring. To change camera modes use CTRL+Middle Button (Mouse 3), CTRL+J or CTRL+Backspace (Also SHIFT+[Mouse 3,J or Backspace]). Middle button, Backspace or J toggle "free look" mode for the current camera view. (expand idividual controls for each camera mode)

==Camera Modes==

There are four different camera modes in Spring. Everyone likes a different one. Try them all out to decide what you like.

===FPS Style===
This is the default view. The camera is controlled just like in a First Person Shooter. Use arrow keys to fly forward/backward and strafe left/right. Hold the middle mouse button to aim the camera. Use the scroll wheel to zoom in and out.

This is the easiest camera to position. However, it can get quite tedious in the middle of a battle trying to control the camera. Its good for screenshots and FPS junkies.

===Classic Overhead(TA) Style===
Exactly the same view as OTA had. It has a fixed height above the ground, but allows you to zoom in and out. Use the arrow keys or move the mouse to the edge of the screen to pan around the map. The scroll wheel zooms in and out. Holding the middle mouse button also pans around the map.

This is the easiest view for OTA players to use. It functions exactly the same as the OTA camera, so no new tricky controls are needed to properly enjoy the game. But there is no way to tilt the camera, so this view does not really show off the full glory of the Spring engine. It is the favorite view mode for most people, as most people play OTA.

===Total War Style===
The same camera system as seen in the (Rome:?)Total War game. It runs at a fixed height above the ground, which is not changable. Use the arrow keys or move the mouse to the edge of the screen to pan around the map. Scrolling the scroll wheel tilts the camera. Putting the mouse in the top corners of the screen rotates the view. Holding down the middle mouse button pans around the map.

Good for those familiar with the Total War games. But again it does not allow for full freedom in the movment, so does not show off the engine as much as it could do.

===Rotatable Overhead Camera===

This is a new camera system invented by the SY's. It has a fixed height, but you can change this height by scrolling. Use the arrow keys to pan around the map. The scroll wheel moves the camera up and down vertically. Holding the middle mouse button aims the camera.

This is perhaps the best camera, as it allows for totally free movement and aiming, but with some handy restrictions on the height. It is the second most popular view behind OTA view.

===FPS "Mode" (C)===
Press 'C' to toggle "First Person Shooter Mode".

Controls:
*Up Arrow: Move in the direction the legs are facing
*Left Arrow: Rotate Legs to the left
*Right Arrow: Rotate Legs to the right
*Mouse: Aim default gun (may lock onto annoying targets such as the ground)
*Left Mouse Button: Shoot whatever guns the engine has decided to let you shoot
*Right Mouse Button: Free Fire Mode, the AI will aim and fire for you.

==General Function Keys==

For the most part the function keys control what the camera sees, so they are listed here for lack of a better place for them.

*'''F1''': Toggles Contour Markings On/Off. Color coded contour markings of the map height. One iteration through the colors (ie: red-green-blue-red) is 32 units high.
*'''F2''': Toggles Path map On/Off. The path map works the following way:
**'''Mobile Unit Selected''': If you have a mobile unit selected, then the pathmap shows where that specific unit can move (green) and where it cant (red). The greener the map, the better the unit can walk on that area. Zones that cant be walked or driven on are always solid red.
**'''Builder Selected''': When you have a builder selected, and click on a building in its build menu (i.e. a Kbot lab), the path map will show you where you can build that building. Its fairly easy to understand, with the green zones representing buildable areas, and the red zones representing the areas where you cannot build.
*'''F3''': Moves the camara to the position of the last message. Messages can be from units, or alerts on the minimap from your allies.
*'''F4''': Toggles Metal Map On/Off. If the map is green, there is metal there. if the map is black, there is no metal. If the map is white, there is lots of metal and it would be a good strategic place to hold.
*'''F5''': Toggles the GUI On/Off. Good for taking screenshots.
*'''F6''': Toggles Sound On/Off. Good for when your D-Gunning kroggies XD
*'''F7''': Toggles the Dynamic sky. If the game is running slowly, try turning this off to speed it up a little bit.
*'''F8''': Save the Game. Not sure exactly how this works, or how you then load a game again, but the button is here for using.
*'''F9''': Show/Hide Unit Status. Unit Status bars are: Health, Building percentage, experience, and group numbers.
*'''F11/F12''': Screenshots. Takes a screenshot and saves it to TASpring/Screenshot###.jpg, where ### is the number of the screenshot.
'''Note:''' F10 is not bound to any control, but its good idea to map it to CreateVideo instead of 'v'. Edit the TASpring/uikeys.txt and replace "bind 'v' CreateVideo" with "bind f10 CreateVideo"

==Snapping/Panning Camera to a Specific View==
Right mouse button (MOUSE2) click on the mini-map to snap the center of the view to that point on the map, right click and drag to move the camera around the map.

Press F3 to snap the camera view to the point of the last "message" (aka commander is under attack, player 1 has placed a point: look here!).

Press T to lock the camera to track the currently selected units. (move the camera manually to stop the tracking)

=Selections/Groups/Group Commands/Group AI=

==The Selection Editor==

'''SelectionEditor.exe''' is a program installed in your install directory, which is used for editing your '''selectkeys.txt''' configuration file, allowing you to make your own shortcut keys for selecting/filtering selection.

[http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2190 This] forum topic that should be duplicated here, with cleaning up and additions made... and permission probably.

==Default Selection Controls==

===Selecting/Deselecting Units===
Unless you have issued a pending command(see [[#Left Mouse Control (Mouse 1)|Left Mouse Control (Mouse 1)]]), left-clicking(Mouse Button 1) a unit will clear the current selection and select the left-clicked unit, if a spot with no valid selection is clicked(empty space, ground, unowned units), the current selection will be cleared. Left-clicking and dragging will draw a box, any units within this box will be selected when you release the mouse button.

Shift+Left-clicking(including dragging a select box), unless you have a pending command, will add units to the current selection.

CTRL+Left-clicking (including dragging a select box), unless you have a pending command, will remove units from the current selection.

Unless the unit is in a group Double-left-clicking will select all visible(camera bounds) units of the clicked type(Shift+Double-left-clicking will add all units of the double-clicked unit's type to the current selection).

CTRL+Z is a shortcut (which can be eddited in Selection Editor) to select all owned units of the current selected type. For example, if a peewee and a brawler are selected, all peewees and brawlers will be selected.

CTRL+A is a shortcut (which can be eddited in Selection Editor) to select all owned units.
 
<table><tr><td>"Tooltips" are displayed in the bottom left of the current interface, if units are selected this information is the sum of all information about the selection (aka, select a bank of 5 solar collectors and it will show the total health and total energy being produced). If you mouse-over a "build-pic" in a units command list it will show you the costs and stats associated with the unit represented by the "build-pic". If you have no selection, the tooltip will show information about what your mouse is over at that time (unit stats if it's a unit, otherwise information about the terrain).
</td><td>
[[Image:CommanderTooltip.png|thumb|120px|Commander Selected]]
[[Image:TerrainTooltip.png|thumb|120px|Terrain Hover (No Units Selected)]]
</td><td>
[[Image:BuildMexTooltip.png|thumb|120px|Metal Extractor Buildpic Hover]]
[[Image:RepairTooltip.png|thumb|120px|Repair Command Hover]]</td></tr></table>
[[Image:PeeweeGroupTooltip.png|frame|center|Group of units Selected]]

===Basic Unit Groups===

Spring supports what could be called quick control groups. Basically you can assign the currently selected units to a numbered group with CTRL+# (where # is a number key) which will put that number(#) above all selected units, then later, you can quickly select these units by pressing SHIFT+#.

If a factory is set to a group, all units built by this factory will also be automatically assigned to this group.

Units can only be in one group at a time, so assigning a new group number to a unit will remove it from it's current group.

Assigning a unit to a group overides normal double-clicking behaviour, if you double-click a member of a group, it's group is selected instead of the units of the same type in range.

Also note, when you CTRL+# a group of units, the old group with that number will no longer exist. Therefore if you intend to add aditional units to a group, you first SHIFT+# the current members and then add (by holding SHIFT) the additional units to the selection group and the use CTRL+# to re-assign all the units to that group. A shortcut for this is holding down both SHIFT and CTRL and pressing a number(#) to add the current selection to that group, and select the entirety of that new group.

===Advance Unit Groups with GroupAI===

It is possible to assign groups 10 and up for automatic control control.

see [[#Select_AI.28CTRL.2BQ.29|Select AI(CTRL+Q)]], to create groups 10 and above.

see [[#Assign/Select_Current_Group(Q)|Assign/Select Current Group(Q)]], to select and add units to these groups.

=Issuing Orders/Building=

===Left Mouse Control (Mouse 1)===
As covered in [[#Selecting/Deselecting Units|Selecting/Deselecting Units]], left clicking is the primary control for selecting units. If, however, a pending order is issued using the menu that appears on the left side of the screen or using a Hotkey, the mouse pointer will change to a symbol representing this action. If there is a pending order and you left click on a valid target for the action the selcted units will perform this action on that target, otherwise the units will "do their best" to perform the action(which could mean just cancelling the Order.

The menu will show all available commands for all selected units, except for wait and self destruct, in the menu, mousing over a menu item will also display the Tooltip for this item.

===Right Mouse Control (Mouse 2)===
Right clicking will always give the selected units the default action for the target, if the order is invalid for some members of the group, it may or may not choose a suitable action for those units to perform.

===Queueing Orders===

Use Shift to queue orders. Queueing orders means that you can tell a unit, or a group of units to do multiple tasks, and they will go off and do them with out any more input from you. Just say you want a Construction Vehicle to build a line of defences around your base. Select the defence building you want, hold shift and click around a few times. The construction vehicle will now go and build (or try to build) all of the selected structures, and you can just sit back and watch. You can queue each and every type of order there is in game, with no limits. It would be possible (but not very smart) to order your commander to build a whole base for you while you go off and have lunch!

If you have a unit selected, holding shift will show green outlined "ghosted" building for all units the selection has been ordered to build and simple green squares for all buildings that are queued for other units. Also, when holding shift, a path (white line) will be shown representing the selected units order queue (even if there is only one order for that unit; aka a line to the building the unit has been ordered to build and the ghosted building).

You can remove an order from the order queue by holding shift and repeating the same order. This doesn't work very well on area or movement type orders but can be useful for cancelling the construction of an un-needed building.

Another use for this, is for issuing complicated movement orders. Say you wan your army to attck your enemy, but you want to attack from the side, where they are their weakest. just issuing one move command to attack the side of their base would send our units moving THROUGH your enemys base to try to get to the side. This is not very good. But if you tell your units to move to a location AWAY from the base and them attack from the side, by queuing up two or more move commands, this problem can be successfully avoided. Or you could tel your units to attack certain buildings in a certain order, for instance attack all the outlying metal extracors, and them go for the power plants in the base, they will follow these orders oblivious to anything else, while you go in and attack the other important things.

learing how to sucessfully queue orders is a vital part of any game, and you will be lost with out it.

==Building Buildings==

When a contruction unit is selected you will see images in it's command list(menu on the left) representing the buildings that it can build (buildpics). Mousing over this buildpic will update the tooltip to show information about the structure. Clicking on a structure's buildpic will select it for contruction. If multiple units are selected, all available structures (and mobile units) will appear in the command list. Choosing to build a building when you have multiple units selected will usually assign all units to help build those buildings if this is a valid command.

===Build (select structure + left-click)===

Builds whatever structure selected in the location clicked by moving the builder unit selected there and nanolathing it into existance. All Queued orders are cancelled

===Build Queue (select structure + shift + left-click)===

Puts the selected structure and location into your unit's order queue.

===Build Line (select structure + shift + left-hold-drag)===

Adds a straight line of the selected structure into your unit's build queue starting where your right hold first depressed and ending where you lift the key.

===Build Box (select structure + shift + alt + left-hold-drag)===

Adds a filled in square or rectangle box of the selected structures to your unit's build queue. The location your first depressed rightmouse is one cornered border and the location you release is the opposing corner. If you move the mouse straigt up your box will look like a vertical line.

===Space Build (shift + mouse5/mouse4)===

Gives your line and/or box structure queues an ammout of spacing between structures (default spacing starts at no space). Each click of the spacing expand button gives you an extra LLTbased size space in between each structure on all 4 dimentions. Similarly, each click of the spacing contract button removes that ammout of space. You cannot remove spaces when structures are already placed with no spacing between them.

==Building Mobile Units (Building with Factories)==

Click on the picture of the unit you want to queue up for building. You can queue up many units this way.

Hold SHIFT while clicking a buildpic to order 5 units at one time, hold CTRL while clicking to order 20, hold CTRL+SHIFT while clicking to order 100. Hold ALT while clicking a buildpic to cancel the current construction and add the clicked unit to beginning of the queue (starting the constuction of that unit immediately). Right clicking a buildpic will cancel 1,5,20 or 100 orders for that unit by the same combination of SHIFT and/or CTRL metioned before.

Assigning a group number to a factory will cause the factory to pass this group number to the units it builds.

You can give factories a Move, Guard, or other order and the factory will pass it on to the units it builds. YOu can use this to choose a better place for new units to go after being built, or to send them straight into construction or a battle without micromanaging them. This includes assigning queued orders (for example: multiple move points to get a unit out of the base in a straight line and then a guard repair order on a specific large unit under construction and then a guard order back on the orriginal factory to increase build speed).

Construction/Repair units can be assigned to guard a factory to increase the speed of production for each of the units the factory makes.

==Commands and Defaults and Hotkeys==
It is assumed that if a unit does not have an ability it will not be it's default action, priorities have been noted.
===Active State (X)===
This command toggles the active state of a unit.
If a unit can be turned off this will usually stop it's prodution and/or use of energy and/or metal and/or stop it from doing something and/or change it's stats.
For example, turning off a radar jamming building would make it stop drawing power and prevent it from jamming radar, or turning off a solar collector would stop it from producing power and cause it to "close up" increasing it's armor.
This behaviour is unit-scriptable so it could technically do anything the designer of the unit wants it to do.

===Attack(A)===
Orders the unit to attack the target or location. If ordered to attack a unit, the selected unit or building will keep firing at the targeted unit/building until it is dead. If the targeted unit moves out of range, or out of sight(sp?), the selected unit will move to target the targeted unit again. If ordered to attack ground, the unit will never stop until told to do so by the user. Note that units automatically attack any visible enemy units inside their range, and will pursue them(depending on their Move State (see below)) to a certain distance before returning to their selected location.

===Capture===
The unit will move up to the targeted unit or building and attempt to convert it to your team. So if the enemy has built a Geothermal power plant , and forgotten to protect it, grab a near by construction unit and try to capture it! Note that this takes quite a while, and it is not a good idea to try to capture a unit that is shooting at you. The closer the unit is to 0 health the faster it will be captured. Be careful to set your Commander's [[#Fire State|fire state]] to "hold fire" if you are trying to capture a unit with him, as you will likely detroy the target before it is captured.

===Cloak(K)===
Makes a unit inivisble to the enemys units. Enemy units will not be able to shoot a unit while it is cloaked, but can still shoot it if it is on radar(I think?). Note that this uses an immense amount of energy, and units uncloak for a few seconds when they shoot. This means that you might want to set the unit to Hold Fire, so the unit doesn't accidentally reveal itself. Cloaking a unit also causes atacking units to lose their target lock.

===DGun(D)===
Disintegrator Gun. A weapon held by the commander. It is a very powerful gun that will kill ANY unit in game. Use it in early game to ward off rushes, or against super units like the Krogoth, or the Goliath. Be careful, as it also destroys your units and buildings at the same time! Uses alot of energy to fire, so make sure you have the required energy before attmpting this, cause if it does not work, your commander will be a sitting duck.

===Fire State===
Fire States are fairly simple to work out, and are fairly self explanatory. There are three different states, each with their advantages and disadvantages.

==== Fire at Will ====
This is the default setting for all new units. It makes units fire at any visible enemy unit within its range. It is good for general destruction.

==== Hold Fire ====
This makes units never fire unless ordered to. Even if they are attacked, they will not do anything. THis is good for sneaking units around the back of a base, as they will not draw any attention to themselfs.

==== Return Fire ====
Units only fire at untis that shoot at them. Again, this is good for sneak attacks, but add that little bit more of self defence to them.

===Guard(G)===
The current selection will "guard" the target owned or allied unit. 
When a unit is order to guard another guarding unit it will:

1) Any unit that is order to guard another will attempt to follow it's target anywhere.

2) The Guarding unit will Defend the target if it becomes threatened and the guard has weapons.

3) It will also Repair if the target if it's damaged and the guard has repair capabilities.

4) Or it will Assist in any constructions the target is working on, if the guard can at least repair. This also applies to guarding units capable of repairing who are assigned to guard a factory.

5) A guarding unit will: Repair a unit that has been just resurrected (if capable). But it will not attempt to assist in the actual resurrection, inspite of the guard's capabilities.

6) If say 3 units were each told to guard eachother such that: Unit 1 guards Unit 2, Unit 2 guards Unit 3, and Unit 3 is told to build or repair or attack or whatever. Units 1 and 2 would also join unit 3 in doing what it was ordered to do.

===High Trajectory===
If this option is available, click the button to toggle this state. 
A unit with High Trajectory mode enabled will shoot almost vertically, allowing it to shoot over hills as well as other units and masking the direction/source of the shot. 
Using this mode reduces accuracy greatly and also the increased distance of the higher trajectory will increase the amount of time a shot will take to reach it's target. 
===Move(M)===
There are 4 ways to move a group of units in Spring:

1) The usual move to point (works for single units or groups, pretty standard.)

2) Holding down on ctrl while giving a move order issues a "Move in formation" command. In this case, formation means whatever formation or configuration the units were in when they were given the order.

3) Holding down Alt during a move command issues a "Move into a square". Units will try to move into a nice organised formation. However, this rarley ever works, as units tend to shove each other out of the way when trying to get into position.

4) Click and drag at the waypoint and it issues a "Move to this line" command. (In this case the line can be oriented however the user wants. The shorter the line the deeper the back the units will line up. And by contrast the longer the line the more the units will line up along with it. If there's enough units in the group they will form double or even triple lines, which may cause some shoving as stated in #3.)

'''Notes:''' Certain formation commands might not work on every type of aircraft. 
By turning on [[#Repeat|Repeat]], units will move back into formation when shoved out of position. However, this should be used with caution, as it can lead to problems when trying to move units later 
Right clicking with a unit selected is usually as good as pressing the "M" key if the selected point doesn't have any objects at that location.

===Move State===

===Patrol(P)===
A unit given a command to patrol will move back and forth between its current position and the taget location. Holding CTRL when giving a patrol command to a selection with more then one unit will cause the units to move to a location relative the the target point compared to the distance of the unit from the center of the selection. Holding SHIFT while issueing a series of patrol orders will cause the unit to repeat this command, moving from current location to the targets and "circle around" through the points on the queued path.

When a unit is patroling it will do whatever it can to "help out" along the path of it's patrol route. How far it will go out of it's designated route is partially defined by line of sight, radar coverage, [[#Move State|move state]], and [[#Fire State|fire state]].

Examples of Patrol Behaviour:
*If a unit that can repair patrols within range of a damaged (or under contsruction) owned or allied unit, the patrolling unit will repair the damaged unit.
*If a unit that can attack patrols within range of an enemy it will attack the enemy unit.

===Reclaim(E)===

Reclaiming will break down something and give you the metal/energy it is worth. Only certain units (namely, construction units and the Commander) have reclaim capabilities. Wrecks, enemy units, features, and your own units are reclaimable. Energy and metal will be added to storage when reclaiming process is complete.

====Default Behavior====
Simply clicking on a feature, a wreck, or an enemy unit with a construction unit will reclaim it by default. Dragging as an area command draws a circle in which all valid objects will be reclaimed.

Assigning multiple units to reclaim a target will increase the speed at which the target is reclaimed.

===Repair(R)===
When repairing a damaged unit, uses a percentage of the metal and energy costs associated with a damaged unit to increase the speed at which a unit regains health. When repairing a unit that is still being constructed the unit will help build the target, increasing the speed at which the unit is completed.
The repair command is cancelled when the target's health reaches 100%, so if a unit under construction is damaged the repair command will complete the building of the target and then continue to repair until the unit is at full health.
Valid targets are any damaged units(need to check but I believe this includes enemy units) and units currently being constucted.
Default behaviour for owned and ally units that are not at full health, including units being constructed by other units and factories.
The more units that are assigned to repair another unit, the faster the unit will be constructed/restored to full health, but the energy and metal costs will increase accordingly.

===Assign/Select Current Group(Q)===
This key has a double function.

If you have one unit belonguing to a group selected, when pressing Q it will select all the units that belong to this group.

If several units are selected, and one belongs to any group, then, when pressing Q it will assign ALL the selected units to this group, and after that will select the group.

It works with AI groups aswell as user generated ("tactical"?) groups.

See [http://taspring.clan-sy.com/wiki/Using_Spring#Default_Selection_Controls Default selection Controls] for more info on groups.

===Repeat===
Moves any orders that have been completed to the back of the order queue. For instance, If you tell a unit to more to one side of the base, and then to the other side of the base, it would keep going back and forwards forever, because when it completed the first move command, it would place that command at the back of the queue again. This is most usefull when building units. If you want a factory to continuously pump out a Sampson, then a Flash, then two Stumpy's, turn on repeat, and watch the units pump out!

===Restore===
Drag an area of terrain to restore the terrain to it's original height if it has been "deformed"(damaged by explosions or flattened by the contruction of a building).

===Resurrect===
In XTA only the Arm F.A.R.K. and the Core necro can use this order. Use this to ressurect dead units. If you see some wreakage on the map from some dead units, select a FARK or Necro and ressurect the dead units to have them fight along side your army. A good way to gain the upper hand later in game is to ressurect your opponents army after a battle. This does take a lot of energy and metal(half as much as building the unit originally), and ressurected units will start on 1 health, so are very vunerable. 
Ressurect is the default order for corpses from destroyed units, this unfortunately includes wreackage that can't acctually be resurrected.(Tip: if you cannot tell what unit the wreakage was then most likely you cannot resurrect it) 
Dragging this order as an area will cause all selected units to ressurect all valid targets in that area. If multiple units are given a common ressurect order, the target will be resurrected faster but only one of them(probably the one the engine decides acctually completed the process) will try to restore it to health. In the case of an area command the units who do not stay behind to repair the target will move on to a new target. 

===Select AI(CTRL+Q)===

Press Control+Q to assign the currently selected units with an "AI".
Setting an AI will generate a "group" from that selection of units.

In Spring, the term AI stands more for an aid or "helper" than for a Complete Control AI (as NTAI, ZCAIN, JCAI).

Current available AIs.

None 
[[Simple Formation]] 
[[Central Build AI]] 
[[Metal Maker AI]] 
Default = Will assign defaul ai for that unit (?)

===Self Destruct(CTRL+D)===
Will detonate the selected units/buildings in a very spectacular explosion after a specific count-down (default is 5 seconds). Use this when destroying units/building that are in the way, or when detonationg mines or crawling bombs. A way to literally go out with a bang is to press Ctrl+A (Select All), Ctrl+D (Self Destruct). Note that this will make you lose the game, but is very spectacular!

===Stop(S)===
Makes them stop any queued commands, and stop moving. They will not automatically stop attacking units, unless their fire state is set to Hold Fire.

===Wait(W)===
If issued at some point in a command queue (holding shift for multiple commands) the unit will wait at that point in the queue until it is queued another wait command(which should cancel the other one out), or unitl it is given a non-queued order (no-shift, cancels command queue aswell as normal). If it is loaded by a transport while waiting, it will cancel the wait command once it has been unloaded.
(I Haven't Tested this functionality, someone should try it out and see what it acctually does... got this from the forums [http://taspring.clan-sy.com/phpbb/viewtopic.php?t=2034&highlight=wait+command])

=Chat, Cheats, and Text Commands=

Pressing ENTER will bring up a "say:" prompt which you can use to communicate with other players or issue "Text Commands". To send a message to all who are connected, type your message and press ENTER. To send a message only to your allies, preface your message with "a:". To send a message to any spectators, type "s:" then your message and press ENTER. To enter a Text Command, simply type the command and press ENTER.

===Basic Text Commands===

<table border="3" cellpadding="2" cellspacing="0">

<tr>
<th>Command</th><th>Effect</th>
</tr>

<tr>
<td>.info</td><td>Shows you what colour each player is, its CPU usage percentage and their ping delay in the bottom left corner of the screen</td>
</tr>

<tr>
<td>.clock</td><td>Shows you the elapsed game time in minutes and seconds in the bottom left corner of the screen</td>
</tr>

<tr>
<td>.take</td><td>Pulls all allied units, that are owned by players who have lost connection to the server, to your team.</td>
</tr>

</table>

===Cheat Codes===

<table border="3" cellpadding="2" cellspacing="0">

<tr><th>Cheat Command</th><th>Effect</th></tr>

<tr>
<td>'''.cheat'''</td><td>'''enable cheats - Cheats don't work in multiplayer until the host types this'''</td>
</tr>

<tr>
<td>.nocost</td><td>Insta-build; everything is built immediatly. (doesn't work on things already under construction, only on new ones)</td>
</tr>

<tr>
<td>.setmaxspeed 50</td><td>Changes the maximum speed multiplier (default is 3.0)</td>
</tr>

<tr>
<td>.setminspeed 0</td><td>Changes the minimum speed multiplier (default is 0.3)</td>
</tr>

<tr>
<td>.spectator</td><td>Allows you to see the entire map... but you lose control of your units</td>
</tr>

<tr>
<td>.team 0, .team 1, etc.</td><td>Change player</td>
</tr>

<tr>
<td>.give ARMCOM, .give 10 CORKROG, etc.</td><td>Place 1 or specified number of specified unit. Valid units are the internal names of units as specified in the unit definition.</td>
</tr>

</table>

=Map Doodles=

Hold the ` key to draw on the map, only you and your allies can see these doodles. Use this tool to mark out territory or warn of impending attacks or mark enemy bases or play tic-tac-toe before the game... be creative but not annoying.

Hold ` while pressing the left mouse button (MOUSE1) to draw a line.

Hold ` while double left clicking, then type a label then press ENTER to add a labled point(also minimap ping and chat message notification).

Hold ` while clicking the middle mouse button (MOUSE3/Scrollwheel Button) to add an empty point(also minimap ping and chat message notification).

Hold ` and clicking the right mouse button (MOUSE2) to erase lines or points.