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

Git Clone URL: (read-only, click to copy)
Package Base: ros-melodic-desktop-full
Description: ROS - A metapackage to aggregate several packages.
Upstream URL:
Keywords: melodic morena robot robotics ros
Licenses: BSD
Submitter: GPereira
Maintainer: bionade24 (jwhendy)
Last Packager: bionade24
Votes: 12
Popularity: 0.014917
First Submitted: 2018-05-13 18:47
Last Updated: 2020-09-21 17:26

Pinned Comments

bionade24 commented on 2019-04-09 19:13

We moved our Development to Github: Please open issues there instead of commenting.

ROS binary Repo (Thirdparty):
pacman-key --recv-keys CB222E7EBC11D682AAC8B317A4A0D73114FDE6FC
pacman-key --edit-key CB222E7EBC11D682AAC8B317A4A0D73114FDE6FC
Add this to your pacman.conf:

Server =

Please vote for getting these packages into community repo.

Latest Comments

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

GPereira commented on 2018-09-22 11:59

I can roll back my edits. But that will mean python 2 will be used

GPereira commented on 2018-09-22 11:58

Can you further explain what that does? Thanks for your input!

stones commented on 2018-09-20 16:04

Well, apparently until now, there are some packages that still have the same problem of the CMake files, some packages points to the wrong directory for Cmake.

Do we have any contact with the maintainer ?? I need to install all the ros melodic. I am not imagining my self modifying each package manually

miramur commented on 2018-09-14 07:33

EDIT: Finally built and installed (no word yet on runtime)! Tips and Tricks:

  • Build Ogre v1.10.12 manually, remove ogre-1.9 as a dependency of rviz and remove ogre as a dependency of gazebo
  • A couple header files are out-of-date. Look for my comments in relevant packages when you hit that build error.
  • You might get a python2 -> python3 error (e.g. a print() call without parentheses). Honestly, easiest fix for those for me was to just pause the build after cloning (^Z) and editing those errors out manually.

Best of luck! This literally took forever to install, since most PKGBUILDs required the changed cmake directory.

In the middle of a long, arduous journey to build this. It's been said before (making a note more for myself): many of the PKGBUILDS in the deps point to the wrong folder for cmake. Specifically, pointing to the root directory of the repo instead of the specific package sub-directory.

Example in ros-melodic-roscpp-serialization, line 64:

-        cmake ${srcdir}/${_dir} \
+        cmake ${srcdir}/${_dir}/roscpp_serialization \

In the meantime, if you encounter an error like:

CMake Error: The source directory "<path>/ros-melodic-cpp-common/src/ros-melodic-cpp-common" does not appear to contain CMakeLists.txt.

That's the issue. Note that many packages pull the exact same repo, some packages are in "core," some in "tools," etc.

tsp commented on 2018-09-09 23:19

I think what Timonegk meant was that the package isn't deterministic anymore. You could build it with the same PKGBUILD on different days and end up with different results because upstream isn't tracking a specific version (AFAIK), it's fluid.

GPereira commented on 2018-09-09 18:00

No, that is not breaking anything. I am trying to make it run on python 3 that's all. Sorry for publishing not working state packages.

timonegk commented on 2018-09-09 15:22

Why are you using the git upstream instead of the tarball releases for melodic? That breaks package versioning.

tsp commented on 2018-09-09 09:11

A lot of packages have broken PKGBUILDs since the most recent update. The cmake call needs to be updated to point to the specific directory in the sources.

So for example the ros-melodic-map-msgs package:

    # Build the project.
    cmake ${srcdir}/${_dir} \
        -DCMAKE_BUILD_TYPE=Release \
        -DCMAKE_INSTALL_PREFIX=/opt/ros/melodic \
        -DPYTHON_EXECUTABLE=/usr/bin/python3 \
        -DPYTHON_INCLUDE_DIR=/usr/include/python3.7m \
        -DPYTHON_LIBRARY=/usr/lib/ \
        -DPYTHON_BASENAME=.cpython-37m \


    # Build the project.
    cmake ${srcdir}/${_dir}/map_msgs \
        -DCMAKE_BUILD_TYPE=Release \
        -DCMAKE_INSTALL_PREFIX=/opt/ros/melodic \
        -DPYTHON_EXECUTABLE=/usr/bin/python3 \
        -DPYTHON_INCLUDE_DIR=/usr/include/python3.7m \
        -DPYTHON_LIBRARY=/usr/lib/ \
        -DPYTHON_BASENAME=.cpython-37m \

timonegk commented on 2018-09-08 11:42

I think that it might be time to update the ros-melodic stack to python3.

Python2 end of life is in 2020 and Arch has used python3 as default since several years. For ROS Melodic, all packages should support python3 (see REP3).

I built every ros-melodic-* package in the AUR with python3 and all the packages were built successfully except of ros-melodic-tf2-py which was not yet python3.7 compatible. There is which fixes the problem but is not yet released. I added a custom patch to the PKGBUILD to resolve the issue until the next release. I will add a comment to the corresponding package later. (EDIT: here)

To update all the PKGBUILD files to python3, you can use the following command (in a folder where every subfolder contains one of the packages): sed -i -e "/ 2/-v 3/" -e "s/python2.7/python3.7m/" -e "s/ python2/ python/" -e "s/python2/python3/g" */PKGBUILD Explanation: The first expression fixes the version in the call of the fix-python-scripts editing the shebang line, the second expression fixes the library and include directories now ending with m, the third expression updates the package dependencies like python2-yaml -> python-yaml and the fourth expression updates the python binary from /usr/bin/python2 to /usr/bin/python3.

If you have further questions, feel free to ask or write an email.

LazyLucretia commented on 2018-06-28 11:51


In latest version of this package, gazebo fails to build as I stated here: One possible workaround is to downgrade ogre to 1.10.10-3 and boost/boost-libs to 1.66.0-3. This lets Gazebo to build, but breaks ros-melodic-diff-drive-controller's dependencies, along with many other packages that uses boost and ogre.