Compile service: Support passing RHS kconfig and building RHS #17
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
chrisandreae
force-pushed
the
rhs-kconfig
branch
from
939e789 to
f5372fc
Compare
chrisandreae
force-pushed
the
rhs-kconfig
branch
from
f5372fc to
c2bb157
Compare
Specifying RHS kconfig will cause both firmware images to be built, which will take twice as long as a LHS-only build. Clients should take care to only request a RHS build for kconfig options that affect the peripheral behaviour.
chrisandreae
force-pushed
the
rhs-kconfig
branch
from
92a60eb to
ee2ace1
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.
Specifying RHS kconfig will cause firmware images for both sides to be built, which will take twice as long as a LHS-only build. Clients should take care to only request a RHS build for kconfig options that affect the peripheral behaviour.