Skip to content

Commit 1375105

Browse files
authored
README.md: Explain PROJECT_ROOT_FORCED
1 parent 559669a commit 1375105

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ To get start on Windows, work on Git BASH:
2020
| `LVCOMPARE_EXECUTABLE` | Path to the LvCompare executable |
2121
| `LVMERGE_EXECUTABLE` | Path to the LvMerge executable |
2222
| `CONFIG_DIRECTORY_LEVEL` | Level of directory from the project root to this configuration file.<br />0 if placed at the project root.|
23-
| `PROJECT_ROOT_FORCED` | (Optional) Path to the project root<br/>If set to non-empty string, it overrides the auto-detection result from `CONFIGURATION_DIRECTORY_LEVEL` and the configuration source path |
23+
| `PROJECT_ROOT_FORCED` | (Optional) Path to the project root<br/>If set to non-empty string, it overrides the auto-detection result from `CONFIGURATION_DIRECTORY_LEVEL` and the configuration source path<br />This option is needed only when the absolute path of the project root cannot be correctly determined.<br />For example, when working on a project in the shared folder of Windows-in-VirtualBox, git sometimes interprete the path as `//VBoxSvr` and cause the script to err, making manual specification nessisary. |
2424

2525
* Inside the project, do
2626
```console

0 commit comments

Comments
 (0)