Re: [ft-devel] Configuring for alternative build environments
The problem is that I have a customized version of ftoption.h. According to CUSTOMIZE, Just put your custom `ftoption.h' file into the objects directory. When I do this sequence: $ cd ~/work $ cp jni-ftoption.h ~/work/ft2-jni/ftoption.h $ cd ~/work/ft2-jni $ ~/ft2/freetype2/configure CFLAGS=-fPIC $ make My customized version of ftoption.h disappears! Oops. This is a bug. I've just fixed it in the git repository. Thanks for the report, and please retry! Related: CUSTOMIZE seems silent on the handling of modules.cfg in this scenario of building outside of the FT source tree. Can you suggest a patch to CUSTOMIZE? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Configuring for alternative build environments
Here's the suggestion, with a bonus tweak to INSTALL.CROSS. [...] Thanks, committed! Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Configuring for alternative build environments
Hello - I'm building a Java Native Interface (JNI) into freetype. I've read freetype-2.4.10's CUSTOMIZE and I'm poking around in ftsystem.c. What I would like is a way to build an FT_Stream that allows me to pass in my own stream handler(s), independent of the C RTL. These stream handlers will actually use Java's I/O - a pre-opened (i.e., no filename readily available) InputStream. My questions: 1. Has anyone already done and published something like this? If not, 2. Any suggestions on Best Practice? It looks like for starters I'll be overriding a bunch of the contents of ftstdlib.h - things like fseek would be replaced by my own, Java-specific version that operates on the InputStream. Thanks for any comments and suggestions, -Del ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
