docs: Give examples of using other build.yaml props #8
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
caksoylar
force-pushed
the
example-with-props
branch
from
3f0d761 to
cf33ada
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.
Following up on zmkfirmware/zmk#2015, add an example using
cmake-argsandartifact-nameto the comment blurb in build.yaml.Here I used an alternate keymap example since that request comes up, e.g. zmkfirmware/zmk#1931. However it isn't the most straightforward since the path seems to be relative to
zmk/app, hence the../... AlsoKEYMAP_FILEisn't a documented arg.An alternative would be to set a Kconfig for that build. Would that be preferable? If so, I can replace this with e.g.
-DCONFIG_ZMK_USB_LOGGING=y.