| commit | c55f2d5c858b5f3bc352f54a3f2c495e4b92f1ea | [log] [tgz] |
|---|---|---|
| author | Kristian H. Kristensen <hoegsberg@google.com> | Thu Nov 11 18:44:57 2021 +0100 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 13 17:40:24 2022 +0000 |
| tree | b3a093c35cb30d31f186a9baee4eb4384c87fcf7 | |
| parent | 18c7e1e910be79cec2ee2b5fef52db0d6842aa46 [diff] |
Alias ffi::shell_surface to shell::Surface and move rust impl Change-Id: Ic6e613210002f05ec9eb29cbd5b96803f99a83f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/croscomp/+/3277709 Tested-by: Kristian Kristensen <hoegsberg@chromium.org> Reviewed-by: Lucas Berthou <berlu@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.