micro-ROS / micro-ROS/micro_ros_setup
uxr/agent/AgentInstance.hpp directory not found
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 509
- Forks
- 183
- Avg merge
- 22h 26m
- Merged PRs (30d)
- 7
Description
## Issue template
- Hardware description: Minisforum EM780 Linux
- Installation type: micro-ros-setup
- Version or commit hash: ros2 humble
#### Steps to reproduce the issue
I followed the instruction with the following link
https://micro.ros.org/docs/tutorials/core/first_application_linux/
I have created the firmware successfully
ros2 run micro_ros_setup create_firmware_ws.sh host
but next when i try to build the firmware, error came out
ros2 run micro_ros_setup build_firmware.sh
In file included from /home/user/chin_ws/src/uros/micro-ROS-Agent/micro_ros_agent/src/agent/Agent.cpp:18:
/home/user/chin_ws/src/uros/micro-ROS-Agent/micro_ros_agent/include/agent/Agent.hpp:18:10: fatal error: uxr/agent/AgentInstance.hpp: No such file or directory
18 | #include
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
In file included from /home/user/chin_ws/src/uros/micro-ROS-Agent/micro_ros_agent/src/main.cpp:15:
/home/user/chin_ws/src/uros/micro-ROS-Agent/micro_ros_agent/include/agent/Agent.hpp:18:10: fatal error: uxr/agent/
AgentInstance.hpp: No such file or directory
18 | #include
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
#### Expected behavior
build successfully
Where should I find this file or directory?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by rerunning create_firmware_ws.sh host and build_firmware.sh from the micro-ROS Linux tutorial, then inspect micro_ros_agent/include/agent/Agent.hpp and the reported Agent.cpp and main.cpp include failures. Trace where uxr/agent/AgentInstance.hpp is expected to come from; done means the firmware build completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100