This README file contains information on the contents of the meta-bsm layer.
Please see the corresponding sections below for details.
Note: This repo is intended to work with the Colibri iMX8X chipset using the Dunfell 5.x.y BSP files. Please see this Toradex wiki stub to get started with the correct BSP files. If a link references kirkstone-6.x.y, replace with dunfell-5.x.y.
URI: meta-clang
branch: dunfell-clang12
URI: meta-browser
branch: master
. . .
Please submit any patches against the meta-bsm layer to the xxxx mailing list (xxxx@zzzz.org) and cc: the maintainer:
Maintainer: XXX YYYYYY xxx.yyyyyy@zzzzz.com
I. Adding the meta-bsm layer to your build II. Misc
- After setting up the
oe-core/
directory with Dunfell tooling (see Toradex link above), goto theoe-core/
directory and type.export
. This will setup the shell environment forbitbake
. - Modify
oe-core/build/conf/local.conf
. Pick the correctMACHINE
and add theACCEPT_FSL_EULA = "1"
. See here for more info. - In
oe-core/layers/
clone:
- meta-clang: Make sure to then switch to the dunfell-clang12 branch
- meta-browser: Master should work
- meta-bsm: This repo, master should work
- Open up
oe-core/layers/meta-browser/meta-chromium/recipes-browser/chromium/chromium-ozone-wayland*.inc
in a text editor - At the end of the file, add
CXXFLAGS += "-D__GBM__"
(see thread to follow bug) - Edit
oe-core/build/conf/bblayers.conf
:
- Add
meta-browser/meta-chromium
- Add
meta-bsm
- Add
meta-clang
Note - Use the other examples in the file as a template to adding this.meta-bsm
might look something along like${DIR}/layers/meta-bsm \
- run
bitbake bsm
. This may take a lot of memory, consider usingPARALLEL_MAKE="-j 4" BB_NUMBER_THREADS="6" bitbake bsm
and replace 4 and 6 as needed. On a 32-core, 32GB Linux machine I used 12 and 12 and no OOM issues. - Wait
- Keep waiting
- Hopefully no errors. Since this is Toradex, transfer the
oe-core/build/deploy/images/colibri-imx8x/
tezi.tar.xz to a USB drive. - Reset the Toradex, plug in the USB, and flash the image. See here for more info.
- After flashing, the inital boot should launch to a login.
- SSH in, or login, and modify
/etc/xdg/weston/weston.ini
. Set--backend=wayland-backend.so
and comment outxwayland=true
. - Reboot
- Weston should boot
- SSH in and launch
chromium --no-sandbox
.
--- replace with specific information about the meta-bsm layer ---
- Add Rust recipes
- Add NodeJS recipes
- Harden with users
- Auto update weston.ini
- Test electron
- Test Tauri