Expose _cairo_null_surface_create() via a test surface

Using a null surface is a convenient method to measure the overhead of the
performance testing framework, so export it although as a test-surface so
that it will only be available in development builds and not pollute
distributed libraries.

1 files changed, 16 insertions, 0 deletions

diff --git a/boilerplate/cairo-boilerplate-test-surfaces.c b/boilerplate/cairo-boilerplate-test-surfaces.c
index 644b2787b..0fc92e3f8 100644
--- a/boilerplate/cairo-boilerplate-test-surfaces.c
+++ b/boilerplate/cairo-boilerplate-test-surfaces.c
@@ -30,6 +30,7 @@
 #include <test-fallback-surface.h>
 #include <test-fallback16-surface.h>
 #include <test-meta-surface.h>
+#include <test-null-surface.h>
 #include <test-paginated-surface.h>
 
 #include <assert.h>
@@ -79,6 +80,21 @@ _cairo_boilerplate_test_meta_create_surface (const char			 *name,
     return _cairo_test_meta_surface_create (content, width, height);
 }
 
+cairo_surface_t *
+_cairo_boilerplate_test_null_create_surface (const char			 *name,
+					     cairo_content_t		  content,
+					     int			  width,
+					     int			  height,
+					     int			  max_width,
+					     int			  max_height,
+					     cairo_boilerplate_mode_t	  mode,
+					     int                          id,
+					     void			**closure)
+{
+    *closure = NULL;
+    return _cairo_test_null_surface_create (content);
+}
+
 static const cairo_user_data_key_t test_paginated_closure_key;
 
 typedef struct {