-
Notifications
You must be signed in to change notification settings - Fork 225
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
Use the "generic-queue" from embassy-time instead of the "integrated-timers" from embassy-executor #1087
Comments
Running into linker errors is not nice. We probably should improve the documentation regarding the features (i.e. explain that |
That sounds like a good idea. I am also a bit confused whether to add i.e. |
Good point! Given with #1089 we'll probably remove the At least we have an issue reminding us that we should do something about the ergonomics here 👍 |
As part of #1196 we no longer enable integrated timers by default, leaving the end user with the choice of using generic queue or integrated timers. |
#1037
The "integrated-timers" timer queue from embassy-executor does not work properly on esp32.
I added "generic-queue" from embassy-time and got a linker error.
As it turns out, this has to do with the "embassy-integrated-timers" default-feature of the esp32-hal.
With this default feature, embassy-executor creates the _embassy_time_schedule_wake function:
embassy-time provides an alternative timer_queue_impl behind "generic-queue":
But if both features are enabled, this duplicate declaration results in a nasty link-time error...
My proposed solution is to use the "generic-queue" from embassy-time instead of the "integrated-timers" from embassy-executor or to at least remove "embassy-integrated-timers" from the default features.
The text was updated successfully, but these errors were encountered: