You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I notice that other layers have put chromium bbappends and patches in dynamic-layers directories, which is what I think you'll want to do too, although I confess I don't know that much about dynamic layers. Doing the following solved it for me, but I can't test whether it keeps the patch when chromium is present:
diff --git a/conf/layer.conf b/conf/layer.conf
index 2d8ff51..dec39d7 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -23,6 +23,9 @@ BBFILES_DYNAMIC += " \
qt6-layer:${LAYERDIR}/dynamic-layers/qt6-layer/*/*/*.bb \
qt6-layer:${LAYERDIR}/dynamic-layers/qt6-layer/*/*/*.bbappend \
\
+ browser:${LAYERDIR}/dynamic-layers/browser/*/*/*.bb \
+ browser:${LAYERDIR}/dynamic-layers/browser/*/*/*.bbappend \
+ \
swupdate:${LAYERDIR}/dynamic-layers/swupdate/*.bb \
swupdate:${LAYERDIR}/dynamic-layers/swupdate/*.bbappend \
\
diff --git a/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend b/dynamic-layers/browser/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend
similarity index 100%
rename from recipes-browser/chromium/chromium-ozone-wayland_%.bbappend
rename to dynamic-layers/browser/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend
diff --git a/recipes-browser/chromium/files/0001-Remove-DRI-dependency.patch b/dynamic-layers/browser/recipes-browser/chromium/files/0001-Remove-DRI-dependency.patch
similarity index 100%
rename from recipes-browser/chromium/files/0001-Remove-DRI-dependency.patch
rename to dynamic-layers/browser/recipes-browser/chromium/files/0001-Remove-DRI-dependency.patch
The text was updated successfully, but these errors were encountered:
I notice that other layers have put chromium bbappends and patches in dynamic-layers directories, which is what I think you'll want to do too, although I confess I don't know that much about dynamic layers. Doing the following solved it for me, but I can't test whether it keeps the patch when chromium is present:
The text was updated successfully, but these errors were encountered: