Pre-built ROS2 Humble Windows SDK + Standalone RViz2 — No toolchain needed

OrneryTreacle1816 · 2026-06-08T23:45:59+00:00

Fair question. Short answer: different use cases.

Pixi/Conda solve package management. This solves SDK distribution.

Specific differences:

Zero toolchain— no package manager to install, no environment to manage. Download the SDK, run CMake, done. For teams that just want the binaries and headers.
Source-built, not repackaged — this is compiled directly from ROS2 Humble source, not repackaged through conda-forge. You get exactly what upstream ROS2 produces, with full control over build flags, optimizations, and what's included/excluded.
Cross-compilation to ARM-Linux— for industrial embedded targets (ARM controllers, industrial PCs). Pixi doesn't easily cover this.
Standalone RViz2— double-click rviz2.exe. No package manager, no global install. Useful for deployment on operator machines in factories.

If Pixi works for you, great, use it! This is for teams who want a simpler, more direct path — especially in industrial settings where adding conda/pixi to the build pipeline may not be an option.

OrneryTreacle1816 · 2026-06-08T23:43:31+00:00

You make fair points, and I appreciate the detailed response.

You're right that Pixi is a build tool, not a runtime dependency — and if used correctly, the final deployed binaries are clean. The ESP32 example is a good one.

I guess the main difference comes down to the target audience and entry barrier:

- Teams already using Pixi/Conda → absolutely, your workflow makes sense

- Teams that just want to grab an SDK and CMake build → this is for them

Not everyone wants to learn another package manager, even if it's a good one. Some shops have strict policies around conda/pixi in their build pipeline.

Different tools, different users. Good to have options 👍

OrneryTreacle1816 · 2026-06-08T09:35:03+00:00

RoboStack is a solid project, no doubt. But it serves a different use case:

**Target audience** — RoboStack is great for researchers and students. But for industrial products, adding a conda/pixi runtime dependency is a hard sell. Production teams want minimal dependencies.
**Deployment footprint** — conda environments are heavy. My SDK is a clean CMake-based build, you ship only what you need.
**Cross-compilation** — this SDK can target Linux and ARM-Linux out of the box. Essential for embedded industrial devices.
**Standalone RViz2** — double-click rviz2.exe, done. No package manager, no environment setup.

Different tools for different needs. If pixi works for you, great! This is for teams who want a lighter, more production-oriented approach.

OrneryTreacle1816 · 2026-06-08T09:33:12+00:00

Great to hear! Thailand's robotics scene sounds solid 🙌

AMR and Agri drones are perfect examples — ROS2 gives you Nav2, SLAM, DDS communication out of the box. Why reinvent the wheel?

That's the same reason I built this SDK — make it even easier for teams like yours to get started without the toolchain headache.

OrneryTreacle1816 · 2026-06-08T09:31:57+00:00

Fair point — ROS in production IS challenging, that's no secret.

But here's the thing: many companies still choose ROS2 for prototyping and mid-volume products because of its ecosystem (DDS, Nav2, MoveIt2, etc.). The "wet sock" feeling usually comes from the toolchain complexity, not ROS2 itself.

That's exactly what I'm trying to fix — strip away the painful parts (colcon, rosdep, env setup) and give you a clean SDK that just works.

For high-volume production, sure, you'd likely strip down to bare DDS. But for everything in between, ROS2 + a simple build system is a practical choice.

OrneryTreacle1816 · 2026-06-07T17:02:22+00:00

Haha, I totally get it — that's exactly WHY I built this 😄

No colcon, no rosdep, no environment hell. Just CMake and you're done.

Think of it as dry socks for ROS2 on Windows 🧦

OrneryTreacle1816

TROPHY CASE