Google Git
Sign in
chromium / chromiumos / platform / croscomp / refs/heads/stabilize-14989.85.B
commit8dd692d38fb918d76c6ad213bd8ffbfbb6a0d361[log] [tgz]
authorLucas Berthou <berlu@google.com>Tue Jul 12 21:14:42 2022
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 13 15:00:44 2022
treebd4b28b836ebf01cee45ce419b99be265584cd99
parent2827e3b3be531384011714b21e617fe8bc5907c4 [diff]
Modify tokio feature requirement to support bytes empty crate.

Full tokio requires bytes-1.* which is currently only imported has as an empty crate. Alternatively we could import byte-1.1.0 as a non empty crate but that seems to be more dependency than doing this.

Change-Id: I5406c08248655b2a611ccb83015af2f526ff15eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/croscomp/+/3759304
Tested-by: Lucas Berthou <berlu@chromium.org>
Reviewed-by: Andres Calderon Jaramillo <andrescj@google.com>
Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org>
Commit-Queue: Lucas Berthou <berlu@chromium.org>
Auto-Submit: Lucas Berthou <berlu@chromium.org>
1 file changed
tree: bd4b28b836ebf01cee45ce419b99be265584cd99
  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-terminal
  12. croscomp.conf
  13. do-build.sh
  14. LICENSE
  15. OWNERS
  16. README.md
  17. 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.