From: Justinizer <Justinizer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: fs-uae-launcher-3.0.5.
Date: Sat, 03 Apr 2021 04:42:19 +0200 [thread overview]
Message-ID: <20210403024219.J9do9CQXy2RjxujzDkuPADU1Otmbczx56YGXgndjWWY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29955@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
New comment by Justinizer on void-packages repository
https://github.com/void-linux/void-packages/pull/29955#issuecomment-812787788
Comment:
> ```
> /usr/share/fs-uae-launcher/OpenGL/DLLS/glut32.dll
> /usr/share/fs-uae-launcher/OpenGL/DLLS/glut64.dll
> /usr/share/fs-uae-launcher/OpenGL/DLLS/glut_README.txt
> /usr/share/fs-uae-launcher/OpenGL/DLLS/opengle32.vc7.dll
> /usr/share/fs-uae-launcher/OpenGL/DLLS/opengle32.vc9.dll
> /usr/share/fs-uae-launcher/OpenGL/DLLS/opengle64.vc9.dll
> ```
>
> are these dll's actually needed? Probably not?
```bash
cat /usr/share/fs-uae-launcher/OpenGL/DLLS/GLE_WIN32_README.txt
This is a Win32 version of the GLE library
compiled as a shared library (DLL) for use with
e.g. Python's ctypes foreign-function interface.
To install, copy the file gle32.dll to your system32
```
Seems not to be needed I will try to cut it out somehow...
next prev parent reply other threads:[~2021-04-03 2:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 21:12 [PR PATCH] " Justinizer
2021-04-02 22:04 ` Johnnynator
2021-04-02 22:17 ` [PR REVIEW] " ericonr
2021-04-03 2:38 ` [PR PATCH] [Updated] " Justinizer
2021-04-03 2:42 ` Justinizer [this message]
2021-04-03 3:09 ` Justinizer
2021-04-03 3:12 ` Justinizer
2021-04-03 3:26 ` [PR PATCH] [Updated] " Justinizer
2021-04-03 3:28 ` Justinizer
2021-04-03 3:28 ` Justinizer
2022-05-16 2:08 ` github-actions
2022-05-30 2:15 ` [PR PATCH] [Closed]: " github-actions
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=20210403024219.J9do9CQXy2RjxujzDkuPADU1Otmbczx56YGXgndjWWY@z \
--to=justinizer@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).