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

sbloch's profile - activity

2021-01-10 16:29:31 -0500 received badge  Nice Question (source)
2017-05-09 01:39:27 -0500 received badge  Famous Question (source)
2017-01-20 05:02:28 -0500 received badge  Student (source)
2017-01-20 04:56:40 -0500 received badge  Notable Question (source)
2016-09-03 21:21:14 -0500 received badge  Popular Question (source)
2016-07-18 14:28:08 -0500 commented question Error trying to subscribe, synchronize and publish topics

Did you ever figure it out? I'm having the same bug.

2016-07-07 21:59:59 -0500 received badge  Supporter (source)
2016-07-07 21:58:24 -0500 received badge  Scholar (source)
2016-07-07 19:04:08 -0500 asked a question Work on duplicate packages with the same name

I'm simultaneously working on two projects with the same starting-point code: I've forked public repo A twice locally. I want to publish my modifications to A (let's call this A') to open-source my code. However, I want to make different changes to the same original package and just use those locally (let's call this A").

Obviously, when I call "catkin_make", I get an error for having multiple packages of the same name. Is there a way around this? Should I setup multiple catkin workspaces or is this bad practice? Do I have to systematically go through one of the packages and change every duplicate name to something else?

2016-07-07 19:04:07 -0500 asked a question Simultaneously Work on Packages of the Same Name

I'm simultaneously working on two projects with the same starting-point code: I've forked public repo A twice locally. I want to publish my modifications to A (let's call this A') to open-source my code. However, I want to make different changes to the same original package and just use those locally (let's call this A").

Obviously, when I call "catkin_make", I get an error for having multiple packages of the same name. Is there a way around this? Should I setup multiple catkin workspaces or is this bad practice? Do I have to systematically go through one of the packages and change every duplicate name to something else?