On Mon, Nov 21, 2005 at 01:06:22AM +0100, Hans-Peter Jansen wrote:
> (FT_Stream_OpenGzip and FT_Stream_OpenLZW still used FT_EXPORT).
They should be FT_EXPORT'ed as they are not used inside freetype.
I don't know how to use them though.
> That leaves me with a couple of questions:
> - Should I prepare some (more) diffs from these issues?
If you just want to test CVS freetype, you can use the attached _hack_
to make freetype export all symbols. Then all apps using freetype
should compile.
BTW, Should this hack be included in CVS temporary? Current CVS sort of
discourages people from testing.
> - What are your plans with this unofficial ftstream interface?
You can find ftglue.[ch] in pango which re-implement many FT_Stream
related functions. There is also a patch for fontconfig to use ftglue.
> - Any rough estimation on code maturity of current CVS?
--
Regards,
olv
=== builds/exports.mk
==================================================================
--- builds/exports.mk (revision 2912)
+++ builds/exports.mk (local)
@@ -64,6 +64,7 @@
$(subst /,$(SEP),$(APINAMES_EXE)) -o$@ $(APINAMES_OPTIONS)
$(PUBLIC_HEADERS)
@echo TT_New_Context >> $(EXPORTS_LIST)
@echo TT_RunIns >> $(EXPORTS_LIST)
+ @echo '*' >> $(EXPORTS_LIST)
$(PROJECT_LIBRARY): $(EXPORTS_LIST)
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
