Changes between Version 80 and Version 81 of BuildInstructions

Timestamp:

Mar 27, 2010, 1:15:19 PM (14 years ago)

Author:

Philip Taylor

Comment:

experimental new system

BuildInstructions

@@ -167 +167 @@
 #endif
 }}}
+
+
+
+== Obtaining the latest release ==
+
+'''This is a new untested distribution method. It might be best to stick with SVN for now, while we sort this out over the next few days.'''
+
+=== Linux packages ===
+
+Unofficial packages may exist or be in development for several distros:
+ * [http://bugs.gentoo.org/show_bug.cgi?id=278541 Gentoo]
+ * [http://aur.archlinux.org/packages.php?ID=28560 Arch]
+ * [https://bugs.launchpad.net/getdeb.net/+bug/543277 Ubuntu]
+If you use a different distro, or if these packages are outdated, or if you want to edit or debug the code, see the next section.
+
+=== Compiling on Linux and OS X ===
+
+You need two files:
+ * [http://releases.wildfiregames.com/0ad-r07405-pre-alpha-unix-build.tar.xz 0ad-unix-build.tar.xz] (6 MB) ''or'' [http://releases.wildfiregames.com/0ad-r07405-pre-alpha-unix-build.tar.bz2 0ad-unix-build.tar.bz2] (8 MB)
+ * [http://releases.wildfiregames.com/0ad-r07405-pre-alpha-unix-data.tar.xz 0ad-unix-data.tar.xz] (92 MB) ''or'' [http://releases.wildfiregames.com/0ad-r07405-pre-alpha-unix-data.tar.bz2 0ad-unix-data.tar.bz2] (106 MB)
+The `.xz` files are smaller but may require you to install [http://tukaani.org/xz/ XZ Utils].
+
+SHA1 digests:
+{{{
+57d61f2bee26666d8e89e9952a6c2b532dd6e030  0ad-r07405-pre-alpha-unix-build.tar.xz
+eaaa0094a8baeaf3d3a11792b7272b397f2ca84c  0ad-r07405-pre-alpha-unix-build.tar.bz2
+2a5837141579f77f3b3b5f3d2e83b490dbef9bc5  0ad-r07405-pre-alpha-unix-data.tar.xz
+a30fc818807a40225bb792892ffd91a1c86fadfe  0ad-r07405-pre-alpha-unix-data.tar.bz2
+}}}
+
+Extract both files to the same location:
+{{{
+# Extract .xz version into the current directory:
+tar xvJf 0ad-r07405-pre-alpha-unix-build.tar.xz
+tar xvJf 0ad-r07405-pre-alpha-unix-data.tar.xz
+# Or, if your tar is older than 1.22:
+xz -cd 0ad-r07405-pre-alpha-unix-build.tar.xz | tar xv
+xz -cd 0ad-r07405-pre-alpha-unix-data.tar.xz | tar xv
+# Or, if you have the .bz2 version:
+tar xvjf 0ad-r07405-pre-alpha-unix-build.tar.bz2
+tar xvjf 0ad-r07405-pre-alpha-unix-data.tar.bz2
+}}}
+
+Then follow the SVN build instructions.
+
+=== Windows ===
+
+Download and run [http://releases.wildfiregames.com/0ad-r07405-pre-alpha-win32.exe 0ad-win32.exe] (114 MB) (self-extracting [http://www.7-zip.org/ 7-Zip]), then select a location to extract the files. This includes all the source code and data files, and precompiled binaries.
+
+SHA1 digest:
+{{{
+76f4ba98ef0f6e05eac9ff2a1b83ca767b181da3  0ad-r07405-pre-alpha-win32.exe
+}}}
+
+Either follow the SVN build instructions, or run binaries\system\pyrogenesis.exe directly.
+
+== Creating Linux packages ==
+
+This section is for people creating installable packages for Linux distros.
+
+Download the `build` tarball listed above. Follow the SVN build instructions. The default is an unoptimised debug-mode build (this is helpful since the game is unstable and buggy); if you want an optimised harder-to-debug build instead, compile with `CONFIG=Release make`.
+
+Run the automated tests to make sure nothing is broken: extract the `data` tarball alongside the `build` one, then run `./test_dbg` (or `./test` for Release builds) from `binaries/system/`. There should be no error output.
+
+You need to distribute the following files from `binaries/system/`:
+ * `pyrogenesis_dbg` (Debug build) or `pyrogenesis` (Release build)
+ * `libCollada_dbg.so` or `libCollada.so`
+ * `libAtlasUI_dbg.so` or `libAtlasUI.so`
+ * `libmozjs-ps-debug.so` or `libmozjs-ps-release.so`
+You also need to distribute the contents of the `data` tarball. You don't need to distribute anything from the `build` tarball. The executables should be located somewhere so that they can use `../data/` to access the `data` tarball's `binaries/data/` directory. (They don't need to be in a directory called `system/`, and that directory doesn't need to be in one called `binaries/`, if you prefer different names). The whole thing should probably go somewhere like `/opt/0ad/`, and you might want to set up a script with a nice name like `/usr/bin/0ad` to run it, depending on local conventions.
+
+These directories and files should be read-only; all per-user output goes in XDG basedir locations (unless we have bugs).