You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main motivation behind this change is to make it easier to package
Descent 3 for Linux. For example, let’s say that you’re packaging
Descent 3 for Debian and you want to make the package work well with
Debian’s game-data-packager. The package for the Descent 3 engine will
put d3-linux.hog in one directory, and the package for the proprietary
Descent 3 game data will put d3.hog into a different directory [1]. The
Descent 3 engine package can use the DEFAULT_ADDITIONAL_DIRS CMake
option in order to make sure that both d3-linux.hog and d3.hog are
located automatically.
Copy file name to clipboardExpand all lines: BUILD.md
+14-11Lines changed: 14 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,15 +195,18 @@ cmake --preset linux -DBUILD_TESTING=ON
195
195
196
196
You can also use the [cmake-gui](https://cmake.org/cmake/help/latest/manual/cmake-gui.1.html) front-end to easily set and view CMake cache variable values, and generate build
|`CMAKE_BUILD_TYPE`|`Debug` builds are generally larger, slower and contain extra correctness checks that will validate game data and interrupt gameplay when problems are detected.<br>`Release` builds are optimized for size and speed and do not include debugging information, which makes it harder to find problems. The build type can also be set using the `--config` argument with a preset. |`Debug`|
|`CMAKE_BUILD_TYPE`|`Debug` builds are generally larger, slower and contain extra correctness checks that will validate game data and interrupt gameplay when problems are detected.<br>`Release` builds are optimized for size and speed and do not include debugging information, which makes it harder to find problems. The build type can also be set using the `--config` argument with a preset. |`Debug`|
|`DEFAULT_ADDITIONAL_DIRS`| A semi-colon separated list of paths that Descent 3 will use as read-only base directories (see [USAGE.md’s Base directories section][1]). Each item in this list is placed between quotation marks in order to form a C++ expression. This will cause issues if the items in the list are not properly escaped. You can use C++ escape sequences in order to embed special characters (like `\`, `"` and `;`) in paths. Example: `C:\\Games\\Descent3\\;D:\\`| A list with one item in it. The item is an empty string. |
204
+
|`ENABLE_LOGGER`| Enable logging to the terminal. |`OFF`|
|`FORCE_COLORED_OUTPUT`| Always produce ANSI-colored compiler warnings/errors (GCC/Clang only; esp. useful with Ninja). |`OFF`|
207
+
|`FORCE_PORTABLE_INSTALL`| Install all files into local directory defined by `CMAKE_INSTALL_PREFIX`. |`ON`|
207
208
| `OFF` |
208
-
|`USE_VCPKG`| Explicitly control whether or not to use vcpkg for dependency resolution. `ON` requires the environment variable `VCPKG_ROOT` to be set. | Determined by the existence of `VCPKG_ROOT` in the environment: If it exists, vcpkg is used. |
209
-
|`CODESIGN_IDENTITY`| Sets the macOS code signing identity. If set to something besides the empty string, then the dynamic libraries put into the hog files will be signed using this identity. | The empty string, `""`. |
209
+
|`USE_VCPKG`| Explicitly control whether or not to use vcpkg for dependency resolution. `ON` requires the environment variable `VCPKG_ROOT` to be set. | Determined by the existence of `VCPKG_ROOT` in the environment: If it exists, vcpkg is used. |
210
+
|`CODESIGN_IDENTITY`| Sets the macOS code signing identity. If set to something besides the empty string, then the dynamic libraries put into the hog files will be signed using this identity. | The empty string, `""`. |
Copy file name to clipboardExpand all lines: USAGE.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,18 +87,19 @@ Descent 3 has two types of base directories:
87
87
- The writable base directory can contain both read-write files and read-only files. There is only one writeable base directory. By default, the writable base directory gets set to the current working directory.
88
88
- The read-only base directories can only contain read-only files. There can be any number of read-only base directories. By default, Descent 3 uses zero read-only base directories.
89
89
90
-
You can set the writable base directory and the list of read-only base directories using the `-setdir`, `-useexedir` and `-additionaldir` command-line options (see [the next section](#command-line-options)).
90
+
You can set the writable base directory and the list of read-only base directories using the `-setdir`, `-useexedir` and `-additionaldir` command-line options (see [the next section](#command-line-options)). Descent 3 also has a list of default read-only base directories. Normally, the list of default read-only base directories is empty, but you can change it by using the `DEFAULT_ADDITIONAL_DIRS` CMake option when compiling Descent 3 (see [BUILD.md’s Build Options section](./BUILD.md#build-options)).
91
91
92
92
When Descent 3 tries to find a read-only file, then it will look through the list of base directories in this order:
93
93
94
94
- the last read-only base directory that was specified on the command-line,
95
95
- the second-to-last read-only base directory that was specified on the command-line,
96
96
- the third-to-last read-only base directory that was specified on the command-line,
97
97
- …
98
-
- the first read-only base directory that was specified on the command-line and, finally,
98
+
- the first read-only base directory that was specified on the command-line,
99
+
- all of the items on the `DEFAULT_ADDITIONAL_DIRS` list in reverse order, and, finally,
99
100
- the writable base directory.
100
101
101
-
Files that are in base directories that are higher on that list will override files that are in base directories that are lower on that list. For example, lets say that you run Descent 3 like this:
102
+
Files that are in base directories that are higher on that list will override files that are in base directories that are lower on that list. For example, lets say that the `DEFAULT_ADDITIONAL_DIRS` list is empty and that you run Descent 3 like this:
0 commit comments