This project doesn't work if there is a global cargo build folder

[jrmoulton]

If a global cargo build folder is set to ~/.cargo/target/, the build will hang as this project cant build while the normal build has a lock on the build folder.

[wdanilo]

@jrmoulton Would you be able to try the newest version? It should have many issues resolved. It's not published yet, so you'd need to try it from the main branch. I'd be very thankful for confirmation it works or a minimal repro, so I could try it out locally.

[jrmoulton]

yeah I'll test it out

[jrmoulton]

No 'Cargo.toml' files found in parent directories of /Users/me/.cargo/src/name_of_file.

/Users/me/.cargo is my global cargo target dir.

[jrmoulton]

I think a minimal repro just includes setting a global target build directory.

[wdanilo]

Did you try testing it from master? I'll be releasing the new version on crates in a few days after I test it deeply. But the version from master does not create projects in your home location anymore, so I suspect the error you see is not from this version. Anyway, I'll release a preview package on crates tomorrow and ping you, so it will be easy for you to test it out. Sorry for the inconvenience!

[jgrund]

I also have a global cargo_target_dir set and am seeing the same behavior (compilation hang) using c5bd99e

The issue goes away if I switch to compiling under my project.

[wdanilo]

Ok, @jgrund and @jrmoulton what would be your suggestions here? What should we do in this case?

[pickx]

possibly related: I'm seeing the following on 1.1.0 with any code that calls a crabtime macro: Path '~/.cargo/registry/src/index.crates.io-X/crabtime-1.1.0/src/lib/project_Y' does not have parent 'target' directory. (where X and Y are placeholders). I believe building worked the last time I tried this, which was the github 1.0.0 version prior to release in crates.io

I tried cargo clean then deleting the contents of ~/.cargo/registery/src but it comes back after a cargo build

[wdanilo]

@pickx I understand you are using global cargo build folder as well, right?

[songzhi]

Meeting the same issue, I don't know how to work around, so I just download this repo to my local machine and it works. I tried to refactor my code by using crabtime, and it's fantastic. Hoping this issue could be fixed soon, so I can merge my refactor patch.

[wdanilo]

I will work on it this weekend :)

[wdanilo]

Ok, I was thinking a lot about it. What should we do in case the global build folder is set there? Should we ignore it and just compile crabtime crates somewhere else? Are there any better ideas than that? :)

[jrmoulton]

I think if you use a custom profile, it will have it's own build folder and lock.