| 54 | |
| 55 | == Installation == |
| 56 | We also provide an install target. When using makefiles, type ''make install'' and Orxonox will get installed. For project files, there's usually an ''INSTALL'' project which you can "build". [[br]] |
| 57 | There are two modes to install the game: |
| 58 | |
| 59 | === Non Copyable Installation (Unix default), INSTALL_COPYABLE=false === |
| 60 | Use absolute paths when installing and use the user directory for the log and configuration files. For Linux this means installing the binary, library and media files as superuser to the CMAKE_INSTALL_PREFIX (/usr per default) and then creating the configuration and log files in ~/.orxonox. [[br]] |
| 61 | On Windows the default location is %ProgramFiles%\Orxonox (usually C:\Program Files\Orxonox) and for the config and log files %ProgramData%\.orxonox (usually C:\Documents and Settings\username\Application Data\.orxonox). [[br]] |
| 62 | You can start the application from any working directory, but you cannot move or rename the installation directory, paths are hard coded. |
| 63 | |
| 64 | === Copyable Installation (Windows default), INSTALL_COPYABLE=true === |
| 65 | With this option, all paths will be stored relatively. That means you can copy and rename the installation directory as you wish. But you may not rename or copy the subdirectories. [[br]] |
| 66 | On Windows the application can be started from anywhere, on Unix the working directory has to be in the binary directory so that the libraries can be found. Anyway symlink to the executable gets created in the installation directory for convenience. [[br]] |
| 67 | The config and log files go to the corresponding folders, but relative to the installation directory. For instance MyDirectory/bin, MyDirectory/config, etc. |