[test] Build test suite into single binary.

Avoid calling libtool to link every single test case, by building just one
binary from all the sources.

This binary is then given the task of choosing tests to run (based on user
selection and individual test requirement), forking each test into its own
process and accumulating the results.

1 files changed, 6 insertions, 14 deletions

diff --git a/test/leaky-polygon.c b/test/leaky-polygon.c
index fbe747549..0ea7094c9 100644
--- a/test/leaky-polygon.c
+++ b/test/leaky-polygon.c
@@ -56,15 +56,6 @@
 #define WIDTH 21
 #define HEIGHT 21
 
-static cairo_test_draw_function_t draw;
-
-static const cairo_test_t test = {
-    "leaky-polygon",
-    "Exercises a corner case in the trapezoid rasterization in which pixels outside the trapezoids received a non-zero alpha",
-    WIDTH, HEIGHT,
-    draw
-};
-
 static cairo_test_status_t
 draw (cairo_t *cr, int width, int height)
 {
@@ -86,8 +77,9 @@ draw (cairo_t *cr, int width, int height)
     return CAIRO_TEST_SUCCESS;
 }
 
-int
-main (void)
-{
-    return cairo_test (&test);
-}
+CAIRO_TEST (leaky_polygon,
+	    "Exercises a corner case in the trapezoid rasterization in which pixels outside the trapezoids received a non-zero alpha",
+	    "fill, trap", /* keywords */
+	    NULL, /* requirements */
+	    WIDTH, HEIGHT,
+	    NULL, draw)