Build fail for Cortex-R5F
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- shell
- Domain
- build-system, embedded-iot
Research direction
Start with build_firmware.sh and reproduce the colcon build using my_custom_toolchain.cmake and my_custom_colcon.meta; inspect actual_output.txt.txt for the failure. Done means the Cortex-R5F firmware build completes and produces firmware/build/libmicroros.a and firmware/build/include.
Written by the indexing model from the issue text.
Description
Issue template
- Hardware description: Cortex R5F, ARM v7-R
- RTOS: FreeRTOS
- Installation type: micro_ros_setup
- Version or commit hash: humble
Steps to reproduce the issue
mkdir microros_ws && cd microros_ws
git clone -b humble https://github.com/micro-ROS/micro_ros_setup.git src/micro_ros_setup
rosdep update && rosdep install --from-paths src --ignore-src -y
colcon build
source install/local_setup.bash
ros2 run micro_ros_setup create_firmware_ws.sh generate_lib
touch my_custom_toolchain.cmake
touch my_custom_colcon.meta
ros2 run micro_ros_setup build_firmware.sh <absolute path to my_custom_toolchain.cmake> <absolute path my_custom_colcon.meta>
Expected behavior
Firmware should build creating static libraries and required header files inside firmware/build/libmicroros.a and firmware/build/include
Actual behavior
Additional information
attaching my custom toolchain cmake and my custom colcon meta file
my_custom_toolchain.cmake.txt
my_custom_colcon.meta.txt
I tried removing the optimization flags in my_custom_toolchain.cmake file when I searched about it, but issue still remains
- Dominant language
- Shell
- Stars
- 509
- Forks
- 183
- Avg merge
- 22h 26m
- Merged PRs (30d)
- 7
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.
More from micro-ROS/micro_ros_setup
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
micro-ROS/micro_ros_setup#814 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
micro-ROS/micro_ros_setup#809 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
micro-ROS/micro_ros_setup#808 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
micro-ROS/micro_ros_setup#806 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
micro-ROS/micro_ros_setup#803 ·
All issues in micro-ROS/micro_ros_setup
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·