-Autobuilds are nightly builds of the latest code. They have the latest features, bugfixes and assets but they could be less stable than regular releases.
+---
+title: Xonotic Autobuilds
+---
-If you "installed" Xonotic by downloading and unpacking the [zip](http://xonotic.org/download/), you can update a regular release to autobuild using the scripts located in `misc/tools/rsync-updater` (use `update-to-autobuild.bat` if you're one Windows, `update-to-autobuild.sh` on Linux and Mac). You can also download an autobuild and various other builds as a zip from https://beta.xonotic.org/autobuild/ - username is `xonotic` and password `g-23`.
+Autobuilds are "beta" builds, like [stable release](https://xonotic.org/download/) builds but with all the latest changes from git.
+They're the easy way to play or host the latest development version. Like stable releases they include source code and an easy way to [compile](Compile) it for various CPUs.
+
+If you "installed" Xonotic by unpacking the stable release zip you can update it to the latest autobuild using the scripts located in `misc/tools/rsync-updater` (use `update-to-autobuild.bat` if you're on Windows, `update-to-autobuild.sh` on Linux and Mac). You can also [download an autobuild zip](https://beta.xonotic.org/autobuild/).
It's best to **make a copy of the original Xonotic directory first** in case you wanna go back to using the release but you can also go back by using the `update-to-release` scripts. Releases and autobuilds should be able to coexist (they will share the same [config](https://www.xonotic.org/faq/#config) though, unless you use something like `-userdir`).
-Autobuilds (and [git builds](https://gitlab.com/xonotic/xonotic/-/wikis/Repository_Access)) are compatible with the same servers as the latest release. When you connect to a server, Xonotic downloads the gamelogic from it (and runs it sandboxed) so you always use the same version as the server. Autobuilds therefore only affect the gamelogic of local games, the engine (rendering, input, ...) and assets (models, sounds, ...).
\ No newline at end of file
+Autobuilds (and [git builds](Repository_Access)) are compatible with the same servers as the latest release. When you connect to a server, Xonotic downloads the gamelogic from it (and runs it sandboxed) so you always use the same version as the server. Autobuilds therefore "only" affect the gamelogic of local or hosted games, the engine (rendering, input, ...), assets (models, sounds, ...), menu, config and scripts.
-This page is about compiling the sources included in [stable](https://xonotic.org/download) and [beta](Autobuilds) releases, and is also applicable when [updating by rsync](https://xonotic.org/download#upgrading). \r
-For development purposes (git builds), please see [Repository_Access](Repository_Access).\r
+---\r
+title: Compiling Xonotic releases and autobuilds\r
+---\r
\r
-The release Makefile aims to provide a convenient way to compile for alternative CPU architectures, or to get a build fully optimised for a recent x86 CPU (the official binaries are generic x86_64). It would also allow you to run Xonotic on an OS too old to be supported by official binaries.\r
+This page is about compiling the sources included in [stable releases](https://xonotic.org/download) and [beta autobuilds](Autobuilds), which you may want to do after [updating by rsync](https://xonotic.org/download#upgrading). \r
+For git builds and development tools please see [Repository_Access](Repository_Access) and [Git HOWTO](Git).\r
+\r
+The release Makefile is the most convenient way to compile for alternative CPU architectures, or to get a build fully optimised for a recent x86 CPU (the official binaries are generic x86_64). It would also allow you to run Xonotic on an OS too old to be supported by official binaries.\r
\r
To this end the Makefile default settings enable all optimisations that can be used on your current CPU without causing bugs, and compile using all available CPU threads.\r
\r
-The engine builds will be dynamically linked except for d0_blind_id which is statically linked to ensure reliable player ID support and because OS distributions don't ship this.\r
+The engine builds will be dynamically linked except for d0_blind_id which is statically linked to ensure reliable player ID support and because OS distributions don't ship this library.\r
+\r
+### Commands\r
\r
Invoking `make` or `make help` in the Xonotic directory will print the supported targets and current config. \r
\r
+---
+title: Xonotic git howto
+---
+
+This page is about how to use `git` and the `all` script for development.
+To download and compile a git build please see [Repository_Access](Repository_Access).
+To get push access and contribute please read [CONTRIBUTING](https://gitlab.com/xonotic/xonotic/-/blob/master/CONTRIBUTING.md).
+
Cloning the repository
----------------------
- [Xonotic Server Management Suite](https://github.com/z/xonotic-server-management-suite)\r
\r
## Development\r
-\r
-- [Repository Access: Compiling and Requesting Push Access](Repository_Access)\r
+- [Repository Access: Compiling and maintaining a Xonotic git build](Repository_Access)\r
+- [Requesting Push Access and Contributing](https://gitlab.com/xonotic/xonotic/-/blob/master/CONTRIBUTING.md)\r
- [Git: HowTo and Repository Structure](Git)\r
- [Licensing / Legal](Legal)\r
\r
## Misc\r
\r
- [Archive](Archive)\r
-- [Gitlab Markdown Reference](https://gitlab.com/help/user/markdown.md) (for editing this wiki)
\ No newline at end of file
+- [Gitlab Markdown Reference](https://gitlab.com/help/user/markdown.md) (for editing this wiki)\r
-Compiling and Contributing\r
-==========================\r
+---\r
+title: Xonotic git builds\r
+---\r
+\r
+Git builds have higher system requirements and are more work to compile and maintain than [autobuilds](Autobuilds) but are needed to develop and/or test Merge Requests.\r
+\r
+To get push access and contribute please read [CONTRIBUTING](https://gitlab.com/xonotic/xonotic/-/blob/master/CONTRIBUTING.md). \r
+For assistance with using `git` and the `all` script for development please see the [git howto](Git). \r
+\r
+---\r
\r
Xonotic uses [several Git repositories](Git). The `all` script in the main repo manages them, builds Xonotic and runs it. Each repo can also contain feature branches next to the stable `master` branch, check them out for WIP features.\r
\r
-Build Requirements\r
-------------------\r
+\r
+# Build Requirements\r
\r
Make sure you have at least 2GB memory to compile. This is enough to run a git dedicated server, but 6GB is required to play using a git client (it uses more memory than regular release and auto builds). \r
\r
\r
You must first install **XCode** which comes on your installation DVD or can be downloaded from the Apple website. This package provides tools like **Git and GCC**, which are needed for successful checkout and compilation of Xonotic. Some versions of XCode come with Git and others don’t - if you don’t have Git after installing XCode get it here: [XCode installer](http://sourceforge.net/projects/git-osx-installer/files/)\r
\r
-Cloning the Repository and Compiling\r
-------------------------------------\r
+\r
+# Cloning the Repository and Compiling\r
\r
To begin downloading:\r
\r
http://git-scm.com/book/en/v2/Git-Branching-Remote-Branches\r
\r
A tutorial to Git for SVN users:\r
-https://git.wiki.kernel.org/index.php/GitSvnCrashCourse
\ No newline at end of file
+https://git.wiki.kernel.org/index.php/GitSvnCrashCourse\r
projects / xonotic / xonotic.wiki.git / commitdiff