ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

Cloned package not getting compiled.

asked 2019-05-22 10:10:02 -0500

Jayadev gravatar image

Hi, I cloned a package from Github to my workspace and tried to catkin_make. But apparently, just that folder is being skipped and is not getting compiled. I tried deleting build and devel, nothing worked. No errors are thrown out, just that new folder is not getting compiled. Thanks in advance.

edit retag flag offensive close merge delete

Comments

Can you describe the structure of your work space and exactly where you have cloned the package to. We don't have enough information to be able to help you.

PeteBlackerThe3rd gravatar image PeteBlackerThe3rd  ( 2019-05-22 10:13:56 -0500 )edit

It's a standard ROS workspace with an src folder holding all the packages. Currently, I have three packages, one created by me and two others cloned from Github. One of the cloned folders in not getting compiled. I guess the structure is fine. Thank you for your response.

Jayadev gravatar image Jayadev  ( 2019-05-22 10:28:20 -0500 )edit
2

We don't do guesses here on ROS Answers.

What is the output of tree -d -L 1 /path/to/your/workspace (if you get an error, make sure to run sudo apt install tree and try again)?


Edit: also:

I cloned a package from Github

can you link to the repository? I have a suspicion this is a rosbuild package, which will not be built by Catkin.

gvdhoorn gravatar image gvdhoorn  ( 2019-05-22 10:30:50 -0500 )edit

I'm sorry, but I'm pretty new to this. Excuse me if my questions are plain basic. I tried the tree to get the workspace structure. tree: Invalid level, must be greater than 0. is the message I got. This is what I ran tree -d -L1 /home/user/workspace . And the repository from which I cloned that package is https://github.com/lrse/ros-keyboard

Jayadev gravatar image Jayadev  ( 2019-05-22 11:04:02 -0500 )edit

A space was missing between the L and the 1, I've updated the command.

gvdhoorn gravatar image gvdhoorn  ( 2019-05-22 12:41:56 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2019-05-24 09:32:43 -0500

Jayadev gravatar image

Found out that the package was actually getting compiled but with a different name as compared to the folder name itself because of that different name being tagged in package.xml by the developer, which was not mentioned anywhere. That's the reason I couldn't find the package when I used the folder name, which is normally the case. Thank you for your time.

edit flag offensive delete link more

Comments

2

Glad you got to the bottom of this. It's a good way to learn that the folder names do not necessarily match package names.

PeteBlackerThe3rd gravatar image PeteBlackerThe3rd  ( 2019-05-24 10:38:12 -0500 )edit

Question Tools

2 followers

Stats

Asked: 2019-05-22 10:10:02 -0500

Seen: 154 times

Last updated: May 22 '19