Problems with include path of libraries in microros

Open
#664 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale

Research direction

Start by inspecting the microros_setup output that creates libmicroros/include and the compile flags used for the static library. Done means the generated headers can be included using one include path, without adding each library directory separately, while matching the include layout used by the code.

Written by the indexing model from the issue text.

Description

Issue template

  • Hardware description: STM
  • RTOS: freeRTOS
  • Installation type: microros_setup
  • Version or commit hash: iron
Steps to reproduce the issue

I have compiled Microros as a static lib and added it using the compile flags. I have also added the folder libmicroros/include as an include path. However, the code does not find any of the headers because the folders are organized in the following way:
library_name/library_name/header_file.h. That's because the includes are /library_name/headear_file.h. In other words, I am forced to add each folder path as an include path. Is there a way to make it simpler? In the previous version of Microros, the folder organization was /library_name/headear_file.h, and the new version's code still follows that standard.

Dominant language
Shell
Stars
509
Forks
183
Avg merge
22h 26m
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from micro-ROS/micro_ros_setup

All issues in micro-ROS/micro_ros_setup

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.