From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: libretro-mupen64plus: update to 20190611
Date: Tue, 11 Jun 2019 19:36:50 +0200 [thread overview]
Message-ID: <20190611173650.Suy-yWzyh-UTm5-pyTkmZS9YwNDtT0KydPx4oDVfsTc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12400@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/12400#issuecomment-500947458
Comment:
Looks like this is now fixed. Total change log:
- Added new build options `gles`, `gles3` which force GLES2 and GLES3 respectively when used with `opengl`.
- Made it possible to use `opengl` with `rpi`, which effectively uses Mesa (setting `platform=rpi,mesa` for the build)
- Fixed `rpi` (needed to install `rpi-userland-devel` instead of `rpi-firmware`)
- Fixed i686 (needed to install `nasm` on host)
- `aarch64` uses GLES2
- `armv6/7` uses rpi (i.e. as before)
- everything else uses standard OpenGL, and all platforms are now enabled.
Questions:
- Since raspberry pi is hardly a generic target, should we remove it and create a separate `-rpi` suffixed package for that, then use the same settings on `armv*` and `aarch64*`? We already have this elsewhere; see e.g. `EmulationStation` and `EmulationStation-rpi`.
next prev parent reply other threads:[~2019-06-11 17:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 15:53 [PR PATCH] " voidlinux-github
2019-06-11 15:54 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 15:54 ` voidlinux-github
2019-06-11 16:20 ` voidlinux-github
2019-06-11 16:20 ` voidlinux-github
2019-06-11 16:21 ` voidlinux-github
2019-06-11 16:41 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 16:41 ` voidlinux-github
2019-06-11 16:42 ` voidlinux-github
2019-06-11 17:02 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 17:02 ` voidlinux-github
2019-06-11 17:03 ` voidlinux-github
2019-06-11 17:25 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 17:25 ` voidlinux-github
2019-06-11 17:33 ` voidlinux-github
2019-06-11 17:33 ` voidlinux-github
2019-06-11 17:33 ` voidlinux-github
2019-06-11 17:36 ` voidlinux-github [this message]
2019-06-11 17:44 ` voidlinux-github
2019-06-11 17:51 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 17:51 ` voidlinux-github
2019-06-11 18:50 ` voidlinux-github
2019-06-11 19:36 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 19:36 ` voidlinux-github
2019-06-11 19:36 ` voidlinux-github
2019-06-11 19:58 ` voidlinux-github
2019-06-11 20:25 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 20:25 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:08 ` voidlinux-github
2019-06-15 12:43 ` [PR PATCH] [Merged]: " voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190611173650.Suy-yWzyh-UTm5-pyTkmZS9YwNDtT0KydPx4oDVfsTc@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).