Skip to content

document the lack of automatic rebuilding after env var changes #443

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
+7 −0
Closed

document the lack of automatic rebuilding after env var changes #443

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,13 @@ functions with hard requirements on some variables supplied by [cargo's
build-script driver][cargo] that it has the `TARGET`, `OUT_DIR`, `OPT_LEVEL`,
and `HOST` variables.

Note that by default, changing these environment variables from one
build to the next does not cause Cargo to rerun `build.rs`, and later
builds may use stale artifacts. One workaround is to `touch build.rs`
whenever you change these variables. You can also enable automatic
rebuilding on a case-by-case basis with
[`rerun-if-env-changed`](https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script).

[cargo]: http://doc.crates.io/build-script.html#inputs-to-the-build-script

## Optional features
Expand Down