-
Notifications
You must be signed in to change notification settings - Fork 131
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
How to set esp-idf-sys
to rebuild when a C component changes?
#316
Comments
adding a remote component can't be detected by cargo as its not changing anything that it know about in the past. That always need a the second case is now what you are wishing for - monitor an already added component from cargo. That is still a bit tricky but not completely hopeless. We don't currently support that but there were changes in the "bindgen" dependency that allows for tracking of c/c++ header files and act if they changed. You can look at the PR that added it in bindgen here. But that would not monitor changes you do in any .c file. For that i don't now about a simple solution, as we would again need full information about every file you are providing in the component. Since you only want to rebuild esp-idf-sys i would go with the |
Thank you, I understand. |
closing this for now, as we don't plan on implementing automatic detection, and a sufficient "workaround" was presented, If someone wants to pick up from here, feel free to reopen it up. |
I successfully set up an extra C component in my Rust project. I noticed however that
cargo build
does not rebuildsesp-idf-sys
when any of the C sources is modified.I try adding a pertinent
rerun-if-changed
directive tobuild.rs
but I don't think thatesp-idf-sys
recognizes that the C component has changed (not sure about any of this, forgive my ignorance).Is there a way to rebuild
esp-idf-sys
depending on an extra C component?The text was updated successfully, but these errors were encountered: