diff options
| author | Ryan <fauxpark@gmail.com> | 2021-09-14 22:16:24 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-09-14 13:16:24 +0100 |
| commit | b56282756b5faa410301de8c4ecdcae0e0148652 (patch) | |
| tree | cf68cfe0e4f148d6eab52ae289ce261bea88f6c3 /docs/hardware_keyboard_guidelines.md | |
| parent | 0ca4a56a0449d17a497ba610d4cee41c914ff50e (diff) | |
[Docs] Clean up some code block languages (#14434)
Diffstat (limited to 'docs/hardware_keyboard_guidelines.md')
| -rw-r--r-- | docs/hardware_keyboard_guidelines.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/hardware_keyboard_guidelines.md b/docs/hardware_keyboard_guidelines.md index 17be7ee6aa..f975f37f55 100644 --- a/docs/hardware_keyboard_guidelines.md +++ b/docs/hardware_keyboard_guidelines.md @@ -156,12 +156,12 @@ Many of the settings written in the `rules.mk` file are interpreted by `common_f The `post_rules.mk` file can interpret `features` of a keyboard-level before `common_features.mk`. For example, when your designed keyboard has the option to implement backlighting or underglow using rgblight.c, writing the following in the `post_rules.mk` makes it easier for the user to configure the `rules.mk`. * `keyboards/top_folder/keymaps/a_keymap/rules.mk` - ```makefile + ```make # Please set the following according to the selection of the hardware implementation option. RGBLED_OPTION_TYPE = backlight ## none, backlight or underglow ``` * `keyboards/top_folder/post_rules.mk` - ```makefile + ```make ifeq ($(filter $(strip $(RGBLED_OPTION_TYPE))x, nonex backlightx underglowx x),) $(error unknown RGBLED_OPTION_TYPE value "$(RGBLED_OPTION_TYPE)") endif |