diff options
| author | David Turner <david@freetype.org> | 2006-03-20 12:10:24 +0000 |
|---|---|---|
| committer | David Turner <david@freetype.org> | 2006-03-20 12:10:24 +0000 |
| commit | 256de4b18f556b963597f171a217c0c1ed045993 (patch) | |
| tree | a8867ae8ce429ca1c4e4283fbd2946f31fdefb18 /src/cache/ftcsbits.c | |
| parent | dad2a2de0174740fb1bf79953d3620df8a75916f (diff) | |
| download | freetype-256de4b18f556b963597f171a217c0c1ed045993.tar.gz | |
* include/freetype/cache/ftccache.h,
include/freetype/cache/ftccmap.h,
include/freetype/cache/ftcglyph.h
include/freetype/cache/ftcimage.h
include/freetype/cache/ftcmanag.h
include/freetype/cache/ftcmru.h
include/freetype/cache/ftcsbits.h:
removing these header files from the public include directory.
* include/freetype/config/ftheader.h:
changing the definition of FT_CACHE_INTERNAL_XXX_H macros to
redirect to FT_CACHE_H instead
* src/cache/ftcbasic.c, src/cache/ftccache.c, src/cache/ftccache.h,
src/cache/ftccback.h, src/cache/ftccmap.c, src/cache/ftcglyph.c,
src/cache/ftcglyph.h, src/cache/ftcimage.c, src/cache/ftcimage.h,
src/cache/ftcmanag.c, src/cache/ftcmanag.h, src/cache/ftcmru.c,
src/cache/ftcmru.h, src/cache/ftcsbits.c, src/cache/ftcsbits.h:
modifications to prevent using the FT_CACHE_INTERNAL_XXX_H macros,
and grab the headers in 'src/cache' instead (see below).
Diffstat (limited to 'src/cache/ftcsbits.c')
| -rw-r--r-- | src/cache/ftcsbits.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/cache/ftcsbits.c b/src/cache/ftcsbits.c index 891c7ab8e..4e544d877 100644 --- a/src/cache/ftcsbits.c +++ b/src/cache/ftcsbits.c @@ -18,7 +18,7 @@ #include <ft2build.h> #include FT_CACHE_H -#include FT_CACHE_INTERNAL_SBITS_H +#include "ftcsbits.h" #include FT_INTERNAL_OBJECTS_H #include FT_INTERNAL_DEBUG_H #include FT_ERRORS_H @@ -341,7 +341,7 @@ * However, we need to `lock' the node before this operation to * prevent it from being flushed within the loop. * - * When we exit the loop, we unlock the node, then check the `error' + * When we exit the loop, we unlock the node, then check the `error' * variable. If it is non-zero, this means that the cache was * completely flushed and that no usable memory was found to load * the bitmap. |