| commit | 7e9ba19d28790969c79803bcc4d9435312ec2c56 | [log] [tgz] |
|---|---|---|
| author | Kristian H. Kristensen <hoegsberg@google.com> | Fri Jan 28 00:14:44 2022 +0100 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Feb 10 15:59:36 2022 +0000 |
| tree | 9b2d8c8997905c32055be0dcbbb1ad7dd4c137c0 | |
| parent | 5b7eab6c3bd5ec954e96d4959f503da4c7ec9e29 [diff] |
Allow some dead code to silence warnings Change-Id: Iccb2a3d40f1eed82cdf230cf1d47d093f148dfeb Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/croscomp/+/3447464 Reviewed-by: Lucas Berthou <berlu@chromium.org> Tested-by: Kristian Kristensen <hoegsberg@chromium.org> Commit-Queue: Kristian Kristensen <hoegsberg@chromium.org>
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.