You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: When building one of the example binaries (for example examples/rp/src/bin/wifi_blinky.rs), the Cargo.toml lists the Embassy dependencies as being local filesystem paths rather than remotely installed packages. When trying to remove the path assignment for those listed packages, the build breaks in a way that can't be easily resolved. It appears that the local Embassy repo pulled in from Github has different versions than what's on Crates.io.
Suggestion: Update the Cargo.toml files in the examples/ directories to use dependency versions that are building from just Crates.io and remove the need to use local Embassy packages. This would simplify using Embassy as a framework by just installing packages from Crates.io instead of needing to rely on the Github repository.
The text was updated successfully, but these errors were encountered:
Problem: When building one of the example binaries (for example
examples/rp/src/bin/wifi_blinky.rs
), the Cargo.toml lists the Embassy dependencies as being local filesystem paths rather than remotely installed packages. When trying to remove thepath
assignment for those listed packages, the build breaks in a way that can't be easily resolved. It appears that the local Embassy repo pulled in from Github has different versions than what's on Crates.io.Suggestion: Update the Cargo.toml files in the examples/ directories to use dependency versions that are building from just Crates.io and remove the need to use local Embassy packages. This would simplify using Embassy as a framework by just installing packages from Crates.io instead of needing to rely on the Github repository.
The text was updated successfully, but these errors were encountered: