| commit | 2827e3b3be531384011714b21e617fe8bc5907c4 | [log] [tgz] |
|---|---|---|
| author | Lucas Berthou <berlu@google.com> | Wed Jun 29 20:58:58 2022 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 30 13:14:52 2022 |
| tree | 223bf9f5c2d886bb5c05fd08a4b9bbdb38686cd3 | |
| parent | 7079d64634b3eedf14b0f2d3b5a7207f13c9c1e4 [diff] |
ebuild: making sure Cargo dep is explicit and libpng dep fix tokio-macros seems to be a concern when trying to add Croscomp to test image. Making the dependency explicit in Cargo.toml fixes this issue. libpng is also used in weston/shared therefore it is needed as a dependency even when not running with wayland backend (moving it in build.rs) Change-Id: Ie23b8cddc1de92743b003617680a5858e5ff2a8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/croscomp/+/3736722 Tested-by: Lucas Berthou <berlu@chromium.org> Commit-Queue: John Plate <jplate@google.com> Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org> Auto-Submit: Lucas Berthou <berlu@chromium.org> Reviewed-by: John Plate <jplate@google.com>
Compositor for ChromeOS
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
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
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.