laze-project.yml: build context tree by embassy arch, not rust target #170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kaspar030
force-pushed
the
laze_refactor_nrf_contexts
branch
from
64e8070
to
1b6658f
Compare
4 tasks
kaspar030
force-pushed
the
laze_refactor_nrf_contexts
branch
from
1b6658f
to
7c6739a
Compare
ROMemories
requested changes
Mar 12, 2024
ROMemories
approved these changes
Mar 12, 2024
kaspar030
force-pushed
the
laze_refactor_nrf_contexts
branch
from
8699b1b
to
ead94f3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the laze contexts were stacked by architecture:
That only makes limited sense when looking at how we integrate embassy support, where e.g. the nrf51 & nrf52 have more in common than the nrf51 and the rp2040.
So this PR reorganizes this context tree like this:
The rustc targets are now provided by modules that are "select"ed where appropriate.