From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: [RFC] SDL2: unify build options on all archs, don't enable rpi for arm*
Date: Wed, 22 Jan 2020 19:17:03 +0100 [thread overview]
Message-ID: <20200122181703.vrjhhKYbKG1bqfNQuuLlEnuwEyP4zaqef_ijGDGWUqQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18298@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
There's a merged pull request on the void-packages repository
[RFC] SDL2: unify build options on all archs, don't enable rpi for arm*
https://github.com/void-linux/void-packages/pull/18298
Description:
Currently `rpi-userland-devel` provides the some `pkgconfig` files as `libglvnd-devel`
```
/usr/lib/pkgconfig/glesv2.pc
/usr/lib/pkgconfig/egl.pc
```
Which makes it impossible to build something that depends on `SDL2-devel` and `libglvnd-devel`/`MesaLib-devel` since `rpi-userland-devel` will be pulled in.
Also if I'm not mistaken, the rpi build option is currently nevertheless broken. SDL2 only searches for `libGLESv2.so.2` if `--enable-video-rpi` is not set, and `rpi-userland` is only providing `libGLESv2.so`. The code of SDL does runtime checks whether it is a rpi so enabling it shouldn't break non rpi's. But everything should be less broken as the current state. So if anyone wanna fix the rpi build option feel free to do so.
next prev parent reply other threads:[~2020-01-22 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 3:50 [PR PATCH] " voidlinux-github
2020-01-14 3:53 ` voidlinux-github
2020-01-17 14:58 ` voidlinux-github
2020-01-17 15:15 ` voidlinux-github
2020-01-19 21:23 ` voidlinux-github
2020-01-19 21:25 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-22 18:17 ` voidlinux-github [this message]
2020-01-25 23:27 ` 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=20200122181703.vrjhhKYbKG1bqfNQuuLlEnuwEyP4zaqef_ijGDGWUqQ@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).