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
Our prototype currently hard codes these addresses in the source code. Getting them from the chip.toml at build time would be better. At first look doing so would require adding some plumbing to xtask. The data we would need is in the 'chip' key from the top level toml table but AFAIK the currently available methods for getting at the app toml exposed to tasks at build time aren't sufficient:
build_util::config exposes the app config that includes tables under [config]:
This work has fallen behind other tasks and I haven't thought much about it beyond the initial comment. AFAIK this is mostly a plumbing exercise to surface the required data at build time.
Our prototype currently hard codes these addresses in the source code. Getting them from the
chip.toml
at build time would be better. At first look doing so would require adding some plumbing to xtask. The data we would need is in the 'chip' key from the top level toml table but AFAIK the currently available methods for getting at the app toml exposed to tasks at build time aren't sufficient:build_util::config
exposes the app config that includes tables under[config]
:hubris/build/util/src/lib.rs
Line 50 in 09fb927
build_util::task_config
exposes tables under the[task_name]
table:hubris/build/util/src/lib.rs
Line 57 in 09fb927
The text was updated successfully, but these errors were encountered: