Bugfix/revert to make

[akoerner1]

---

Description

This PR overhauls the build system and adds several major features across ADORe subsystems.

Build System Migration

The build system has been migrated from just to GNU Make. just lacks available system packages, which caused installation failures on some systems, notably NVIDIA Jetson Orin. After encountering these issues the team decided to revert to GNU Make.

Assuming Docker and GNU Make are installed the following is the new procedure to build ADORe:

1. Clone the ADORe repositiory:

git clone git@github.com:eclipse-adore/adore.git && cd adore && git submodule update --init --recursive

2. Build the ADORe CLI Docker context:

make build

4. Start lichtblick for visualization:

cd tools/lichtblick
make start

5. Run the ADORe CLI and a scenario

make cli
cd adore_scenarios/simulation_scenarios
ros2 launch dlr_campus.launch.py

6. Open Lichtblick in the browser:

http://localhost:8080/?ds=rosbridge-websocket&ds.url=ws://localhost:9090&layout=Default.json

ADORe Embedded

adore/adore_embedded builds a self-contained binary package under 2GB compatible with Docker, Podman, and chroot. Packages are published to eclipse-adore/adore releases via GitHub Actions on PRs to develop.

Landing Page

The ADORe landing page has been restyled and reorganized.

Eclipse Zenoh Integration

The ADORe CLI now bundles the ROS Zenoh DDS plugin and starts a Zenoh router on launch.

• Router config: zenoh_router_config.json5
• Bridge config: zenoh_bridge_config.yaml
• Startup behavior: adore.env

The Zenoh bridge node bridges selected topics from FastDDS to Zenoh. Both the router and bridge start with the CLI by default.

Mission Control Dashboard

When the ADORe CLI is running the mission control dashboard can be found at: localhost:8888

Topic Tools -- inspect, subscribe, publish, template, save, and load ROS topics and message types.

ROS Task Manager -- manage and halt ROS processes via the web interface.
ROS Workspace -- The ADORe mission control dash board now has a "ROS Workspace" tab that can be used to manage the ROS 2 workspace directory. With that the current build status for each package is monitored, builds can be triggered.

Hardware Monitor -- a new ROS node at adore/ros2_workspace/src/adore_interfaces/hardware_monitor reports system health (CPU, RAM, disk) and hardware inventory to the following ROS topics:

/cluster/ADORe_CLI/hardware_inventory
/cluster/ADORe_CLI/hardware_status

Model Checker -- a model checking dashboard with live results and config save/edit/load support.

Goal Picker -- select start position, goal position, and heading with automatic coordinate conversion between lat/long and UTM.

Type of Change

Please delete options that are not relevant:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (adds or updates documentation)
• Refactor (non-breaking change for code readability/structure)
• Other (please describe):

Checklist

• I have performed a self-review of my own code.
• I have signed and submitted the Eclipse Foundation Contributors Agreement: https://www.eclipse.org/legal/eca/.
• My last commit was made with the --signoff flag as required by the Eclipse Foundation.
• I have commented my code, particularly in hard-to-understand areas and provided a README.md when necessary.
• I have added tests that prove my fix is effective or that my feature works.
• Tests pass locally with my changes: (run 'make test' on the ADORe project root to run unit tests).
• I have updated the documentation in documentation/technical_reference_manual where necessary.
• I have updated the THIRD-PARTY.md if I have introduced new third-party libraries or dependencies to the project.
• I have updated the CONTRIBUTERS.md if I wish to acknowledged for my contribution.