@@ -72,21 +72,20 @@ host. clang-native from the meta-clang layer is used to build those binaries.
7272Additionally, make sure the machine being used to build Chromium is powerful
7373enough: a x86-64 machine with at least 16GB RAM is recommended.
7474
75- ### dunfell -specific requirements
75+ ### kirkstone -specific requirements
7676
77- The dunfell OE/Yocto branch is an LTS release, which is often at odds with
77+ The kirkstone OE/Yocto branch is an LTS release, which is often at odds with
7878Chromium's release model because it often requires recent versions of certain
7979recipes to build correctly.
8080
81- This is particularly a problem for the toolchain (i.e. LLVM) and, at times,
82- node.js. As such, dunfell users ** must** ensure the following:
83- * Chromium needs clang >= 12 and for that, meta-clang's ** dunfell-clang12**
84- branch needs to be used.
85- * Since Chromium 112, at least Nodejs 14 is required for parts of the build.
86- meta-oe needs to be at least a commit
87- 116bfe8d5e5851e7fc5424f40da8691a19c5b5ee ("nodejs: make 14.18.1 available but
88- not default") and ` PREFERRED_VERSION_nodejs-native = "14.%" ` needs to be
89- added to ` conf/local.conf ` .
81+ This is particularly a problem for the toolchain (i.e. LLVM/clang and Rust).
82+ Because meta-clang's kirkstone branch currently only provides clang 14, we are
83+ unable to support Chromium versions higher than 120 due to those versions
84+ requiring a more recent clang version. Also, kirkstone users ** must** ensure the
85+ following:
86+ * Chromium needs a somewhat recent version of Rust, and for that
87+ meta-lts-mixins' ** kirkstone/rust-1.68** or ** kirkstone/rust-1.70** branch
88+ needs to be used.
9089
9190## PACKAGECONFIG knobs
9291
0 commit comments