summaryrefslogtreecommitdiff
path: root/boilerplate/cairo-boilerplate-script.c
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2009-08-23 15:25:42 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2009-08-29 17:07:38 +0100
commit8078cd194e95a10cf653c970d1ddd39049a511f2 (patch)
tree4ee7f0d49ef3eb37fbae0ae2d9ad0a5e613cdfc1 /boilerplate/cairo-boilerplate-script.c
parent7447915381fc64bd0c66f7110c1dd0b8a10d73f5 (diff)
downloadcairo-8078cd194e95a10cf653c970d1ddd39049a511f2.tar.gz
[boilerplate] Runtime library check
For the purposes of benchmarking it is useful to run cairo-perf against a different library from the one it was compiled against. In order to do so, we need to check that the runtime library contains the required entry points for our targets - which we can check by using dlsym.
Diffstat (limited to 'boilerplate/cairo-boilerplate-script.c')
-rw-r--r--boilerplate/cairo-boilerplate-script.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/boilerplate/cairo-boilerplate-script.c b/boilerplate/cairo-boilerplate-script.c
index d1d76b5c8..e37fdf13e 100644
--- a/boilerplate/cairo-boilerplate-script.c
+++ b/boilerplate/cairo-boilerplate-script.c
@@ -129,6 +129,7 @@ _cairo_boilerplate_script_cleanup (void *closure)
static const cairo_boilerplate_target_t target[] = {{
"script", "script", ".cs", NULL,
CAIRO_SURFACE_TYPE_SCRIPT, CAIRO_CONTENT_COLOR_ALPHA, 0,
+ "cairo_script_surface_create",
_cairo_boilerplate_script_create_surface,
NULL,
_cairo_boilerplate_script_finish_surface,