Package Details: ros-melodic-desktop-full 1.4.1-3

Git Clone URL: https://aur.archlinux.org/ros-melodic-desktop-full.git (read-only, click to copy)
Package Base: ros-melodic-desktop-full
Description: ROS - A metapackage to aggregate several packages.
Upstream URL: https://github.com/ros/metapackages
Keywords: melodic morena robot robotics ros
Licenses: BSD
Submitter: GPereira
Maintainer: None
Last Packager: bionade24
Votes: 12
Popularity: 0.000000
First Submitted: 2018-05-13 18:47 (UTC)
Last Updated: 2021-03-23 03:30 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

bionade24 commented on 2019-02-01 21:47 (UTC) (edited on 2019-02-01 21:47 (UTC) by bionade24)

@marsmee: Thanks for your suggestons. If they really don't wnat to change this in upstream, I'll use the second option (list(REMOVE_ITEM Boost_LIBRARIES -lpthread)) and add .patch files to AUR. But I'll try to get the fix into upstream.

marsmee commented on 2019-01-31 22:19 (UTC) (edited on 2019-02-01 14:18 (UTC) by marsmee)

@bionade24 As for as I know you can find the pkgConfig.cmake.in file in /opt/ros/melodic/share/catkin/cmake/templates/ which itself is included by /opt/ros/melodic/share/catkin/cmake/catkin_package.cmake. The different libraries a catkin/ROS package uses are passed (indirectly) through the DEPENDS argument of the catkin_package macro, that expands e.g. Boost to ${Boost_LIBRARIES} which includes the evil -lpthread. I don't think you have a chance to suppress this behavior by a CMake command line parameter or such.

I suggest that you place list(REMOVE_ITEM Boost_LIBRARIES -lpthread) before catkin_package in each ROS package that performs a find_package(Boost REQUIRED COMPONENTS ... thread). Or maybe it is easier to modify the affected configs directly with sed?

bionade24 commented on 2019-01-31 17:04 (UTC)

@drapostolski: Have you installed ros-melodic-catkin & python-catkin_pkg ? I never got this error.

drapostolski commented on 2019-01-23 21:49 (UTC) (edited on 2019-01-23 22:10 (UTC) by drapostolski)

I am trying to install this package via the Manjaro Software Manjaro from the AUR, but I am getting the error :

ImportError: "from catkin_pkg.package import parse_package" failed: No module named 'catkin_pkg' Make sure that you have installed "catkin_pkg", it is up to date and on the PYTHONPATH (the full error message is posted here: https://answers.ros.org/question/313134/manjaro-arch-cmake-error-when-installing-ros-melodic-desktop-full/)

I have tried to install this package with having python2-catkin_pkg installed (no catkin_pkg in python 3), and with having python-catkin_pkg installed (no catkin_pkg in python 2), but I get the same error.

Can anyone help?
@bionade24 how did you solve this problem ?

krukai commented on 2019-01-22 21:44 (UTC)

@bionade24 Thank you for taking over! I'd gladly sponsor you some of your namesake.

bionade24 commented on 2019-01-19 06:57 (UTC)

Hello, I'm the new maintainer. I'm busy at this weekend now, but I'll hope I can fix everything until Wednesday. Submissions & Co-Maintainers are welcome!

bionade24 commented on 2019-01-14 18:56 (UTC)

Why are those packages now orphaned? Does @GPereira not wnat to pack them anymore?

bionade24 commented on 2019-01-13 20:14 (UTC) (edited on 2019-01-13 21:37 (UTC) by bionade24)

The problem I specified in my post before isn't related to rostime, it's a catkin problem. After removing -lpthread out of opt/ros/melodic/share/cpp_common/cmake/cpp_commonConfig.cmake:119 it works, and libboost_thread.so is still there, so there schould be thread support. Is this an upstream issue ? But please correct me if I did bullshit.

Edit: Does work when changing -lpthread to pthread Edit_2: There are multiple files which set the libraries for various packages, some are always regenerating, so no chance to change them. But all have the comment # generated from catkin/cmake/template/pkgConfig.cmake.in. Where can I find this file, since grep finds nothing?

GPereira commented on 2019-01-12 19:45 (UTC)

Or explain what you did.

GPereira commented on 2019-01-12 19:44 (UTC)

Have you got it working? If so, please submit a patch