Changes between Version 357 and Version 358 of BuildInstructions


Ignore:
Timestamp:
Sep 1, 2019, 7:40:11 PM (5 years ago)
Author:
Krinkle
Comment:

Add high-level doc to explain workspaces

Legend:

Unmodified
Added
Removed
Modified
  • BuildInstructions

    v357 v358  
    11[[TOC]]
    22
    3 This page describes how to get the very latest unstable version of the code. Unless you want to actively follow and contribute to development, **you probably want the [https://play0ad.com/download latest relatively-stable release] instead.**
    4 
    5 The current release of the game is aimed at developers and not at 'normal' users. As such, the following instructions assume a reasonable level of technical proficiency. If you encounter difficulties, please post on the [https://www.wildfiregames.com/forum/index.php?showforum=312 forum].
    6 
    7 == General prerequisites ==
     3This page describes how to install the latest development version of the code. This may be **unstable** and is intended for those that want to actively follow or contribute to the software development. **To install the latest alpha release,  [https://play0ad.com/download Download the Latest Alpha] instead.**
     4
     5The development version of the game is aimed at software developers (not regular players). As such, these instructions assume a higher level of technical proficiency. If you encounter difficulties, please consult the [https://www.wildfiregames.com/forum/index.php?showforum=312 forum].
     6
     7== System requirements ==
    88You'll need:
    99
     
    2020 * Up-to-date system software (Windows service packs, graphics driver updates, etc)
    2121 * Some technical proficiency. We try to make the build process as smooth and painless as possible, but it's designed to be followed by programmers - if you just want to play the game, wait for a pre-packaged installer instead.
     22
     23== Introduction ==
     24
     25The development environment for 0AD is comprised of three layers. Each goes on top of the previous:
     26
     271. Libraries.
     282. Workspaces.
     293. Source code.
     30
     31Libraries are external dependencies (such as SpiderMonkey). For Windows and Linux, the script to create or update the Workspaces also handles installation and updating of libraries. For macOS, the `libraries/osx/build-osx-libs.sh` script should be used instead.
     32
     33Workspaces contain the integrations for code editors (such as Visual Studio, Xcode, etc.) as well as the Makefile for the main source code. The workspaces are auto-generated by the `update-workspaces` script from the `buids/workspaces/` directory.  Once ready, the integrations are ready for use, such as `build/workspaces/gcc/Makefile` (for Linux and macOS) and `build\workspaces\vc2015` (for Windows).
     34
     35Finally, the source code is build by the workspace. For example, by running `make` in `build/workspaces/gcc`.
    2236
    2337== Windows ==