32a5acde5b
There are some specific cases in which we need Weston to behave differently when running in the test suite. This adds a new API to allow the tests to select these behaviors. For instance, in the DRM backend we plan to add a writeback connector screenshooter. In case it fails for some reason, it should fallback to the renderer screenshooter that all other backends use. But if we add a test to ensure the correctness of the writeback screenshooter, we don't want it to fallback to the renderer one, we want it to fail. With this new API we can choose to disable the fallback behavior specifically for this test. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com> |
||
|---|---|---|
| .. | ||
| cms-colord.c | ||
| cms-helper.c | ||
| cms-helper.h | ||
| cms-static.c | ||
| executable.c | ||
| main.c | ||
| meson.build | ||
| screen-share.c | ||
| systemd-notify.c | ||
| text-backend.c | ||
| weston-screenshooter.c | ||
| weston.desktop | ||
| weston.h | ||
| xwayland.c | ||