This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| guide:paths_on_the_command_line [2017-03-13 12:02] – skyjake | guide:paths_on_the_command_line [2017-03-15 07:28] (current) – [Path symbols] skyjake | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Paths on the command line ====== | ||
| + | |||
| + | |||
| + | This article explains how Doomsday 1.x handles paths in command line arguments. | ||
| + | |||
| + | As a general rule of thumb, all relative paths on the command line are interpreted relative to the current working directory where the engine is started from. | ||
| + | |||
| + | |||
| + | ===== Base folder and runtime folder ===== | ||
| + | |||
| + | |||
| + | These are the folders that the engine is working with: | ||
| + | |||
| + | * Doomsday base (root) directory (for example **C: | ||
| + | |||
| + | * [[runtime_folder]]: | ||
| + | |||
| + | The [[-basedir]] option tells the engine where the base directory is located. | ||
| + | |||
| + | When the engine is looking for resource files, it interprets relative paths in relation to the base directory. | ||
| + | |||
| + | |||
| + | ===== IWAD folder ===== | ||
| + | |||
| + | |||
| + | The [[-iwad]] option can be used to define a directory where IWAD files can be found. Doomsday will locate all the IWAD files inside the provided directory. | ||
| + | < | ||
| + | -iwad ~/ | ||
| + | </ | ||
| + | |||
| + | |||
| + | ===== Path symbols ===== | ||
| + | |||
| + | < | ||
| + | |||
| + | If Doomsday finds a path that begins with a greater-than character (>) or a closing brace character (}, the > or } character is replaced with the path specified by [[-basedir]]. For example, //-file > | ||
| + | |||
| + | |||
| + | ===== See also ===== | ||
| + | |||
| + | * [[platform-specific_notes_readme_]] | ||
| + | * [[configuration]] | ||
| + | |||
| + | |||
| + | |||