Package Details: ros-melodic-roscpp 1.14.11-1

Git Clone URL: https://aur.archlinux.org/ros-melodic-roscpp.git (read-only, click to copy)
Package Base: ros-melodic-roscpp
Description: ROS - roscpp is a C++ implementation of ROS.
Upstream URL: https://github.com/ros/ros_comm
Licenses: BSD
Conflicts: ros-melodic-roscpp-git
Submitter: GPereira
Maintainer: None
Last Packager: bionade24
Votes: 2
Popularity: 0.000000
First Submitted: 2018-02-24 12:19 (UTC)
Last Updated: 2021-04-29 20:41 (UTC)

Latest Comments

bionade24 commented on 2019-04-19 17:52 (UTC)

@lukicdarkoo: This is because the former Maintainer used the ros-gbp releases instead of the official meldodic-devel branch. I'm currently restructuring development of the PKGBUILDs. New place for PRs is https://github.com/ros-melodic-arch First goal is to switch to this branches.

lukicdarkoo commented on 2019-04-19 17:33 (UTC)

Any news on this https://github.com/ros/ros_comm/pull/1580

When the new changes are going to be included?

jwhendy commented on 2019-02-16 23:00 (UTC)

I'm not sure either. Most seem to default to melodic-devel, which would fit with the ros-[release]-foo naming structure. There are likely other issues that arise with this, but at the moment, many of these things we're talking about patching or manually applying JustWork(TM) if one grabs upstream melodic-devel. On all the ones affected by libbost_signals and -lpthread, I end up just doing aur fetch and editing the PKBUILD source to point to git instead of ros-gbp. I'm nearly done getting everything playing nicely with cmake 3.13 and boost 1.69, which is nice.

bionade24 commented on 2019-02-16 20:42 (UTC) (edited on 2019-02-16 20:48 (UTC) by bionade24)

@jwhendy: I don't know what the intention of @GPereira was to use the ros-gbp packages. But which is the official branch? melodic-devel?

Edit: Seems all official ROS builds are also based on ros-gbp. Don't no if the others even work.

jwhendy commented on 2019-02-16 17:48 (UTC)

The cmake/boost transition that is working it's way through ROS makes AUR usage incredibly difficult since these are all based on the ros-gbp releases (melodic packages from Aug 2018). Is there a reason not to follow the official ROS github packages instead?

bionade24 commented on 2019-01-30 16:27 (UTC) (edited on 2019-01-31 20:24 (UTC) by bionade24)

@aethr11: Do you have boost installed? Edit: Github Issue: https://github.com/ros/ros_comm/pull/1580 Workaround should be easy.

aethr11 commented on 2019-01-30 15:20 (UTC)

changed -lpthread to pthread but showing boost_signals library not found

bastikr commented on 2019-01-26 12:10 (UTC)

I also had to remove signals from the CMakeLists.txt and change the -lpthread statement to be able to build this package. Do we wait until things change upstream or should we apply these changes automatically here?

bionade24 commented on 2019-01-18 20:53 (UTC)

@Cubimon: I changed -lpthread to pthread in opt/ros/melodic/share/cpp_common/cmake/cpp_commonConfig.cmake:119

Cubimon commented on 2019-01-18 19:32 (UTC) (edited on 2019-01-18 19:32 (UTC) by Cubimon)

I removed signals from find_package in CMakeLists.txt:25 of the source. Include directories stay the same anyway ¯\_(ツ)_/¯ and no libs are required

jwhendy commented on 2019-01-17 05:47 (UTC)

And ros-melodic-rosconsole-bridge threw an error about needing libboost_regex 1.69, so I wonder if some of these packages are just in between boost dependencies somehow? I'm not that familiar with how these are maintained... should I report this upstream?

jwhendy commented on 2019-01-17 05:37 (UTC)

I had to downgrade to boost and boost-libs 1.68.0-2 for this to work. libboost_signal.so moved from /usr/lib/boost/ to something in /usr/include/boost/signals[2]. This might be coupled with having to downgrade to cmake 3.12.3 to get ros-melodic-cpp-common to play along with something else as well.