Because global behaviors have to exist on both the central and split regardless if the user references them in their keymap, we can't omit the behavior declaration if the user doen't reference it and decide to compile it later based on the existence of the behavior declaration. The best option seems to be to decide whether to compile those behaviors based on the feature Kconfig flag. This also means that the two reset behaviors will always be compiled into both sides.
16 lines
366 B
Text
16 lines
366 B
Text
/*
|
|
* Copyright (c) 2020 The ZMK Contributors
|
|
*
|
|
* SPDX-License-Identifier: MIT
|
|
*/
|
|
|
|
/ {
|
|
behaviors {
|
|
// Behavior can be invoked on peripherals, so name must be <= 8 characters
|
|
// and cannot be /omit-if-no-ref/
|
|
rgb_ug: rgb_ug {
|
|
compatible = "zmk,behavior-rgb-underglow";
|
|
#binding-cells = <2>;
|
|
};
|
|
};
|
|
};
|