Skip to content

Update CHROMIUM.md - #1944

Merged
svillar merged 2 commits into
Igalia:mainfrom
guillaume-roche:patch-1
Dec 18, 2025
Merged

svillar merged 2 commits into
Igalia:mainfrom
guillaume-roche:patch-1

Conversation

@guillaume-roche

@guillaume-roche guillaume-roche commented Nov 21, 2025 •

Copy link
Copy Markdown
Contributor

Fix build instructions:

  • It is required to run again gclient sync after switching to the wolvic branch. Otherwise, the gn gen command fails.
  • autoninja doesn't work anymore to build the project. Directly calling ninja allows to build without issues.

The second issue is probably due to an incompatibility between an up-to-date depot_tools and the wolvic branch of Chromium.

Fix build instructions:
- It is required to run again gclient sync after switching to the wolvic branch. Otherwise, the gen gen command fails.

- autoninja doesn't work anymore to build the project. Directly calling ninja allows to build without issues.

@svillar svillar left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

I just have one comment

Comment thread CHROMIUM.md

```
autoninja -C out/Default content_aar ui_aar
ninja -C out/Default content_aar ui_aar

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still use autoninja without any issue

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, thanks for you feedback. On my side, I couldn't make it work despite multiple trials. Should I suggest to fall back on ninja if autoninja doesn't work?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated this part, is that better?

@EasonZxp

Copy link
Copy Markdown
Contributor

Also encountered this issue. Using ninja allows compilation to pass, but autoninja fails to compile successfully.

Additionally, I have another question:
When using the aar compiled from the wolvic branch of the wolvic-chromium repository in the wolvic repository, a v8 deserializer crash occurs.

I also tried building with the wolvic-chromium/release/1.2.x branch of the wolvic-chromium repository and the v1.2.3-chromium version of the wolvic repository, but the v8 deserializer error still occurs during runtime.

It seems the issue might be caused by a mismatch between the compiled outputs of the two repositories?

I’d like to ask if there is any documentation specifying which commit of wolvic-chromium corresponds to the released versions of the wolvic repository?

@svillar

@svillar

svillar commented Dec 15, 2025

Copy link
Copy Markdown
Member

Also encountered this issue. Using ninja allows compilation to pass, but autoninja fails to compile successfully.

I found that using the in-tree autoninja is much more reliable than the top of the tree version from depot_tools. There is a depot_tools checkout inside the chromium repos that should work fine for any checkout you have.

Additionally, I have another question: When using the aar compiled from the wolvic branch of the wolvic-chromium repository in the wolvic repository, a v8 deserializer crash occurs.

Not sure if it's the same issue but currently we cannot use minification when creating the packages because there are crashes here and there, and also some of the code we require for example for YouTube seems to be removed from the final package.

I also tried building with the wolvic-chromium/release/1.2.x branch of the wolvic-chromium repository and the v1.2.3-chromium version of the wolvic repository, but the v8 deserializer error still occurs during runtime.

It seems the issue might be caused by a mismatch between the compiled outputs of the two repositories?

I’d like to ask if there is any documentation specifying which commit of wolvic-chromium corresponds to the released versions of the wolvic repository?

We're using a branch called wolvic

@svillar svillar left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@svillar
svillar merged commit 406f44d into Igalia:main Dec 18, 2025
@guillaume-roche
guillaume-roche deleted the patch-1 branch December 22, 2025 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants