[Backport wrynose] Add chromium browser support - #475
Ricardo Salveti (ricardosalveti) merged 5 commits into
Conversation
|
Please rebase |
944f393 to
6637b9f
Compare
Done !! |
|
Sorry, but I just noticed that the cherry-pick's were done without -x, and so we are left without a record of the origin change. Can you please do it again with |
070b45b to
5840d9a
Compare
Include the `chromium-ozone-wayland` package in the image to support user-space web demonstrations on the Weston Wayland compositor. Exclude demo image from world build by adding EXCLUDE_FROM_WORLD = "1" to the image recipe. This image includes Chromium, which is highly resource-intensive and significantly increases CI/CD pipeline build times. Setting this variable prevents 'bitbake world' from automatically building this image during automated regression testing, while still allowing developers to build the image explicitly when needed. Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@oss.qualcomm.com> (cherry picked from commit da29e28) Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@oss.qualcomm.com>
Introduce the proprietary variant of the multimedia demo image to bundle user-space applications with proprietary Qualcomm binaries. Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@oss.qualcomm.com> (cherry picked from commit 79b179c) Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@oss.qualcomm.com>
5840d9a to
12fdf39
Compare
I did what you have requested. Please let me know if there any any further feedback. |
Integrate `qcom-multimedia-demo-image` and its proprietary variant into the CI build matrix. This incorporates framework demonstrations and user-space applications into the automated pipeline. - Include the `meta-browser` layer to support Chromium-based apps. - Include `qcom-distro-multimedia-image.yml` configuration. - Set build targets for both open-source and proprietary demo images. Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@oss.qualcomm.com> (cherry picked from commit 23999bc) Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@oss.qualcomm.com>
Add a nightly schedule trigger running Monday to Saturday at 3:00 AM UTC so that build-yocto.yml serves as the daily build. Sunday is reserved for the weekly workflow. Introduce a weekly profile that gates the multimedia demo image builds for qcom-armv8a, rb3gen2-core-kit and glymur-crd, each using the default kernel. These builds are excluded from nightly and PR builds by a step-level if condition. Mark those matrix entries with a profile key on the distro entry and test that key in the condition instead of matching the image name, so that adding another weekly-only target is a matrix change and does not touch the condition. Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@oss.qualcomm.com> (cherry picked from commit 8f09c8b) Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@oss.qualcomm.com>
Add a weekly build workflow that triggers every Sunday at 3:00 AM UTC. The weekly build calls build-yocto.yml with profile=weekly which, in addition to the standard nightly builds, also builds the multimedia demo and proprietary demo images for qcom-armv7a, qcom-armv8a, rb3gen2-core-kit and glymur-crd across default, 6.18, rt-6.18 and u-boot kernel combinations. Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@oss.qualcomm.com> (cherry picked from commit 86b2ee1) Signed-off-by: Ashwin Prabhakar <ashwin.prabhakar@oss.qualcomm.com>
12fdf39 to
43357c2
Compare
|
Building locally to validate this first. |
Ricardo Salveti (ricardosalveti)
left a comment
There was a problem hiding this comment.
Took a substantial amount of tries, hours and what not, but built fine in the end :-)
Ricardo Salveti (@ricardosalveti) thanks for trying it out. I also tried at my end and it does take a while 😃. Jose Quaresma (@quaresmajose) can you please review and let me know if this looks okay to you. |
269c8b1
into
qualcomm-linux:wrynose
Backport of #307 to wrynose