Package Details: libmgba-git 0.10.0.r7169.b5e94b0ab-1

Git Clone URL: (read-only, click to copy)
Package Base: mgba-git
Description: Shared library of mGBA
Upstream URL:
Licenses: custom:MPL2
Conflicts: libmgba
Provides: libmgba
Submitter: Vaporeon
Maintainer: Vaporeon
Last Packager: Vaporeon
Votes: 8
Popularity: 0.000000
First Submitted: 2014-12-15 01:23 (UTC)
Last Updated: 2021-12-20 05:01 (UTC)

Required by (2)

Sources (1)

Latest Comments

1 2 Next › Last »

kode54 commented on 2021-09-30 00:53 (UTC)

Hmm, I guess it's fixed, then.

Vaporeon commented on 2021-09-29 14:12 (UTC)

Odd, when I build the current package it has the correct version in the compiled binaries.

kode54 commented on 2021-09-29 02:31 (UTC)

The CMake scripts within the mGBA project somehow do not detect their Git repository properly, and instead somehow pick up the commit hash and repository state of the AUR package above the source directory. They will report $currenthash of the AUR package, and "dirty" because makepkg altered the PKGBUILD to the latest tag and hash from the mGBA repository.

aldelaro5 commented on 2021-09-28 01:14 (UTC) (edited on 2021-09-28 01:15 (UTC) by aldelaro5)

So this aur package is behaving strangely because the version implies it is building the latest from master, but it doesn't seem to do this because I got a pr merged which created the commit 6a05dba8797316c0e75f6e226031bbc658defc76, but what I actually get is a version at commit 96e1ae42729c38f11bc29196323dffe5b6537e20, is this normal? I verified that the binary does not have the changes in the PR.

(you can verify by doing mgba-qt --version, the package will have the correct version, not the binary)

Vaporeon commented on 2020-11-10 13:35 (UTC)

I am aware, it's because of how the cmake thing is written. I have not looked into bypassing it or anything so it's correct. They can be written to work in build environments like this though, for instance the "invader-git" package does not have this issue.

kode54 commented on 2020-11-10 08:46 (UTC)

Thought I'd point out that the project's version.cmake thing which determines the Git revision and inserts it into the binaries, is somehow running the git describes on the AUR package's Git repository and not mGBA's.

Ppjet6 commented on 2016-08-01 22:24 (UTC)

Can you add -DCMAKE_INSTALL_LIBDIR=lib into the build function, please. The package currently fails to install to /usr/lib64

mac1202 commented on 2015-03-13 12:06 (UTC)

Thank you.

Vaporeon commented on 2015-03-13 01:31 (UTC)

Ok I made the libretro core its own package.