fdo-mirrors/cairo
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/cairo/cairo.git synced 2026-05-01 11:28:09 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
cairo/boilerplate
History
Vladimir Vukicevic 3623da441a [nquartz] Initial commit of native quartz surface 
Inital commit of Native Quartz surface.  The main missing functionality
is mask() support (which is just a noop right now, except for the simple
solid-alpha case).
2006-09-13 14:48:40 -07:00
..
.gitignore Add 2006-09-06 13:58:31 -04:00
cairo-boilerplate.c [nquartz] Initial commit of native quartz surface 2006-09-13 14:48:40 -07:00
cairo-boilerplate.h perf: Make xlib testing wait for the X server to finish rendering. 2006-09-11 10:59:38 -07:00
cairo-test-beos.cpp Split libcairotest files out from test/ and into boilerplate/ 2006-08-30 15:34:27 -07:00
cairo-test-beos.h Split libcairotest files out from test/ and into boilerplate/ 2006-08-30 15:34:27 -07:00
cairo-test-directfb.c Split libcairotest files out from test/ and into boilerplate/ 2006-08-30 15:34:27 -07:00
cairo-test-directfb.h Split libcairotest files out from test/ and into boilerplate/ 2006-08-30 15:34:27 -07:00
Makefile.am [Makefile] Fix typo 2006-09-06 12:45:07 -04:00
Makefile.win32 [win32] Makefile.win32: use correct (/MD) runtime library flag everywhere 2006-09-09 23:29:17 -07:00
README Add boilerplate/README explaining its purpose 2006-08-30 22:33:53 -07:00
xmalloc.c Move test-specific stuff out of boilerplate/ and back into test/ 2006-08-31 01:39:06 -07:00
xmalloc.h Split libcairotest files out from test/ and into boilerplate/ 2006-08-30 15:34:27 -07:00

README 

This directory provides code that is common to both of cairo's tests
suites:

 * The test suite for correctness in test/
 * The test suite for performance in perf/

We call it boilerplate as it consists primarily of the boilerplate
code necessary for initializing a backend in order to create a surface
for that backend.

The code here just might be useful for someone looking to get started
writing cairo code to use a particular backend, (but there are no
promises that the boilerplate code found here for any particular
backend is exemplary).