-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(console): Added runtime component registration support in console_simple_init #402
feat(console): Added runtime component registration support in console_simple_init #402
Conversation
4a1a9a3
to
8bccb89
Compare
Just one note, overall this component seems pretty generic and not specifically tied to esp-protocols. Perhaps we can move it to https://github.com/espressif/idf-extra-components in the future? Implementations of commands specific to protocols should stay here, of course. |
6dd55e9
to
3f60801
Compare
3f60801
to
057873c
Compare
.plugin_regd_fn = &cmd_registration_function | ||
};̌ | ||
``` | ||
2. Add the `WHOLE_ARCHIVE` flag to CMakeLists.txt of the component. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this potentially links more object files than necessary. We only need to ensure that the component registration callback is linked, but the component may also contain other object files. Following the "user shouldn't pay for what they don't use" principle I think we could try to have a more light-weight solution.
This is probably not a blocker for this PR specifically, we can always update the documentation later. But for other console components you create we might need to revise the WHOLE_ARCHIVE approach. (Also, not a blocker for releasing the first versions.)
Just one remark, LGTM otherwise! |
Added support for runtime component registration in console_simple_init.