| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Richard Hult reported that -Wl,--allow-shlib-undefined was incorrectly
being identified as supported by gcc under Mac OS/X:
configure:25103: checking whether gcc supports -Wl,--allow-shlib-undefined
configure:25117: gcc -c -Werror -Wl,--allow-shlib-undefined conftest.c
>&5
i686-apple-darwin9-gcc-4.0.1: --allow-shlib-undefined: linker input file
unused because linking not done
So instead of just checking whether the compiler accepts the flag, check
that we can actually link a dummy file.
|
|
Previously there was a bug in cairo and/or poppler causing glyph 0 of
user fonts to not show up. This is fixed now, so we exercise glyph 0.
|
|
Carl spotted that 1db894 introduced an error into text_to_glyphs() such
that following an allocation error the code would attempt to thaw an
unfrozen glyph cache, leading to an attempt to unlock an unlocked mutex -
which causes a deadlock under win32.
|
|
|
|
Quartz fonts and user fonts use an indirect font face when creating a
scaled font for the toy font face. This means that they insert a scaled
font into the font map that has a different font face to the one that is
initially searched upon. The result is that when we try to create an
identical scaled font, we fail to find the existing scaled font and
attempt to insert a duplicate into the hash table - which triggers an
assert.
In order to avoid creating duplicate fonts, we add a new method to the
font backends that allows cairo_scaled_font_create() to peek at the
font_face that will be used to actually implement the scaled font
constructor - thus we are able to use the correct font_face as part of the
hash key.
|
|
This allows user-fonts to use glyph 0 when embedding in PS/PDF.
According to ISO32000 Type 3 fonts do not require a notdef glyph.
|
|
In the previous commit I added comments and a duplicate prototype. Remove
the duplicate - but keep the comments.
|
|
After discussing the scaled font locking with Behdad, it transpired that it
is not sufficient for a font to be locked for the lifetime of a scaled glyph,
but that the scaled font's glyph cache must be frozen for the glyph'
lifetime. If the cache is not frozen, then there is a possibility that the
glyph may be evicted before the reference goes out of scope i.e. the glyph
becomes invalid whilst we are trying to use it.
Since the freezing of the cache is the stronger barrier, we remove the
locking/unlocking of the mutex from the backends and instead move the
mutex acquisition into the freeze/thaw routines. Then update the rule on
acquiring glyphs to enforce that the cache is frozen and review the usage
of freeze/thaw by all the backends to ensure that the cache is frozen for
the lifetime of the glyph.
|
|
Use cairo_get_target() to propagate any errors from the secondary context.
|
|
Dolt is a hack to speed up libtool-based build systems:
http://dolt.freedesktop.org/
It's completely transparent to the user. Brings make time
of cairo from 70s down to 20s. Yay!
|
|
Use cairo_get_target() to propagate errors from secondary contexts.
|
|
Use cairo_get_target() to propagate errors from secondary contexts.
|
|
Use cairo_get_target() to propagate errors from the secondary context.
|
|
Use cairo_get_target() to propagate errors from the secondary context.
|
|
Use cairo_get_target() to propagate errors from the secondary context.
|
|
Use cairo_get_target() to propagate errors from the secondary context.
|
|
Use cairo_get_target() to propagate errors from the secondary context.
|
|
Use cairo_get_target() to propagate errors from secondary contexts.
|
|
Use cairo_get_target() to propagate errors from the secondary context.
|
|
Use cairo_get_target() to propagate errors from the secondary contexts.
|
|
Use cairo_get_target() to propagate errors from the secondary context.
|
|
Use cairo_get_target() to propagate errors from the secondary context.
|
|
Return early before trying to emit an empty subset into the document -
avoids a potential use of an uninitialised status variable.
|
|
Bug 18140 identifies a case where we have an atomic increment, but not an
atomic exchange. We need both to implement atomic reference counting, so
add a second check to detect whether __sync_val_compare_and_swap
generates a non-atomic instruction.
Fixes http://bugs.freedesktop.org/show_bug.cgi?id=18140.
|
|
Mention in the API docs that you can pass a NULL filename to
cairo_(pdf|ps|svg)_surface_create in order to construct a queryable
surface without generating any temporary files. Similarly when passing a
NULL write_func to cairo_pdf_surface_create_for_stream et al.
|
|
Behdad prefers the latter to keep a clean namespace.
|
|
Currently the emulation of Porter-Duff operators does not correctly
handle the unbounded operators.
|
|
We're unable to satisfactorily emulate SATURATE using the src/dst blend
modes, so fallback. (Might just be a bug in libdirectfb...)
|
|
Fallback if we have a clip that is not a simple region.
|
|
When blitting whether we need to use the premultiplied color is dependent
upon the destination surface capabilities.
|
|
We need to respect the current clip when copying the fallback image back to
the target surface.
|
|
DirectFB seems to use inclusive upper bounds.
|
|
The current version of DirectFB does not support any filters, so set
NEAREST on the source patterns so that we can fully optimize the pattern
inside core.
|
|
A region with no extents means everything should be clipped out, so we
need an extra flag to disambiguate when we have 0 clip rectangles.
|
|
Fallback if we need to create a cache larger than the maximum usable
surface.
|
|
If we have non-integer translation on a source pattern then we need to use
STRECTHBLIT (the core takes care to optimize NEAREST patterns to integer
translations so that this will only be used when interpolation is
required).
|
|
Explicitly list the extend modes that are supported/unsupported and
immediately check for an unsupported operation.
|
|
Only clone the ROI in order to efficiently handle large sources.
|
|
Use _cairo_directfb_surface_backend for consistency with other backends.
|
|
Trim lots of trailing whitespace and fix up according to CODING_STYLE.
|
|
Used only as a predicate, so simply return a boolean.
|
|
The dfb backend recreated a solid color surface for every colour,
completely bypassing the solid pattern cache.
|
|
Create an RGB or ARGB surface depending upon the content type of the test
target, with the result that the directfb rgb24 target no longer
unconditionally fails.
|
|
Rename the temporary variable in line with the convention used by the rest
of the build system.
|
|
Fix memleak of the image surfaces.
|
|
PS (ghostscript) interprets the degenerate end-caps quite differently, and
perhaps slightly more rationally... Add this to XFAIL, until we have a
definitive specification on how we should behave.
|
|
|
|
Do not return NULL but an NO_MEMORY error surface if we fail to allocate
the surface during creation.
|
|
Simplify the ADD_TRI macro to make the code more readable.
|
|
We jumped to the ERROR path without setting an error status - assume
NO_MEMORY.
|
