Skip to content
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

Jump to bottom

Missing build.rs for cargo:rerun-if-env-changed? #3

Open
xobs opened this issue Apr 4, 2021 · 1 comment · May be fixed by #4
Open

Missing build.rs for cargo:rerun-if-env-changed? #3

xobs opened this issue Apr 4, 2021 · 1 comment · May be fixed by #4

Comments

@xobs
Copy link

xobs commented Apr 4, 2021

According to a post on Reddit, it looks like this crate doesn't get rebuilt when environment variables change. For example, changing the CPU frequency doesn't cause a rebuild of the consts in this crate.

There should be a build.rs added that prints out any environment variables that should cause a rebuild. For example:

build.rs:

fn main() {
    println!("cargo:rerun-if-env-changed=AVR_CPU_FREQUENCY_HZ");
}
@lord-ne
Copy link

lord-ne commented Aug 25, 2021 •
edited
Loading

For some reason this still doesn't seem to be triggering a rebuild for me

EDIT: Never mind, my build script was in the wrong directory. It works now, I'm going to make a pull request.

@lord-ne lord-ne linked a pull request Aug 25, 2021 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rebuild if AVR_CPU_FREQUENCY_HZ environment variable changes lord-ne/avr-config
2 participants
@xobs @lord-ne