This reverts commit f52bcaa27f
.
It did not pass CI, and was merged anyway because there were two CI
errors in the same cygwin job. The other error was not the fault of this
commit, and since cygwin errors were glossed over because they were
"expected", the presence of a new error *added* by this commit was
overlooked.
Per the meson development policy, PRs which result in CI errors
can/should be reverted at will, no questions asked.
pull/12134/head
parent
1fd70a2a00
commit
84c8905d52
6 changed files with 8 additions and 116 deletions
@ -1,17 +0,0 @@ |
||||
## `fs.relative_to()` |
||||
|
||||
The `fs` module now has a `relative_to` method. The method will return the |
||||
relative path from argument one to argument two, if one exists. Otherwise, the |
||||
absolute path to argument one is returned. |
||||
|
||||
```meson |
||||
assert(fs.relative_to('c:\\prefix\\lib', 'c:\\prefix\\bin') == '..\\lib') |
||||
assert(fs.relative_to('c:\\proj1\\foo', 'd:\\proj1\\bar') == 'c:\\proj1\\foo') |
||||
assert(fs.relative_to('prefix\\lib\\foo', 'prefix') == 'lib\\foo') |
||||
|
||||
assert(fs.relative_to('/prefix/lib', '/prefix/bin') == '../lib') |
||||
assert(fs.relative_to('prefix/lib/foo', 'prefix') == 'lib/foo') |
||||
``` |
||||
|
||||
In addition to strings, it can handle files, custom targets, custom target |
||||
indices, and build targets. |
@ -1,5 +0,0 @@ |
||||
int |
||||
main(void) |
||||
{ |
||||
return 0; |
||||
} |
Loading…
Reference in new issue