Package Details: ignition-cmake 3.4.1-1

Git Clone URL: https://aur.archlinux.org/ignition-cmake.git (read-only, click to copy)
Package Base: ignition-cmake
Description: A set of CMake modules that are used by the C++-based Gazebo projects.
Upstream URL: https://gazebosim.org/libs/cmake
Licenses: Apache
Submitter: racko
Maintainer: acxz
Last Packager: acxz
Votes: 2
Popularity: 0.000000
First Submitted: 2018-02-24 09:35 (UTC)
Last Updated: 2023-11-22 03:17 (UTC)

Pinned Comments

acxz commented on 2022-05-09 16:16 (UTC)

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

Latest Comments

1 2 3 Next › Last »

acxz commented on 2022-05-09 16:16 (UTC)

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

acxz commented on 2022-05-08 19:21 (UTC)

The urls have also been updated.

AchmadFathoni commented on 2022-05-08 12:32 (UTC)

Thanks drr21. Now it's fixed

drr21 commented on 2022-05-08 12:19 (UTC)

Package is broken. Somehow now the name of the downloaded folder starts with gz-make-ignitioninstead of ign-cmake-ignition

MaEtUgR commented on 2019-10-25 10:09 (UTC)

Thanks for the insight! Now I understand it a lot better. I saw you already had a discussion with the gazebo maintainer about requirement versioning... Let's see what happens. Since it now builds out of the box I'm super happy. Thanks and happy coding.

acxz commented on 2019-10-25 05:00 (UTC)

I see, yes --noconfirm is definitely convenient and useful.

I am not sure how yay decides on the priority of packages, but I believe it will match the package name letter for letter first, which means if gazebo requests ignition-cmake, yay gives you ignition-cmake before any other version of it. This is expected and welcome behavior, tho.

The only way to resolve this issue so that users do not accidentally download the wrong ignition-cmake version is to manually require ignition-cmake=0 in the gazebo PKGBUILD. This will also fix the issue occurring when using --noconfirm.

The reason this dependency issue is getting covered up is because there is another dependency that gazebo requires which installs ignition-cmake-0 so gazebo does not end up griping about the wrong ignition-cmake version. Basically, gazebo is installing extraneous packages that are not needed.

MaEtUgR commented on 2019-10-25 04:50 (UTC)

I believe --noconfirm is hiding the issue for you.

I only use it to verify that it's scriptable, easily repeatable, also works in docker.

and ignition-cmake-0, the latter of which is the correct one to compile gazebo with.

Then it should be the default right? Otherwise every noob user like me will do the wrong thing.

acxz commented on 2019-10-25 04:45 (UTC)

I believe --noconfirm is hiding the issue for you. If you do not use that flag, you will be given the option to choose between this package and ignition-cmake-0, the latter of which is the correct one to compile gazebo with. But yes I agree with you that the issue needs to be resolved in the gazebo PKGBUILD.

MaEtUgR commented on 2019-10-25 02:58 (UTC) (edited on 2019-10-25 03:01 (UTC) by MaEtUgR)

You seem to have this notion that this package is required for gazebo

Yes because if I install gazebo using yay -S gazebo --noconfirm the operation fails if ignition-cmake cannot be built and installed. I don't know the internals and I understood your comment before but the dependency seems to be configured somewhere.

EDIT: The PKGBUILD file of the gazebo AUR contains the line makedepends=('cmake' 'doxygen' 'ignition-cmake') I'll add a comment there to consider removing the dependency.

1 2 3 Next › Last »