We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello @donRaphaco, I'm removing the libatomic from the extensions repositories and adding it to rcutils package, check this: https://github.com/micro-ROS/micro_ros_setup/pull/171/checks?check_run_id=953530520
rcutils
But in the case of the ESP32 I'm not able to remove the folder components/libatomics and these two lines without having building errors.
components/libatomics
Is possible for you to remove this libatomic dependency for the ESP32 board support? I'm working in this PR: #18 You can commit there if you wish.
Thanks!
The text was updated successfully, but these errors were encountered:
rm libatomic from esp32 (see #19)
5c87578
Signed-off-by: Raphael Vogelgsang <[email protected]>
It should be fixed with 5c87578
Sorry, something went wrong.
33c5bf6
Test atomics (#18)
8c8baba
* Simple 64 bit atomic mocks, no atomicity * Remove atomics * Add esp32 deps * Update esp32 * rm libatomic from esp32 (see #19) Signed-off-by: Raphael Vogelgsang <[email protected]> Co-authored-by: Raphael Vogelgsang <[email protected]>
donRaphaco
No branches or pull requests
Hello @donRaphaco, I'm removing the libatomic from the extensions repositories and adding it to
rcutils
package, check this: https://github.com/micro-ROS/micro_ros_setup/pull/171/checks?check_run_id=953530520But in the case of the ESP32 I'm not able to remove the folder
components/libatomics
and these two lines without having building errors.Is possible for you to remove this libatomic dependency for the ESP32 board support? I'm working in this PR: #18 You can commit there if you wish.
Thanks!
The text was updated successfully, but these errors were encountered: