ros2nix

Use ROS with the Nix package manager (by acowley)
Add to my DEV experience Suggest topics
Source Code
Suggest alternative
Edit details
Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
Sponsored

Ros2nix Alternatives

Similar projects and alternatives to ros2nix

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better ros2nix alternative or higher similarity.
Suggest an alternative to ros2nix

ros2nix reviews and mentions

Posts with mentions or reviews of ros2nix. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-04-09.
  • Nix is the ultimate DevOps toolkit
    21 projects | news.ycombinator.com | 9 Apr 2021
    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

Stats

Basic ros2nix repo stats
1
17
0.0
over 6 years ago

acowley/ros2nix is an open source project licensed under BSD 3-clause "New" or "Revised" License which is an OSI approved license.

The primary programming language of ros2nix is Nix.

Popular Comparisons

  1. ros2nix VS haskell-nix
  2. ros2nix VS nix-ros-overlay
  3. ros2nix VS nixos
  4. ros2nix VS vaultenv
  5. ros2nix VS rclcpp
  6. ros2nix VS nix-home
  7. ros2nix VS nixos
  8. ros2nix VS nix-1p
  9. ros2nix VS asdf
  10. ros2nix VS nickel

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com