From: amak79 <amak79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Build RetroArch using OpenGL instead of OpenGLES
Date: Tue, 03 Aug 2021 06:03:19 +0200 [thread overview]
Message-ID: <20210803040319.-D703dPaHjdkVozGSCtn4x10wdN8qikO7i9HGmaHXjo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32246@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
New comment by amak79 on void-packages repository
https://github.com/void-linux/void-packages/issues/32246#issuecomment-890437664
Comment:
@TegarOk can you please re-open this issue.
I think I've made some sense of the many of RetroArch OpenGL/ES configure options.
```
--enable-opengl Enable OpenGL 2.0 support
--disable-opengl Disable OpenGL 2.0 support
--disable-opengl_core Disable Modern OpenGL driver support (GLES3+/GL3.2 core+), requires OpenGL.
--disable-opengl1 Disable OpenGL 1.1 support
--enable-opengles Enable Use GLESv2 instead of desktop GL
--enable-opengles3 Enable OpenGLES3 support
--enable-opengles3_1 Enable OpenGLES3.1 support
--enable-opengles3_2 Enable OpenGLES3.2 support
```
The `--enable-opengl_core` option will enable both OpenGL (3.2+) and OpenGL ES (3+) support. I mistakenly thought that `--enable-opengles` was needed for OpenGL ES support. I still don't know when this option should be used.
I've tested RetroArch with `opengl` enabled and `gles2` disabled on an RPi 3B+. RetroArch reports that OpenGL ES support is disabled and so far everything works.
I think I need to re-work the template to either disable `gles2` by default or drop it entirely.
@ericonr can you please add your thoughts on this issue.
next prev parent reply other threads:[~2021-08-03 4:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 15:10 [ISSUE] " TegarOk
2021-07-30 5:51 ` amak79
2021-07-30 7:14 ` amak79
2021-07-30 7:34 ` amak79
2021-07-30 7:35 ` amak79
2021-07-30 8:19 ` amak79
2021-07-30 8:21 ` amak79
2021-07-30 11:16 ` amak79
2021-07-30 11:41 ` amak79
2021-07-31 5:56 ` TegarOk
2021-07-31 5:56 ` TegarOk
2021-07-31 9:56 ` TegarOk
2021-07-31 10:47 ` amak79
2021-07-31 12:46 ` TegarOk
2021-07-31 12:57 ` amak79
2021-07-31 12:58 ` TegarOk
2021-07-31 13:11 ` amak79
2021-07-31 13:13 ` TegarOk
2021-08-01 0:46 ` TegarOk
2021-08-01 0:46 ` [ISSUE] [CLOSED] " TegarOk
2021-08-01 2:41 ` amak79
2021-08-03 4:00 ` ericonr
2021-08-03 4:03 ` amak79 [this message]
2021-08-03 4:05 ` amak79
2021-08-03 6:17 ` amak79
2021-08-03 6:37 ` amak79
2021-08-03 8:35 ` amak79
2021-08-03 12:07 ` amak79
2021-08-03 14:01 ` ericonr
2021-08-03 15:21 ` st3r4g
2021-08-09 2:14 ` [ISSUE] [CLOSED] " ericonr
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=20210803040319.-D703dPaHjdkVozGSCtn4x10wdN8qikO7i9HGmaHXjo@z \
--to=amak79@users.noreply.github.com \
--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).