A blaise.cfg value like `rtl-src=~/devel/blaise/compiler/src/main/pascal` was treated as RELATIVE (only a leading '/' counted as absolute) and prefixed with the config directory, and the `~` was never expanded — producing a bogus path like `/home/user/cwd/~/devel/...` and an "RTL source directory not found" error. Resolve config paths through a shared helper: a leading '~' or '~/' expands to $HOME (and is treated as absolute); a leading '/' is used as is; anything else is relative to the config file's directory. Applies to both unit-path= and rtl-src=. If $HOME is unset, '~' is left untouched rather than mis-resolved. Tests: TConfigTests.TestParseTildePath_ExpandsToHome and TestParseRtlSrcTilde_ExpandsToHome. Verified end-to-end: a blaise.cfg using `~/...` for unit-path + rtl-src compiles with no path flags from any CWD. |
||
|---|---|---|
| .. | ||
| src | ||
| project.xml | ||