fdo-mirrors/cairo
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/cairo/cairo.git synced 2026-05-23 10:48:12 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
cairo/build/Makefile.win32.features

42 lines
1 KiB
Text
Raw Normal View History

[build] Include all generated win32 build files in the repo So a git clone can be built on win32. The files only change after adding new backends.
2009-01-09 15:55:24 -05:00
# Generated by configure. Modify to customize.
CAIRO_HAS_XLIB_SURFACE=0
CAIRO_HAS_XLIB_XRENDER_SURFACE=0
CAIRO_HAS_XCB_SURFACE=0
xcb: Refresh. Still an experimental backend, it's now a little too late to stabilise for 1.10, but this should represent a major step forward in its feature set and an attempt to catch up with all the bug fixes that have been performed on xlib. Notably not tested yet (and expected to be broken) are mixed-endian connections and low bitdepth servers (the dithering support has not been copied over for instance). However, it seems robust enough for daily use... Of particular note in this update is that the xcb surface is now capable of subverting the xlib surface through the ./configure --enable-xlib-xcb option. This replaces the xlib surface with a proxy that forwards all operations to an equivalent xcb surface whilst preserving the cairo-xlib API that is required for compatibility with the existing applications, for instance GTK+ and Mozilla. Also you can experiment with enabling a DRM bypass, though you need to be extremely foolhardy to do so.
2010-01-22 21:26:26 +00:00
CAIRO_HAS_XLIB_XCB_FUNCTIONS=0
xcb: Make shm optional Trying to build xcb on a system without SHM wrapped by xcb. The right answer would be to build libxcb-shm. The quick answer is to compile out shm support.
2010-01-25 16:45:03 +00:00
CAIRO_HAS_XCB_SHM_FUNCTIONS=0
Import Qt backend by Mozilla Written by Vladimir Vukicevic to enable integration with Qt embedded devices, this backend allows cairo code to target QPainter, and use it as a source for other cairo backends. This imports the sources from mozilla-central: http://mxr.mozilla.org/mozilla-central/find?text=&kind=text&string=cairo-qpainter renames them from cairo-qpainter to cairo-qt, and integrates the patch by Oleg Romashin: https://bugs.freedesktop.org/attachment.cgi?id=18953 And then attempts to restore 'make check' to full functionality. However: - C++ does not play well with the PLT symbol hiding, and leaks into the global namespace. 'make check' fails at check-plt.sh - Qt embeds a GUI into QApplication which it requires to construct any QPainter drawable, i.e. used by the boilerplate to create a cairo-qt surface, and this leaks fonts (cairo-ft-fonts no less) causing assertion failures that all cairo objects are accounted for upon destruction. [Updated by Chris Wilson] Acked-by: Jeff Muizelaar <jeff@infidigm.net> Acked-by: Carl Worth <cworth@cworth.org>
2009-06-14 20:43:05 +01:00
CAIRO_HAS_QT_SURFACE=0
[build] Include all generated win32 build files in the repo So a git clone can be built on win32. The files only change after adding new backends.
2009-01-09 15:55:24 -05:00
CAIRO_HAS_QUARTZ_SURFACE=0
CAIRO_HAS_QUARTZ_FONT=0
CAIRO_HAS_QUARTZ_IMAGE_SURFACE=0
CAIRO_HAS_WIN32_SURFACE=1
CAIRO_HAS_WIN32_FONT=1
Add skia backend Originally written by Vladimir Vukicevic to investigate using Skia for Mozilla, it provides a nice integration with a rather interesting code base. By hooking Skia underneath Cairo it allows us to directly compare code paths... which is interesting. [updated by Chris Wilson]
2009-06-15 11:15:22 +01:00
CAIRO_HAS_SKIA_SURFACE=0
[build] Include all generated win32 build files in the repo So a git clone can be built on win32. The files only change after adding new backends.
2009-01-09 15:55:24 -05:00
CAIRO_HAS_OS2_SURFACE=0
CAIRO_HAS_BEOS_SURFACE=0
[drm] Add an accelerated image surface. Use the DRM interface to h/w accelerate composition on image surfaces. The purpose of the backend is simply to explore what such a hardware interface might look like and what benefits we might expect. The use case that might justify writing such custom backends are embedded devices running a drm compositor like wayland - which would, for example, allow one to write applications that seamlessly integrated accelerated, dynamic, high quality 2D graphics using Cairo with advanced interaction (e.g. smooth animations in the UI) driven by a clutter framework... In this first step we introduce the fundamental wrapping of GEM for intel and radeon chipsets, and, for comparison, gallium. No acceleration, all we do is use buffer objects (that is use the kernel memory manager) to allocate images and simply use the fallback mechanism. This provides a suitable base to start writing chip specific drivers.
2009-06-11 15:18:55 +01:00
CAIRO_HAS_DRM_SURFACE=0
CAIRO_HAS_GALLIUM_SURFACE=0
[build] Include all generated win32 build files in the repo So a git clone can be built on win32. The files only change after adding new backends.
2009-01-09 15:55:24 -05:00
CAIRO_HAS_PNG_FUNCTIONS=1
[gl] Add basics for GL surface backend using test-fallback as base.
2009-01-29 09:19:01 -08:00
CAIRO_HAS_GL_SURFACE=0
gl: Add GLESv2 backend to build system Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2011-03-03 23:17:31 +02:00
CAIRO_HAS_GLESV2_SURFACE=0
backends: Adds a new Cogl based backend This adds a new GPU accelerated backend for Cairo based on the Cogl 3D graphics API. This backend aims to support Cairo in a way that translates as naturally as possible to using a GPU, it does not strive to compete with the anti-aliasing quality of the image backend if it can't be done efficiently using the GPU - raw performance isn't the only metric of concern, so is power usage. As an overview of how the backend works: - fills are handled by tessellating paths into triangles - the backend has an extra fill_rectangle drawing operation so we have a fast-path for drawing rectangles which are so common. - strokes are also tessellated into triangles. - stroke and fill tessellations are cached to avoid the cpu overhead of tessellation and cost of upload given that its common for apps to re-draw the same path multiple times. The tessellations can survive translations and rotations increasing the probability that they can be re-used. - sources and masks are handled using multi-texturing. - clipping is handled with a scissor and the stencil buffer which we're careful to only update when they really change. - linear gradients are rendered to a 1d texture using a triangle strip + interpolating color attributes. All cairo extend modes are handled by corresponding texture sampler wrap modes without needing programmable fragment processing. - antialiasing should be handled using Cogl's multisampling API XXX: This is a work in progress!! TODO: - handle at least basic radial gradients (No need to handle full pdf semantics, since css, svg and canvas only allow radial gradients defined as one circle + a point that must lie within the first circle.) - currently we fall back to pixman for radial gradients. - support glyph rendering with a decent glyph cache design. The current plan is a per scaled-font growable cache texture + a scratch cache for one-shot/short-lived glyphs. - decide how to handle npot textures when lacking hardware support. Current plan is to add a transparent border to npot textures and use CLAMP_TO_EDGE for the default EXTEND_NONE semantics. For anything else we can allocate a shadow npot texture and scale the original to fit that so we can map extend modes to texture sampler modes.
2011-07-21 12:15:05 +01:00
CAIRO_HAS_COGL_SURFACE=0
[build] Include all generated win32 build files in the repo So a git clone can be built on win32. The files only change after adding new backends.
2009-01-09 15:55:24 -05:00
CAIRO_HAS_DIRECTFB_SURFACE=0
Add OpenVG backend. Based on the work by Øyvind Kolås and Pierre Tardy -- many thanks to Pierre for pushing this backend for inclusion as well as testing and reviewing my initial patch. And many more thanks to pippin for writing the backend in the first place! Hacked and chopped by myself into a suitable basis for a backend. Quite a few issues remain open, but would seem to be ready for testing on suitable hardware.
2009-07-15 16:37:25 +01:00
CAIRO_HAS_VG_SURFACE=0
CAIRO_HAS_EGL_FUNCTIONS=0
CAIRO_HAS_GLX_FUNCTIONS=0
build: Add wgl to Makefile.sources and regenerate features.
2010-06-14 16:05:14 +01:00
CAIRO_HAS_WGL_FUNCTIONS=0
script: enable by default I'm willing to make this a supported backend as I find it to be an invaluable debugging tool... Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2011-08-14 20:56:15 +01:00
CAIRO_HAS_SCRIPT_SURFACE=1
[build] Include all generated win32 build files in the repo So a git clone can be built on win32. The files only change after adding new backends.
2009-01-09 15:55:24 -05:00
CAIRO_HAS_FT_FONT=0
Support compiling without fontconfig Adds a new, fake, fontconfig font backend. Fontconfig can be disabled using --disable-fc, in which case the toy text API wont find fonts and the internal font will always be used. Also defines the feature macro CAIRO_HAS_FC_FONT. The two fontconfig-specific functions in cairo-ft.h depend on that macro now.
2009-03-17 00:53:30 -04:00
CAIRO_HAS_FC_FONT=0
[build] Include all generated win32 build files in the repo So a git clone can be built on win32. The files only change after adding new backends.
2009-01-09 15:55:24 -05:00
CAIRO_HAS_PS_SURFACE=1
CAIRO_HAS_PDF_SURFACE=1
CAIRO_HAS_SVG_SURFACE=1
CAIRO_HAS_TEST_SURFACES=0
configure: Disable tee backend by default We don't want to enable it by default when nobody uses it.
2010-07-30 21:48:14 +02:00
CAIRO_HAS_TEE_SURFACE=0
configure: Disable xml backend by default We don't want to enable it by default when nobody uses it.
2010-07-30 22:04:44 +02:00
CAIRO_HAS_XML_SURFACE=0
build: Sync up autogenerated win32 build files.
2010-07-12 10:36:00 +03:00
CAIRO_HAS_PTHREAD=0
Fix configuration if gobject is absent Autodetect gobject and only use it if present. Its absence is not to be considered a failure since it's not required.
2010-08-07 21:32:09 +02:00
CAIRO_HAS_GOBJECT_FUNCTIONS=0
[win32] Sync Makefile.win32.features. Ooops.. wasn't sure if I should commit this or not.
2009-09-13 20:24:29 +03:00
CAIRO_HAS_TRACE=0
[build] Improve handling of missing test apparatus Improve detection, reporting and disabling of test backends when we lack the required libraries and utilities.
2009-09-08 17:51:33 +01:00
CAIRO_HAS_INTERPRETER=1
[win32] Sync Makefile.win32.features. Ooops.. wasn't sure if I should commit this or not.
2009-09-13 20:24:29 +03:00
CAIRO_HAS_SYMBOL_LOOKUP=0
Reference in a new issue Copy permalink