Robotics StackExchange | Archived questions

I'm trying to build a package using catkin build,i even get notification that package has been built.But no package found is the error while using rosfind package.What should I do now?

[build] No packages were found in the source space '/home/atharva/catkinws/src/laserscankinect/src' [build] No packages to be built. [build] Package table is up to date.
[build] Summary: All 0 packages succeeded!
[build] Ignored: None.
[build] Warnings: None.
[build] Abandoned: None.
[build] Failed: None.
[build] Runtime: 0.0 seconds total.
atharva@atharva-Inspiron-7537:~/catkinws/src/laserscankinect$ catkin build laserscan_kinect

Asked by atharva_jadhav on 2018-10-25 11:45:54 UTC

Comments

even get notification that package has been built

I don't believe that is true.

We see this in the output you copy-pasted:

[build] Summary: All 0 packages succeeded! 

"0 packages" means "no packages".

Asked by gvdhoorn on 2018-10-26 04:46:11 UTC

Yeah, I do have same query but, a notification on top right of my screen shows package built successfully.If no packages are built in real,how can i build them?

Asked by atharva_jadhav on 2018-10-26 06:58:27 UTC

I believe it only shows that the build was successful. But it would always be successful if it doesn't build any packages.

Asked by gvdhoorn on 2018-10-26 07:43:25 UTC

Thanks for reply, how do i make sure that the package is build?

Asked by atharva_jadhav on 2018-10-26 07:45:48 UTC

Answers

It appears Catkin is looking in the incorrect workspace as it is looking in the laserscan_kinect/src and not catkin_ws/src.

Try typing 'catkin build laserscan_kinect' or 'catkin_make' inside ~/catkin_ws.

Asked by bsheffield on 2018-10-25 14:24:04 UTC

Comments

Yup, compilation needs to be done from the root of the workspace (i.e. ~/catkin_ws and not from the root of a package).

Asked by jayess on 2018-10-26 02:38:30 UTC

@jayess are you sure about that? You are correct regarding catkin_make, but OP mentions catkin build. I believe you can run catkin build from any directory within a workspace. https://catkin-tools.readthedocs.io/en/latest/verbs/catkin_build.html

Asked by jarvisschultz on 2018-10-26 07:29:29 UTC

This problem could have been caused by running catkin init more than once, or possibly just once but in the wrong directory.

Asked by jarvisschultz on 2018-10-26 07:31:13 UTC

@jarvisschultz Good point, I didn't catch that the asker was using catkin build I only saw that the answerer was using catkin_make

Asked by jayess on 2018-10-28 21:06:09 UTC