Package Details: retroarch-rbp-git

Git Clone URL: (read-only)
Package Base: retroarch-rbp-git
Description: Reference frontend for the libretro API.
Upstream URL:
Licenses: GPL
Groups: libretro
Conflicts: retroarch
Provides: retroarch, retroarch-git
Submitter: cecton
Maintainer: cecton
Last Packager: cecton
Votes: 3
Popularity: 0.219540
First Submitted: 2016-04-30 15:20
Last Updated: 2017-12-27 00:11

Dependencies (17)

Required by (5)

Sources (1)

Pinned Comments

cecton commented on 2016-04-30 17:04

Pull requests are welcome on github:

Latest Comments

jewelux commented on 2018-01-10 23:43

@cecton Seems the incompatibility with mupen caused by Sorry for my wrong conclusion.

cecton commented on 2017-12-26 21:30

Thanks @jewelux I will revert that changes

jewelux commented on 2017-12-26 21:18

New build instruction seems to break compatibility to some cores e.g. mupen64plus. To recover compatibility you should remove the line starts with "export PKG_CONFIG_PATH ..." Tested on RPI2

cecton commented on 2017-10-29 20:53

@MattScherbatsky sorry not tested on Rpi3. Maybe you can fix it?

MattScherbatsky commented on 2017-10-29 19:03

Raspberry Pi 3, new installation and I get this error:

CC deps/miniupnpc/minisoap.c
CC tasks/task_decompress.c
LD retroarch
/usr/bin/ld: obj-unix/gfx/drivers/dispmanx_gfx.o: undefined reference to symbol 'vc_dispmanx_display_close'
/opt/vc/lib/ error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make: *** [Makefile:148: retroarch] Error 1

jewelux commented on 2017-07-04 11:24

@cecton The build option holdver is helpful if you already got (and saved) the source code of a working version. But usually it is not the case if you are using a package manager like yaourt or you are installing the package for the first time.
So it could be make sense to provide both: a package "retroarch-rbp" for the last stable release and "retroarch-rbp-git" for the current development branch.

Anyway thx for the working 1.6.1 update!

cecton commented on 2017-07-04 09:31

@jewelux I put back the Git version again. The build seems to work now.

Now I wonder. How people do usually handle this when the master branch is broken? But I think I have my answer, there is an option that probably helps in makepkg:

--holdver Do not update VCS sources

jewelux commented on 2017-07-03 20:26

@cecton: Last link-button ("Submit Request") in the "Package Actions" box in the right upper corner of these page. To submit a merge-request is the only way to transfer votes, comments, etc. to a new (and renamed) package base.
Good luck!

cecton commented on 2017-07-03 18:34

@jewelux thx I'm giving it a shot now btw.... :D actually I can't find the button to create a new package..... -_-

jewelux commented on 2017-07-03 15:21

@cecton: Today, I successfully build v1.6.1 with these pkgbuild locally on a rpi2. So now it should work without any build errors.
To rename a package: a) create a new package b) select the package option "Submit Request" c) create a new merge-request d) maybe set the replaces-variable in the pkgbuild.
Hope it helps. Thx.

All comments