Docker build instructions post-Chrobalt

[Dom Jackson]

Hi, 

I am wondering if there are any up-to-date instructions for building a linux executable using Docker post-Chrobalt migration?

I can see there are Dockerfiles for linux and unittests but they don't actually build an executable like the cobalt-build-linux Docker images used to do. 

Is there something I am missing or some up-to-date documentation?

[kaid...@google.com]

Hi,

Chrobalt is still in very early development - there are not yet any public docs to support it, as things still change around a lot.

However, Linux and Android builds are set up, and you can follow the steps in Github Actions to see how the builds work.

Mostly, it's based on how Chromium builds, as current Chrobalt branch is based on Chromium m114 version. 

Kaido

[Dom Jackson]

Ah okay, that makes sense. I’ll take a look at the GitHub Actions steps and see if I can get something building.

Thanks and good luck with Chrobalt!

-Dom

[Dom Jackson]

Just to let you know I managed to get this building and running for `linux-x64x11` using the instructions in the Github Action. 

Do you have plans to start publishing nightly builds or is it all still in too much flux? It took my measly machine 8 hours for Linux and 19 hours for the APK xD

-Dom 

[Kaido Kert]

Hi,

Good work in getting it built and running ! Yes, the build requirements are hefty, you'll need either robust caching or remote compilation to do meaningful work. Have a look at using the GN cc_wrapper argument, it works with ccache / sccache / distcc and other similar tools  .

We keep Android APKs on Github build artifacts on every build job - you'll find those when navigating to the job summary page ( example, scroll down to the bottom of the page ).
Linux binaries are not currently kept, as they are less portable and would probably only be suitable for running in the original distro container.

Kaido

You received this message because you are subscribed to the Google Groups "cobalt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cobalt-dev+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/cobalt-dev/2ee077f6-920d-4d2f-95f7-21537a2c522dn%40googlegroups.com.

[Dom Jackson]

Ah amazing, that makes it much easier! We'll start playing around with them. 

On a separate note (do tell me to split to another conversation if it makes sense), how up-to-date are the current supported-features docs for Chrobalt?

-Dom

[Kaido Kert]

The supported features list does not reflect Chrobalt planned featureset at all.

Given Chrobalt will be embedding Blink, the Web-facing features are expected to be much broader of course, but the supported set is still very much TBD.

Kaido

To view this discussion visit https://groups.google.com/d/msgid/cobalt-dev/7152147b-8e31-4567-bf83-683a37890766n%40googlegroups.com.

[Dom Jackson]

Ah good to know! Thanks.

I only ask because we loaded our app in it and it worked flawlessly without us having to do anything. 

When we tried a year or so ago we had to replace all our HTML elements and remove the History API etc.

We’ll keep an eye out for if anything changes support-wise.

-Dom 

To view this discussion visit https://groups.google.com/d/msgid/cobalt-dev/CAEfkO9S07GQfWWRAKxAUrMQ2avnojMF%2BEP%2Btoa4ohJGAQS_-aQ%40mail.gmail.com.