-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_cargo_build_script_run not executing relative to crate? #391
Comments
Hi, sorry for the delay, I am a bit overloaded at the moment, Would you mind sharing the Cargo.toml file you used so I can repro? Can you also share some details about your operating system? |
Thanks for the repro. Sorry I still don't follow fully, what are you changing in the BUILD file? |
if you checkout the repo, and run the instructions in the readme, you can reproduce the error. i'm on Mac OS 10.15.5 |
Yes I can repro, this was not what I wanted to ask. You said earlier that:
Are you editing the build.rs? |
yep |
Does this happen when using |
@parisholley did #427 solve your problem? |
i am having issues with crates such as ring/openssl that attempt to compile libraries as part of the build... they try to refer to files that are relative to the crate (when vendor'd) but instead, the working directory is my repository root. if i manually edit the build files to do ./cargo/vendor/crate-name-version/path/to/file.c then it works fine (but obviously isn't a solution).
The text was updated successfully, but these errors were encountered: