public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowi@redhat.com>
To: git-commits@fedoraproject.org
Subject: [flatpaks/flatpak-runtime] f45: Accept VulkanLayer extensions
Date: Fri, 11 Sep 2026 14:43:21 GMT	[thread overview]
Message-ID: <178913780181.1.919937395655801221.flatpaks-flatpak-runtime-aad99c9ede51@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : flatpaks/flatpak-runtime
            Branch : f45
            Commit : aad99c9ede5139eaa0a94120b768f241da4d3b30
            Author : Yaakov Selkowitz <yselkowi@redhat.com>
            Date   : 2026-03-02T21:13:16-05:00
            Stats  : +20/-0 in 2 file(s)
            URL    : https://src.fedoraproject.org/flatpaks/flatpak-runtime/c/aad99c9ede5139eaa0a94120b768f241da4d3b30?branch=f45

            Log:
            Accept VulkanLayer extensions

Vulkan has multiple search paths for metadata.  /etc/vulkan is used for the
GL extensions, while /usr/share/vulkan is used for additional layers.

---
diff --git a/container-sdk.in.yaml b/container-sdk.in.yaml
index d553804..6ac1268 100644
--- a/container-sdk.in.yaml
+++ b/container-sdk.in.yaml
@@ -30,6 +30,12 @@ flatpak:
             no-autodownload: true
             download-if: have-kernel-module-nvidia
             autoprune-unless: have-kernel-module-nvidia
+        @ID_PREFIX@.Platform.VulkanLayer:
+            directory: lib64/vulkan
+            add-ld-path: lib
+            merge-dirs: share/vulkan/implicit_layer.d;share/vulkan/explicit_layer.d;
+            subdirectories: true
+            no-autodownload: true
     finish-args: >
         --env=ALSA_CONFIG_DIR=/usr/share/alsa
         --env=ALSA_CONFIG_PATH=/usr/share/alsa/alsa.conf
@@ -83,6 +89,10 @@ flatpak:
         # Provide driver implementations with GL extensions
         rm -f /usr/lib64/libdrm_*.so*
 
+        # Create symlinks to expected locations from Vulkan extensions
+        rm -fr /usr/share/vulkan
+        ln -s ../lib64/vulkan/share/vulkan /usr/share/vulkan
+
         touch -d @0 /usr/share/fonts /usr/share/fonts/*
         fc-cache -rs
 

diff --git a/container.in.yaml b/container.in.yaml
index f5d932a..3ecb1e8 100644
--- a/container.in.yaml
+++ b/container.in.yaml
@@ -30,6 +30,12 @@ flatpak:
             no-autodownload: true
             download-if: have-kernel-module-nvidia
             autoprune-unless: have-kernel-module-nvidia
+        @ID_PREFIX@.Platform.VulkanLayer:
+            directory: lib64/vulkan
+            add-ld-path: lib
+            merge-dirs: share/vulkan/implicit_layer.d;share/vulkan/explicit_layer.d;
+            subdirectories: true
+            no-autodownload: true
     finish-args: >
         --env=ALSA_CONFIG_DIR=/usr/share/alsa
         --env=ALSA_CONFIG_PATH=/usr/share/alsa/alsa.conf
@@ -84,6 +90,10 @@ flatpak:
         # Provide driver implementations with GL extensions
         rm -f /usr/lib64/libdrm_*.so*
 
+        # Create symlinks to expected locations from Vulkan extensions
+        rm -fr /usr/share/vulkan
+        ln -s ../lib64/vulkan/share/vulkan /usr/share/vulkan
+
         touch -d @0 /usr/share/fonts /usr/share/fonts/*
         fc-cache -rs
 

                 reply	other threads:[~2026-09-11 14:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178913780181.1.919937395655801221.flatpaks-flatpak-runtime-aad99c9ede51@fedoraproject.org \
    --to=yselkowi@redhat.com \
    --cc=git-commits@fedoraproject.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