libweston: drop opaque struct wet_testsuite_data

Until now we had struct wet_testsuite_data as an opaque
struct that should be defined by the testsuite of libweston
users. Instead, keep the data as a void * and document that
users are responsible for defining the data type.

Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
This commit is contained in:
Leandro Ribeiro 2020-10-19 16:24:44 -03:00 committed by Pekka Paalanen
parent 32a5acde5b
commit 2d4dd70ff5
3 changed files with 3 additions and 9 deletions

View File

@ -98,12 +98,6 @@ text_backend_destroy(struct text_backend *text_backend);
int
wet_main(int argc, char *argv[], const struct weston_testsuite_data *test_data);
/* test suite utilities */
/** Opaque type for a test suite to define. */
struct wet_testsuite_data;
#ifdef __cplusplus
}
#endif

View File

@ -203,7 +203,7 @@ struct weston_testsuite_quirks {
*/
struct weston_testsuite_data {
struct weston_testsuite_quirks test_quirks;
struct wet_testsuite_data *test_private_data;
void *test_private_data;
};
/** Represents a head, usually a display connector

View File

@ -7334,9 +7334,9 @@ debug_scene_graph_cb(struct weston_log_subscription *sub, void *data)
* 1. The struct weston_testsuite_quirks, which can be used by the tests to
* change certain behavior of Weston when running these tests.
*
* 2. The struct wet_testsuite_data member, which can be used by the test suite
* 2. The void *test_private_data member which can be used by the test suite
* of projects that uses libweston in order to give arbitrary test data to the
* compositor.
* compositor. Its type should be defined by the test suite of the project.
*
* This function can be called at most once per compositor instance, just after
* creating the weston_compositor object and never again. This happens because