rclcpp
robotnix
rclcpp | robotnix | |
---|---|---|
4 | 14 | |
492 | 565 | |
2.4% | 2.3% | |
9.1 | 6.7 | |
2 days ago | about 1 month ago | |
C++ | Nix | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rclcpp
-
How to use various QoS settings in ros2 used in moveit software?
I think there's an overload of rclcpp::action::create_client that will accept an rcl_action_client_options_t (see here https://github.com/ros2/rclcpp/pull/1133/files) but it looks like MoveGroupInterface doesn't pass anything in when it creates the action clients:
-
Making the jump to ROS2
So one of the bigger issues I've encountered is that re-entrant services can break with the multi-threaded executor https://github.com/ros2/rclcpp/issues/1212 Services in ROS2 by default are not reentrant meaning they need to be called asynchronously. Since my team was porting ROS1 nodes over we wanted to keep the old blocking service call behavior in ROS2 to avoid changing decision logic. Unfortunately, we found out that this can cause the node to crash per the issue above. The fix for that issue was implemented in Humble irc, but can't be ported back to foxy. That's one specific example, but we've seen a few other issues like that as well.
-
RADU: Motor Controller Software for Arduino and Raspberry Pico
Alternatively, you can use the default client libraries like rclpy or rclcpp for writing custom code that reads and writes ROS2 messages.
-
Nix is the ultimate DevOps toolkit
Thanks for the response!
> This is difficult to answer without knowing more details.
The situation specifically is the ROS ecosystem, where metadata is managed in these package.xml files:
https://github.com/ros2/rclcpp/blob/master/rclcpp/package.xm...
The federated nature of the ecosystem has led to a culture where it's very normal to be building dozens of these at once, in the same workspace together, often from multiple repos (the repo above has four in it). So there are several build tools which automate the work of examining a source workspace and building all the packages within it in the correct topological order, respecting build_depend tags. The newest of these tools (colcon) has actually made the package.xml optional in many cases, as it can examine CMakelists, setup.py, BUILD, etc, and discover for itself what the dependencies are.
Your "distribution" of ROS is formed by listing all the packages and repos in this big file, for which there is other tooling to manage pulling dependency sources, whatever: https://github.com/ros/rosdistro/blob/master/foxy/distributi...
Anyway, so the existing ROS/nix efforts (1) seem to basically consume all of this package/distribution metadata at once and generate a giant parallel structure of nix definitions (eg https://github.com/lopsided98/nix-ros-overlay/blob/master/di...), which I fear would be completely opaque to users and any system which required everyone to leave behind these existing workflows would be an immediate non-starter.
I think the ideal scenario (and what it would look like if I built this myself based on debs) would be that you could source the "base" workspace as usual (enter the nix-shell?), and check out source, build packages as usual with colcon, the usual workspace-building tool, but there'd be an extra plugin/verb/flag for it, which would make it build each package as a nix package instead of into the usual installspace. The verb would generate the nix definitions on the fly, and probably handle the invocation and build-parallelism side of it as well.
[1]: https://github.com/acowley/ros2nix, https://github.com/lopsided98/nix-ros-overlay
robotnix
- Immutable Linux Distributions for Those Looking to Embrace the Future
-
Towards a reproducible F-Droid
danielfullmer/robotnix
-
Error signing TrichromeChrome.apk when building OTA package
commit 660b23fb152874b6d237065045c78ceeb6ebdbf9 Author: Chirayu Desai Date: Fri Jun 24 01:41:28 2022 +0530 releasetools: Replace Trichrome fingerprint * Trichrome APKs depend on TrichromeLibrary, and they specify both package name and a certificate digest * We sign TrichromeLibrary and both dependent APKs with the same key, so we can simply make sure that the fingerprint matches the key the APK is being (re)signed with Based on: https://github.com/danielfullmer/robotnix/blob/master/modules/apps/chromium-trichrome-patcher.py Change-Id: I79f8c69787decd5abbb5d5513dee9bc357eb8814
-
post home folders
You might be interested in https://github.com/danielfullmer/robotnix
-
Nixery – Docker images on the fly with Nix
Just noting, using Nix it is possible to build an actual real deal Android image using Robotnix:
- https://github.com/danielfullmer/robotnix/
This is different from a non-Android Linux on Mobile devices, which is what Mobile NixOS aims to achieve :).
-
Project End of Life
If you still want to do your own builds, I'd recommend looking at Robotnix (https://github.com/danielfullmer/robotnix). While it doesn't out of the box build on AWS like this, it's a way more sane build process and it would be easy enough to execute a build on any cloud provider.
- Wir schreiben für das c't-Magazin über Linux - fragt uns alles! [Beginn um 17 Uhr]
- Build Android (AOSP) Using Nix
- I wonder if we're ever going to see a mobile OS made with the same philosophy as Arch Linux.
-
Add Android Auto to Calyx OS before flashing ROM
There are some tools already which support automated builds such as https://github.com/dan-v/rattlesnakeos-stack and https://github.com/danielfullmer/robotnix - however they'll need work to support both CalyxOS and also Android Auto.
What are some alternatives?
micro_ros_arduino - micro-ROS library for Arduino
calyxos
ros2_serial_example
AuroraStore
nix-1p - A (more or less) one page introduction to Nix, the language.
nix - Nix, the purely functional package manager
rclpy - rclpy (ROS Client Library for Python)
rattlesnakeos-stack - Build your own privacy and security focused Android OS in the cloud.
rosserial - A ROS client library for small, embedded devices, such as Arduino. See: http://wiki.ros.org/rosserial
Pine64-Arch - :penguin: Arch Linux ARM for your PinePhone/Pro and PineTab/2
Micro-XRCE-DDS - An XRCE DDS implementation. Looking for commercial support? Contact [email protected]
haskell-nix - Nix and Haskell in production