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

Git Clone URL: https://aur.archlinux.org/ros-melodic-desktop-full.git (read-only)
Package Base: ros-melodic-desktop-full
Description: ROS - A metapackage to aggregate several packages.
Upstream URL: http://www.ros.org/
Keywords: melodic morena robot robotics ros
Licenses: BSD
Submitter: GPereira
Maintainer: bionade24 (jwhendy)
Last Packager: GPereira
Votes: 6
Popularity: 0.686173
First Submitted: 2018-05-13 18:47
Last Updated: 2018-09-26 11:24

Pinned Comments

bionade24 commented on 2019-04-09 19:13

WE ARE CURRENTLY IN REDEVELOPMENT, THIS PACKAGE PROBABLY BREAKS!!!!
We moved our Development to Github: https://github.com/ros-melodic-arch
Please open issues there instead of commenting.

marsmee commented on 2019-01-31 22:19

@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?

Latest Comments

1 2 3 4 5 6 ... Next › Last »

bionade24 commented on 2019-04-09 19:13

WE ARE CURRENTLY IN REDEVELOPMENT, THIS PACKAGE PROBABLY BREAKS!!!!
We moved our Development to Github: https://github.com/ros-melodic-arch
Please open issues there instead of commenting.

ilinojkovic commented on 2019-04-01 19:33

@bionade24 That didn't work as well, but I used sudo pacman -Rsc $(pacman -Qs ros- | awk ' NR % 2 == 1 { print substr($1, 7) } ') and it seems it cleared things up.

bionade24 commented on 2019-04-01 15:28

@masmee: Then do sudo pacman -Rsc ros-melodic-*

ilinojkovic commented on 2019-04-01 12:22

@bionade24 I cannot do that, getting the error: target not found: ros-melodic-desktop-full since this package itself is not installed, just some of its dependencies.

bionade24 commented on 2019-03-29 14:29

@ilinojkovic: sudo pacman -Rsc ros-melodic-desktop-full

ilinojkovic commented on 2019-03-28 21:06

Hi all. I'm a newbie to arch, and seems already in deep water with ros :) So I had troubles installing this package on my Manjaro machine. I tried several approaches, from the official one to the one provided by @kwarzi in git repo. All of the approaches had some errors, so I ended up using docker.

The question that I have now is - how to easily remove/purge all the ros dependencies that are downloaded and/or installed on my local machine?

Quite a few of the packages did install but a lot is still left uninstalled. It would be quite a pain going through all one by one.

kwrazi commented on 2019-02-25 04:18

For people having trouble installing ros-melodic, I've created a set of scripts to help test, debug, fix and install ros-melodic packages on archlinux. Check out this github repo.

fanjiang commented on 2019-02-15 02:15

@vegarab Remove ros-melodic-cpp-common and clean the AUR cache of it.

the culprit file got embedded into the package when built.

bionade24 commented on 2019-02-14 15:43

@vegarab: I don't know what you did wrong, but it works for me(Of course, you have to work-around the bugs). I would clean the cache of your AUR helper and try again, I suppose to use pikaur, but yay is good to. In near future I'll provide binaries.

vegarab commented on 2019-02-14 14:51

With @Cubimon I am still not able to build this. First attempt at install manages to install just over 100 packages (of the 320-something dependencies). After attempting to install 4 times (seemed like there were some circular dependencies), it is no longer able to install any of the 147 remaining packages due to missing dependencies.

I'm using packer to install. As mentioned, during the fourth install attempt packer finds 147 dependencies but none of them can be installed due to missing dependencies - but all of the mentioned missing dependencies are part of the initial 147 dependencies.