The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
I'm guessing you built from source, as you say you changed the source of image_view directly. At the end of a successful build (and if instructed to do so), rosmake will create the ROS_NOBUILD file in the package directory as an indication to the build system that the package can (and should) be skipped in any subsequent rosmakes. Normally, packages installed via a package manager don't include the source and come with a ROS_NOBUILD to prevent make clean mishaps.
So the behaviour you saw was actually 'by design': rosmake is meant to skip building image_view and consequently your changes do not take effect.
AFAIK the most accepted setup for working on ROS (core) packages is to create a ROS 'workspace' and manage it using rosws and .rosinstall files. See this page for a tutorial.
| | 2 | No.2 Revision |
I'm guessing you built from source, as you say you changed the source of image_view directly. At the end of a successful build (and if instructed to do so), rosmake will create the ROS_NOBUILD file in the package directory as an indication to the build system that the package can (and should) be skipped in any subsequent rosmakes. Normally, packages installed via a package manager don't include the source and come with a ROS_NOBUILD to prevent make clean mishaps.mishaps among other things.
So the behaviour you saw was actually 'by design': rosmake is meant to skip building image_view and consequently your changes do not take effect.
AFAIK the most accepted setup for working on ROS (core) packages is to create a ROS 'workspace' and manage it using rosws and .rosinstall files. See this page for a tutorial.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
