meta-browser/meta-chromium/README.md

9 * URI: git://git.openembedded.org/openembedded-core
10   - branch: master
11   - revision: HEAD
13 * URI: git://git.openembedded.org/meta-openembedded
14   - layers: meta-oe
15   - branch: master
16   - revision: HEAD
18 * URI: git://github.com/kraj/meta-clang
19   - branch: master
20   - revision: HEAD
23 ------------
29 list openembedded-devel@lists.openembedded.org (you have to be subscribed to
33 -----------
42 git send-email -1 -s --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-browser]…
46 -------
47 recipes-browser/chromium:
56 open-source Chromium browser.
60 - We manually patch parts of the build system to replace Chromium's bundled
61   copies of some packages (flac, libjpeg and others) with system-wide ones.
62 - Parts of the V8 (Chromium's JavaScript engine) build need to run binaries
66 ------------------
72 host. clang-native from the meta-clang layer is used to build those binaries.
74 For building most of the code for your target, a C++14-compliant compiler is
78 enough: a x86-64 machine with at least 16GB RAM is recommended.
81 -------------------
82 * component-build: (off by default)
83   Enables component build mode. By default, all of Chromium (with the exception
85   GB RAM. Component mode was created to facilitate development and testing,
87   to a separate shared object. Use component mode for development, testing, and
88   in case the build machine is not a 64-bit one, or has less than 8 GB RAM.
93 * custom-libcxx (off by default)
95   meta-clang provided libc++, this could be useful in some cases, where the
100   Enables GTK4 runtime support in Chromium by adding --gtk-version=4
103 * kiosk-mode: (off by default)
104   Enable this option if you want your browser to start up full-screen, without
105   any menu bars, without any clutter, and without any initial start-up
108 * proprietary-codecs: (off by default)
110   codecs, most notably MPEG standards (h.264, h.265, MP4, MP3, AAC etc). It is
114 * use-egl: (on by default)
120 * use-vaapi: (off by default)
121   Enables VA-API support with that allows hardware accelerated media playback on
122   GPUs that support VA-API. If h.264 codec is required, proprietary-codecs must
127   Chromium expects the presence of `org.freedesktop.UPower` via D-Bus to
132 ---------------
144 For more information, see https://dev.chromium.org/developers/how-tos/api-keys.