Missing instructions on how to do a full build of the browser

[simonschmeisser]

The docs mention a partial build of the browser/xulrunner but I couldn't figure out how to get started with a full one:

sailfishos/sailfish-browser#1013

I tried both sfdk and mb2 and would appreciate some hints

[llewelld]

Just for reference, here are the docs in question:

https://docs.sailfishos.org/Reference/Core_Areas_and_APIs/Browser/Working_with_Browser/

There are unfortunately lots of 'gotchas' when it comes to building gecko-dev. There are workarounds needed for different architectures (x86, arm, aarch64) and depending on whether you're building on OBS or locally using sfossdk or sfdk. I agree it'd be good to capture all of these in the docs.

For example, we should document the git_workaround flag that's needed for local builds (not needed on OBS). And the fact that a patch for scratchbox2 is needed for local x86 builds (not needed on OBS, not needed for arm or aarch64).

The process in a nutshell. Get the source:

git clone git@github.com:sailfishos/gecko-dev.git
cd gecko-dev
git submodule update --init

Clean builds should use the prepare step to apply patches:

sfdk build -d -p --with git_workaround

Subsequent incremental builds should skip the prepare step:

sfdk build -d --with git_workaround

You'll also need sufficient resources: in my experience 16GiB RAM is probably not enough but 32GiB should be.

[simonschmeisser]

Thanks a lot, I'll test these and open a PR then!