crosvm/gpu_display
Noah Gold eec8ecef18 gpu_display: fix Cargo feature selection.
The features we request in gpu_display weren't complete with respect to
the code we were using from dependent crates. This has been fine because
we usually build crosvm as a monolith, but when testing we need the
individual crates to be complete.

Bug: 295082178
Test: nextest -p gpu_display --features=kiwi -E \
'test(can_create_2_window_proc_threads)'

Change-Id: Ib1f6a23149f08124eab3cad56cf9350a570d1c9a
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4805406
Commit-Queue: Colin Downs-Razouk <colindr@google.com>
Reviewed-by: Vikram Auradkar <auradkar@google.com>
2023-10-24 23:18:38 +00:00
..
examples Replace #[cfg(unix)] with #[cfg(any(target_os = "android", target_os = "linux"))] 2023-10-11 00:43:29 +00:00
protocol health-check: Add check for newline at ends of files 2022-08-18 00:17:04 +00:00
src gpu_display: gpu_display_win: use builder to create the wndproc thread 2023-10-24 23:18:38 +00:00
build.rs gpu_display: find wayland-scanner with which in build.rs 2023-02-27 21:18:21 +00:00
Cargo.toml gpu_display: fix Cargo feature selection. 2023-10-24 23:18:38 +00:00