Google Git
Sign in
chromium / chromiumos / platform / croscomp / daa28835df607bb2cd7e6c30432768bf53dbb7af
commitdaa28835df607bb2cd7e6c30432768bf53dbb7af[log] [tgz]
authorLucas Berthou <berlu@google.com>Wed Apr 06 21:48:56 2022
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 14 14:42:21 2022
treee66ab7ee88c43d03a84b3ed7baf84c998ee3062b
parent6a43cc821c34b9ffde89479b4c55f3b56cd14087 [diff]
GBM: fixing hack that allows to run current configuration of croscomp on
top of "gbm" backend which is half surface less.

BUG: 228365773
Change-Id: I24e855a453f064b261dccbef1e0618d6e1a60563
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/croscomp/+/3575333
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Commit-Queue: Lucas Berthou <berlu@chromium.org>
Tested-by: Lucas Berthou <berlu@chromium.org>
1 file changed
tree: e66ab7ee88c43d03a84b3ed7baf84c998ee3062b
  1. bindgen/
  2. protocol/
  3. scripts/
  4. src/
  5. third_party/
  6. wayland-server/
  7. weston/
  8. .gitignore
  9. build.rs
  10. Cargo.toml
  11. croscomp-9999.ebuild
  12. croscomp-terminal
  13. croscomp.conf
  14. do-build.sh
  15. LICENSE
  16. OWNERS
  17. README.md
  18. rustfmt.toml
README.md

croscomp

Compositor for ChromeOS

Building

Build using portage

$ mkdir ~/trunk/src/third_party/chromiumos-overlay/chromeos-base/croscomp

$ ln -s  ../../../../platform/croscomp/croscomp-9999.ebuild \
	~/trunk/src/third_party/chromiumos-overlay/chromeos-base/croscomp

$ emerge-$BOARD croscomp

Building in the CrOS SDK

$ export BOARD=strongbad

$ setup_board --board=$BOARD

C deps:

$ emerge-$BOARD libxkbcommon wayland pixman libdrm mtdev wayland-protocols cairo mesa-freedreno minigbm lcms pango opengles-headers

Rust deps:

$ emerge-$BOARD bitflags bindgen libloading nix smallvec xml-rs downcast-rs parking_lot_core lock_api owning_ref parking_lot scoped-tls pkg-config

$ ./do-build.sh

$ cros deploy $DUT mtdev

Troubleshooting

You may need to specify which mtdev to deploy

$ cros deploy $DUT sys-libs/mtdev

If croscomp doesn't run smoothly you can get more logs with: $ export WAYLAND_DEBUG=1 RUST_BACKTRACE=1 RUST_LOG=debug

Croscomp may be missing libinput that may require libevdev

$ cros deploy $DUT dev-libs/libevdev
$ cros deploy $DUT libinput

Running chrome under croscomp

Using the CLs from

https://chromium-review.googlesource.com/c/chromium/src/+/3272706,

build and deploy chrome to the device. You need

target_os = ["chromeos"]
ozone_platform_wayland = "true"
ozone_platform = "wayland"
use_wayland_egl = "false"
use_wayland_gbm = "true"

in the gn args and then

$ ninja -C out_$BOARD/Relase chrome

followed by

$ deploy_chrome --build-dir=out_$BOARD/Release --device=$DUT --nostartui

Make sure both ui and frecon are not running, then start croscomp remotely on the device and use scripts/start-chrome.sh to start the chrome login screen on croscomp.