CEF branch 4472 build for mac arm64 fails

Having problems with building or using CEF's C/C++ APIs? This forum is here to help. Please do not post bug reports or feature requests here.

Re: CEF branch 4472 build for mac arm64 fails

Postby charlieq » Thu Jul 29, 2021 6:31 pm

magreenblatt wrote:Did you read the link? It mentions a script for creating a universal package.


Are you referring to
Universal Builds
A “universal” (or “fat”) .app can be created from distinct x86_64 and arm64 builds produced from the same source version. Chromium has a universalizer.py tool that can then be used to merge the two builds into a single universal .app.

% ninja -C out/release_x86_64 chrome
% ninja -C out/release_arm64 chrome
% mkdir out/release_universal
% chrome/installer/mac/universalizer.py \
out/release_x86_64/Chromium.app \
out/release_arm64/Chromium.app \
out/release_universal/Chromium.app
The universal build is produced in this way rather than having a single all-encompassing gn configuration because:

Chromium builds tend to take a long time, even maximizing the parallelism capabilities of a single machine. This split allows an additional dimension of parallelism by delegating the x86_64 and arm64 build tasks to different machines.
During the mac-arm64 bring-up, the x86_64 and arm64 versions were built using different SDK and toolchain versions. When using the hermetic SDK and toolchain, a single version of this package must be shared by an entire source tree, because it’s managed by gclient, not gn. However, as of November 2020, Chromium builds for the two architectures converged and are expected to remain on the same version indefinitely, so this is now more of a historical artifact.
@ https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/docs/mac_arm64.md#universal-builds
charlieq
Techie
 
Posts: 40
Joined: Mon Mar 20, 2017 9:50 pm

Re: CEF branch 4472 build for mac arm64 fails

Postby magreenblatt » Thu Jul 29, 2021 6:46 pm

Yes
magreenblatt
Site Admin
 
Posts: 11083
Joined: Fri May 29, 2009 6:57 pm

Re: CEF branch 4472 build for mac arm64 fails

Postby charlieq » Thu Jul 29, 2021 7:14 pm

magreenblatt wrote:Yes


But the script is to create a universal app. I would like universal CEF package to be created that could be used by my app.
charlieq
Techie
 
Posts: 40
Joined: Mon Mar 20, 2017 9:50 pm

Re: CEF branch 4472 build for mac arm64 fails

Postby magreenblatt » Thu Jul 29, 2021 10:03 pm

What do you mean by “ universal CEF package”?
magreenblatt
Site Admin
 
Posts: 11083
Joined: Fri May 29, 2009 6:57 pm

Re: CEF branch 4472 build for mac arm64 fails

Postby charlieq » Thu Jul 29, 2021 10:43 pm

magreenblatt wrote:What do you mean by “ universal CEF package”?


A CEF package can work on both x64 (intel) & arm64 machine.
charlieq
Techie
 
Posts: 40
Joined: Mon Mar 20, 2017 9:50 pm

Re: CEF branch 4472 build for mac arm64 fails

Postby charlieq » Fri Jul 30, 2021 8:09 am

magreenblatt wrote:Yes

Got error:
universalizer.PNG
universalizer.PNG (242.72 KiB) Viewed 183 times
charlieq
Techie
 
Posts: 40
Joined: Mon Mar 20, 2017 9:50 pm

Re: CEF branch 4472 build for mac arm64 fails

Postby magreenblatt » Fri Jul 30, 2021 1:29 pm

charlieq wrote:
magreenblatt wrote:What do you mean by “ universal CEF package”?


A CEF package can work on both x64 (intel) & arm64 machine.

That is the intended purpose of the universalizer.py script discussed above.
magreenblatt
Site Admin
 
Posts: 11083
Joined: Fri May 29, 2009 6:57 pm

Previous

Return to Support Forum

Who is online

Users browsing this forum: Google [Bot] and 10 guests