164 | | 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 in a directory alongside the `data` tarball's `binaries/data/` directory, so they can access it as `../data/` relative to the executables path. (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. |
| 164 | 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 in a directory alongside the `data` tarball's `binaries/data/` directory, so they can access it as `../data/` relative to the executables path. (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. See #492 for some files that might be useful. |