forked from OSSystems/meta-browser
-
Notifications
You must be signed in to change notification settings - Fork 1
Fix MR branch for/review/ossystems/scarthgap/138.0.7204.157 #16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
adalessandro
wants to merge
12
commits into
brightsign:for/review/ossystems/scarthgap/138.0.7204.157
Choose a base branch
from
adalessandro:for/review/ossystems/scarthgap/138.0.7204.157
base: for/review/ossystems/scarthgap/138.0.7204.157
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rust 1.86 ships adler2, so the library name has to be adjusted accordingly. Signed-off-by: Alexander Stein <[email protected]>
…#882) This adds a section to the readme, explaining the solution to a build error discussed in OSSystems#845. Adding this in the readme makes it easier to be found. Signed-off-by: Matthias Schoepfer <[email protected]>
Release notes: https://chromereleases.googleblog.com/2025/05/stable-channel-update-for-desktop_14.html Build and patch changes: ------------------------ Added patches: * 0014-Revert-Remove-libavif-based-AVIF-decoder.patch * 0015-Revert-Remove-third_party-libavif.patch * 0017-rust-Use-adler-instead-of-adler2.patch * 0018-third_party-node-update_node_binaries-Update-nodejs-.patch Updated patches: * 0016-Disable-crabbyavif-to-fix-build-errors.patch * Rebased remaining patches. Removed patches: * 0015-Revert-Connect-the-Rust-log-crate-to-the-base-loggin.patch License changes: ---------------- Added licenses: * TBD Removed licenses: * TBD Updated licenses: * TBD Test-built: ----------- * chromium-ozone-wayland * master, clang, MACHINE=qemux86-64, qemuarm, qemuarm64 * chromium-x11 * master, clang, MACHINE=qemux86-64, qemuarm, qemuarm64 Signed-off-by: Ariel D'Alessandro <[email protected]>
Add configuration options to enable hardware video decoding using stateless V4L2 M2M device. This allows offloading e.g. h264 video playback to Hantro VPU on i.MX8MP where this was tested. To make that work, enable 'use-v4l2' and 'proprietary-codecs' PACKAGECONFIG. This commit was implemented with much great help from Jianfeng Liu . Signed-off-by: Marek Vasut <[email protected]>
The TST043015CNHX panel is a 480x272 panel. Chromium browser limits the minimum window width to 500px since commits: 6b0ecc1e4532c ("Set lower bound on contents pane size.") 580d6900dc7fc ("In tab dragging, the window size should be larger than its minimum size.") To make chromium browser usable on those tiny panels as well, reduce the minimum window width to 480px. The upstreaming of this change is in progress. Signed-off-by: Marek Vasut <[email protected]>
rust triple is not specialized in yocto for neon enabled arm targets.
Adds a patch to `filter_clang_args.py` to skip `-mbranch-protection` and `-mfpu=` flags when compiling Rust. These flags are specific to ARM clang and cause build issues on other architectures with Rust compiler. Upstream-Status: Inappropriate [specific to our build setup]
fixes: ../../media/gpu/v4l2/legacy/v4l2_video_decoder_backend_stateful.cc:450:20: error: non-constant-expression cannot be narrowed from type '__suseconds64_t' (aka 'long long') to 'long' in initializer list [-Wc++11-narrowing]
Removed -g flags from arm builds. arm linker is unable to link the image due to image size if -g flag is used: arm-poky-linux-gnueabi-ld.lld: error: output file too large: 7344071860 bytes
f5e682c
to
f22df04
Compare
Chromium 138+ uses its bundled libc++ and compiler-rt. To ensure the build system uses these and does not fall back to system-provided runtime libraries, explicitly pass the target triple and disable system stdlib++. This avoids linker errors caused by missing crtbeginS.o, crtendS.o, and libgcc when using Clang with a minimal sysroot. Release Notes: https://chromereleases.googleblog.com/2025/07/stable-channel-update-for-desktop_15.html Build and patch changes: ------------------------ Added patches: * 0011-fix-check_version-Only-compare-node.js-major-version.patch Updated patches: * 0009-Adjust-the-Rust-build-to-our-needs.patch Removed patches: * 0011-Revert-Allow-and-use-std-hardware_destructive_interf.patch * 0012-Revert-Set-Rust-symbol-visibility-to-hidden-when-C-s.patch * 0013-pdfium-Fix-missing-PDFiumAPIStringBufferAdapter-temp.patch * 0014-Revert-Remove-libavif-based-AVIF-decoder.patch * 0015-Revert-Remove-third_party-libavif.patch * 0016-Disable-crabbyavif-to-fix-build-errors.patch * 0016-Fix-adler-reference-for-Rust-1.86-and-later.patch * 0017-rust-Use-adler-instead-of-adler2.patch * 0018-third_party-node-update_node_binaries-Update-nodejs-.patch * 0020-rust-filter-out-arm-specific-flags-from-rust-compile.patch License changes: ---------------- Added licenses: * third_party/compiler-rt/src/LICENSE.TXT * third_party/libtess2/LICENSE * third_party/llvm-libc/src/LICENSE.TXT * third_party/net/third_party/mozilla_security_manager/LICENSE Removed licenses: * third_party/accessibility-audit/LICENSE * third_party/io_grpc_grpc_api/LICENSE * third_party/libavifinfo/LICENSE Updated licenses: * third_party/android_deps/libs/com_google_android_gms_play_services_auth/LICENSE -> third_party/android_deps/autorolled/committed/libs/com_google_android_gms_play_services_auth/LICENSE * third_party/android_deps/libs/com_google_android_gms_play_services_auth_api_phone/LICENSE -> third_party/android_deps/autorolled/committed/libs/com_google_android_gms_play_services_auth_api_phone/LICENSE * third_party/android_deps/libs/com_google_android_gms_play_services_auth_base/LICENSE -> third_party/android_deps/autorolled/committed/libs/com_google_android_gms_play_services_auth_base/LICENSE * third_party/android_deps/libs/com_google_android_gms_play_services_auth_blockstore/LICENSE -> third_party/android_deps/autorolled/committed/libs/com_google_android_gms_play_services_auth_blockstore/LICENSE * third_party/android_deps/libs/com_google_android_gms_play_services_fido/LICENSE -> third_party/android_deps/autorolled/committed/libs/com_google_android_gms_play_services_fido/LICENSE * third_party/android_deps/libs/com_google_android_libraries_identity_googleid_googleid/LICENSE -> third_party/android_deps/autorolled/committed/libs/com_google_android_libraries_identity_googleid_googleid/LICENSE * third_party/expat/src/expat/COPYING * third_party/libjpeg_turbo/LICENSE Test-built: ----------- * chromium-ozone-wayland * MACHINE=qemux86-64, qemuarm, qemuarm64 * chromium-x11 * MACHINE=qemux86-64, qemuarm, qemuarm64 Test dependencies: ------------------ * URI: git://git.yoctoproject.org/poky - branch: scarthgap - revision: ac257900c33754957b2696529682029d997a8f28 * URI: git://git.openembedded.org/meta-openembedded - layers: meta-oe - branch: scarthgap - revision: 491671faee11ea131feab5a3a451d1a01deb2ab1 * URI: git://github.com/kraj/meta-clang - branch: scarthgap-clang20 - revision: 76596813cd0061bd9818a80926e6900af61fcaa0 * URI: git://git.yoctoproject.org/meta-lts-mixins - branch: scarthgap/rust - revision: 96deb45139df027473faf0938fe006d33c45c375 Signed-off-by: Caner Altinbasak <[email protected]> Signed-off-by: Ariel D'Alessandro <[email protected]>
scarthgap doesn't define UNPACKDIR, use WORKDIR instead.
Chromium138/Electron37 requires Node.js v22.11.0. Add a new recipe to use updated version.
f22df04
to
5540b9c
Compare
@caneraltinbasak sorry, I have to push another update. |
Updated the README with the proper hashes for scarthgap. This is now ready to review. |
Can you please fix the merge conflicts. |
Same answer here as #15 , let's follow up on that thread to avoid duplication. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends on #15
Following MR OSSystems#921
Please review and rebase your branch with this one, so the upstream MR gets updated for final submission.
I've kept you as the commit author, then added your signed-off-by and mine.
While here, rebased the git history for scarthgap by picking commits to be in sync with the master branch, but essentially the changes are the same.
This is the difference between both
scarthgap
andmaster
MRs (after my updates). Which matches what were submitted formerly.