From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: dan <i@dan.games>, 59416@debbugs.gnu.org
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#59416] [PATCH staging 0/1] gnu: ppsspp: Drop OGLCompiler andOSDependent from glslang libs.
Date: Tue, 21 Mar 2023 09:09:53 -0400 [thread overview]
Message-ID: <874jqes126.fsf_-_@gmail.com> (raw)
In-Reply-To: <6abd2ac20099d8d67b6d3e051ec0a5c412b41ea1.camel@gmail.com> (Liliana Marie Prikler's message of "Tue, 22 Nov 2022 21:16:02 +0100")
Hi Dan,
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> Am Montag, dem 21.11.2022 um 01:56 +0800 schrieb dan:
>> The recent update on vulkan-sdk packages breaks the build of ppsspp
>> on the staging branch[1]. This patch tries to drops unused glslang
>> libs from the CMakeLists.txt file of ppsspp, following the recent
>> changes made on glslang[2].
>>
>> [1]: http://ci.guix.gnu.org/build/1751089/details
> You probably want to update this link, but ppsspp on staging is
> currently waiting on CI.
>
>> [2]:
>> https://github.com/KhronosGroup/glslang/commit/7cd519511c32d7e86d901c7ed231cb84c652d18d
>>
>> dan (1):
>> gnu: ppsspp: Drop OGLCompiler and OSDependent from glslang libs.
> Have you tested whether this actually works as intended, i.e. whether
> OpenGL and Linux-specific features continue to work?
Gentle ping :-).
--
Thanks,
Maxim
prev parent reply other threads:[~2023-03-21 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 17:56 [bug#59416] [PATCH staging 0/1] gnu: ppsspp: Drop OGLCompiler andOSDependent from glslang libs dan
2022-11-20 18:00 ` [bug#59416] [PATCH 1/1] gnu: ppsspp: Drop OGLCompiler and OSDependent " dan
2022-11-22 20:16 ` [bug#59416] [PATCH staging 0/1] gnu: ppsspp: Drop OGLCompiler andOSDependent " Liliana Marie Prikler
2023-03-21 13:09 ` Maxim Cournoyer [this message]
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=874jqes126.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=59416@debbugs.gnu.org \
--cc=i@dan.games \
--cc=liliana.prikler@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.