Thomas Bracht Laumann Jespersen
Thomas Bracht Laumann Jespersen
Is this a bug in `clean_rmeta()`? Currently, `link_deps()` shouldn't be used if your `PATH` variable contains spaces - I have kind of decided not to fix that issue here (#81),...
Sorry for the late reply. Is this also an issue in rustc's compiletest?
First of all, thanks for submitting this :+1: We could start by either adding a flag to `clean_rmeta()` that would enable/disable this new behaviour, or we could put this in...
> The library in the example project appears to be empty. None of the examples use anything from it. Correct. > I'm trying to set this up for a library...
Yes, I agree, splitting by whitespace is dangerous and wrong, I had this discussion in #81. We concluded at that time that what should ideally be changed is `Config.target_rustcflags` from...
See also #84, which wasn't merged.
Is this in `link_deps()`? The only path-handling uses `std::env::split_paths()` which seems to work correctly with spaces: ``` fn main() { let path = "/full/path/with spaces;/another/space example"; for p in std::env::split_paths(path)...
> Well, the problem starts from using link_deps(), wherever the actual bug may lie. :smile: Wait, so it was working with paths with spaces before introducing `link_deps()`? The only thing...
I'll add it as a caveat to using `link_deps()` in the README for the time being. Sorry for the trouble, and thanks again for reporting it.
Fortunately, this is really easy to reproduce, even on Linux. Just create a directory with spaces in the name and run `cargo test` in the `test-project`. I'll try to fix...