You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it will work to use weak symbols for the master hook function definitions in the core, and make parts of the HID module(s) selectively link that way. I need to test this.
The text was updated successfully, but these errors were encountered:
I want everything that's pluggable/selectable to be defined somewhere in the sketch, with preprocessor macros or by other means.
Plugin hook functions could be done with weak symbols, maybe, in order to bring them in without reading config files in the plugin repo.
HID endpoints (i.e. BootKeyboard) could have the static objects defined only inside weak wrapper functions (in core?), and if those functions are overridden elsewhere, they should be dropped from the program. Test this.
I think it will work to use weak symbols for the master hook function definitions in the core, and make parts of the HID module(s) selectively link that way. I need to test this.
The text was updated successfully, but these errors were encountered: