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.006379
First Submitted: 2008-10-18 22:59 (UTC)
Last Updated: 2023-12-11 14:35 (UTC)

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 2 3 4 5 6 7 .. 33 Next › Last »

bobosito commented on 2022-02-14 04:36 (UTC)

It's no problem. Just as long as someone is on it. Do you have a separate repository where people can create merge requests for the package build?

billypilgrim commented on 2022-02-13 12:06 (UTC)

@bobosito: Yeah, exactly!

Apologies to all that this package has been out of date for so long. Currently gazebo requires patching to work with the latest version of tbb and I haven't yet had a chance to rebase my patchset onto the latest version.

bobosito commented on 2022-02-12 20:56 (UTC)

The patching path is correct. After the patch is downloaded a link is made to the patch file inside of the src folder.

ashfaqf commented on 2022-02-12 12:56 (UTC)

I think the patching is done from the wrong path. Shouldnt it be:

patch -p1 < ../../fix-for-tbb-2021.patch

bobosito commented on 2022-02-10 22:05 (UTC)

It's no problem. Sorry for the late reply. Everyone has to start somewhere. Just append -j3 to the ninja command in the pkgbuild. I don't think ninja reads parallel job number from any environment variable.

Kanishk598 commented on 2022-02-02 21:28 (UTC)

@bobosito, I am new to package building in Arch. Can you please tell me what changes can I make in my files to compile this package? Should I append $NINJAFLAGS="-J2" to the line inside build() function having ninja? What else can I do? I have a 4 core laptop.

bobosito commented on 2022-01-21 04:55 (UTC) (edited on 2022-01-21 05:04 (UTC) by bobosito)

I got it building on my system without hanging by changing the number of parallel jobs in the PKGBUILD.

I tried changing the number of parallel jobs in MAKEFLAGS in /etc/makepkg.conf. Apparently, ninja only uses an environment variable called NINJA_STATUS and you can't pass flags to ninja using it, so that doesn't work. You could pass MAKEFLAGS to ninja as an argument, but you shouldn't do that cuz ninja doesn't support all of make's flags.

Could write up a bashscript to strip the job number from makeflags and put it into ninja as command line argument or switch to make?

I feel like unless there's something in the configuration to fix that memory issue that I'm missing, it should be handled in the PKGBUILD cuz it would mean for some users it will hang unless they edit the PKGBUILD.

bobosito commented on 2022-01-21 03:55 (UTC) (edited on 2022-01-21 05:01 (UTC) by bobosito)

My PC runs out of memory while building, and I'm not building in /tmp. What changes would I have to make to /etc/makepkg.conf?

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