Package Details: gazebo 11.14.0-2

Git Clone URL: https://aur.archlinux.org/gazebo.git (read-only, click to copy)
Package Base: gazebo
Description: A multi-robot simulator for outdoor environments
Upstream URL: https://classic.gazebosim.org/
Licenses: Apache
Submitter: None
Maintainer: acxz
Last Packager: acxz
Votes: 35
Popularity: 0.000062
First Submitted: 2008-10-18 22:59 (UTC)
Last Updated: 2023-12-11 14:35 (UTC)

Dependencies (34)

Sources (1)

Pinned Comments

billypilgrim commented on 2022-05-09 16:04 (UTC)

Development is on Github: https://github.com/acxz/gazebo-arch Please open issues and PRs there instead of commenting.

Latest Comments

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 Next › Last »

bchretien commented on 2015-04-30 02:42 (UTC)

Note: compilation currently fails with the new Boost release (1.58). For more information: https://bitbucket.org/osrf/gazebo/issue/1590/build-fails-with-boost-158

bchretien commented on 2015-02-05 10:53 (UTC)

@kartikmohta: it still used to bug with Ogre 1.9 the last time I tested, but I'll check if everything appears to be fine with the 5.0.1 release. @LikeSmith: thanks for reporting this. For /usr/lib64, this is due to a change in the latest pacman which screws things up with CMake-based PKGBUILDs on 64-bit systems (fixable by setting CMAKE_INSTALL_LIBDIR to "lib"). For the md5sum, this is weird (AFAIK they don't provide any hash so this is based on the local version I downloaded a while back). Since Gazebo 5 has been released, this will be updated anyway. As for ruby, the dependency may be ruby-ronn for the doc. I'll update the PKGBUILD soon.

LikeSmith commented on 2015-02-05 04:52 (UTC)

A couple things from my experience installing. Currently, the md5sum for the package is incorrect, also, I had to install ruby before gazebo would install (I think it required for sdformat). I've also been getting issues because "/usr/lib64 exists in filesystem" If i move lib64 to lib64.back, the install works, but it creates a new lib64 directory. The original lib64 is a symlink to the regular lib directory. Is there a solution to this problem that doesn't involve getting rid of the lib64 symlink?

kartikmohta commented on 2015-01-08 02:53 (UTC)

I think you can change the ogre-1.8 dependency to just ogre, Gazebo compiles fine with ogre 1.9 which is in the official repos. Or is that done due to some requirement of the optional dependencies?

bchretien commented on 2015-01-02 19:25 (UTC)

@sfranchi: hmmm actually the install script is still bundled so the explanation is normally done at the end of the install: > Now you need to export some Gazebo variables: > If you're using bash:" > echo 'source /usr/share/gazebo/setup.sh' >> ~/.bashrc" > source ~/.bashrc"

bchretien commented on 2015-01-02 19:14 (UTC)

@sfranchi: I guess I can add a message for those who are not aware of this.

sfranchi commented on 2015-01-02 16:05 (UTC)

@bchretien: Thanks that fixed it. I must have missed that I was supposed to run that sh file.

bchretien commented on 2014-12-30 00:55 (UTC)

@sfranchi: did you source /usr/share/gazebo/setup.sh? Can you check that it contains the proper LD_LIBRARY_PATH export?

sfranchi commented on 2014-12-29 22:14 (UTC)

I get an error when trying to launch the latest gazebo from a fresh install: [code] gazebo: error while loading shared libraries: libOgreRTShaderSystem.so.1.8.1: cannot open shared object file: No such file or directory [/code] ogre was installed as a prereq, and the library file is located in /opt/OGRE-1.8/lib Any idea on how to fix this?

bchretien commented on 2014-08-11 21:38 (UTC)

@mattre: thanks for the warning, update done ;-)

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 Next › Last »