cortex-m-rtic-trace: source TPIU/DWT/ITM information from manifest
tmplt opened this issue · comments
The end-user should only need to input the TPIU/DWT/ITM information once in the [package.metadata.rtic-scope]. cargo-rtic-scope sources it currenly, but that is not the case for cortex-m-rtic-trace.
We can pass information from the manifest to the crate itself by exporting environmental variables. The crate built may abstract things but this requires a dependency to be added in Cargo.toml and in best case, a new build.rs that exports the variables; or in the worst case: modifying an exising build.rs.
This is not possible without touching build.rs which we should not have to do.