Eclipse ROS fuerte

edit

I had the same problem, changing my launcher to source setup.bash solved it.

Create a file called "Eclipse.desktop" and paste the below text into it, possibly replacing /opt/eclipse with wherever your Eclipse installation is located.

#!/usr/bin/env xdg-open

[Desktop Entry]
Version=1.0
Type=Application
Terminal=false
Icon[en_US]=/opt/eclipse/icon.xpm
Exec=bash -c "source /opt/ros/fuerte/setup.bash; /opt/eclipse/eclipse"
Name[en_US]=Eclipse
Name=Eclipse
Icon=/opt/eclipse/icon.xpm

I had problems compiling ROS packages in Eclipse and found that adding the variable "LD_LIBRARY_PATH=/opt/ros/fuerte/lib" to the existing variables (ROS_PACKAGE_PATH, ROS_ROOT, PYTHONPATH, PATH) in "(Project)Properties->C/C++ Make Project->Environment" fixed the problem.

We typically do not use eclipse projects in eclipse for ros. Makefile projects seem to work well and require almost no configuration.

• Create your ros package (with roscreate-pkg)
• Start eclipse from your ros shell (or in a bash script which calls setup.bash first).
• Create a new empty makfile c++ project rooted at your project
• Add 'set(CMAKE_VERBOSE_MAKEFILE TRUE)` in your CMakeLists.txt

The last point helps the indexer auto-find headers because it will track all the -I flag settings that ros's make target generates.

• Finally build and clean using the default build/clean options.

You can then get creative by adding make targets in the ide for tests etc.

Are you sure you set the relevant environment variables under (Project)Properties->C/C++ Make Project->Environment too?

As far as I know Eclipse may not reach environment variables, such as ROS_PACKAGE_PATH, ROS_ROOT, PYTHONPATH, PATH. And you should add these manually.

I'm sure there should be a more elegant solution so that they can be added automatically, but this worked for me every time.

I encountered the same problem today using Eclipse Juno and ROS Fuerte on a Ubuntu system. I tried the solutions by dgossow and snorri, neither worked.

After reading some more about eclipse it hit me. The problem was that my eclipse juno install started with a workspace of ~/workspace but my ROS project was located in ~/ros_workspace. Once I restarted eclipse with a workspace of ros_workspace I was able to successfully build my project.

I believe this problem is unique to Eclipse Juno and ROS Fuerte, as I have another computer running Eclipse Indigo and ROS Electric without this problem.

Sorry - I cannot just leave comments on an answer, so this is directed to doml25.

Can you clarify what you mean? I am having the same issue with Fuerte and Juno - I created a package in /ros_workspace. Then I created a new Eclipse workspace in /ros_workspace. I imported the package into the Eclipse workspace, but still am getting "/cmake.mk: No such file or directory". I tried creating an Eclipse workspace within the already-created package space, but that failed even more miserably.

BTW - can anybody tell me where this commenting tool is?

To clarify for khambuch: I used the solution provided by dgossow and the problem still persisted. At that time when I opened eclipse I used ~/workspace as my workspace while the Ros Project was in the directory ~/ros_workspace. I imported the project into eclipse without copying the files.

When I closed eclipse and re-opened it selecting ~/ros-workspace as my workspace and then importing the project into eclipse everything worked.

Eclipse saves its configuration inside the directory you choose for a workspace. By switching workspaces, I forced eclipse to establish a new configuration and then it worked as expected.