| commit | 5846298ea42665c2c0b520d468d79d8fedd4a16f | [log] [tgz] |
|---|---|---|
| author | Lucas Berthou <berlu@google.com> | Tue Aug 02 18:08:26 2022 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 03 18:05:57 2022 |
| tree | b11b9ea5c361845ea90f9b8f99f303208464ba69 | |
| parent | ca08f49644ede3adbd3f9d51e0a5bd6568ad4749 [diff] |
Typo correction in readme Also adding missing blank lines for formating. Change-Id: I2f35b4b001e571b04b6e4fa66cb29126ab66b6e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/croscomp/+/3806260 Reviewed-by: Lucas Berthou <berlu@chromium.org> Reviewed-by: John Plate <jplate@google.com> Auto-Submit: Lucas Berthou <berlu@chromium.org> Commit-Queue: John Plate <jplate@google.com> Reviewed-by: Ben Widawsky <bwidawsk@google.com> Tested-by: Lucas Berthou <berlu@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
When running the ./do-build.sh script if you get the following error
$ ninja: error: loading 'build.ninja': No such file or directory`
It means meson generation failed to generate the build.ninja file, the easiest work around is to delete weston out folder and retry the script
$ rm /mnt/host/source/src/platform/croscomp/target/x86_64-cros-linux-gnu/debug/weston $ ./do-build.sh
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.