Re: [ft-devel] about freetype-1.3.1 compile issue
Hi On Mon, 20 Feb 2006 17:03:15 +0800 Giant SZ Li [EMAIL PROTECTED] wrote: How do you compile static library libttf.a for ARM7? our arm7 platform run linux 2.4, our cross compiler is arm-linux-uclibc-(3.4.2 version)! I download freetype-1.3.1.tar.gz, and uncompress it, cd freetype-1.3.1 ./configure --disable-shared --enable--static then make I think freetype-1.3.1 had been packaged before autoconf knows the name of arm-uclibc-linux, I'm not sure if configure works well for the target. Have you checked the object files are really compiled with uclibc headers? Now I'm trying to cross build on glibc-based Linux/ARM to uclibc library. Regards, mpsuzuki ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Relevance of new API FT_Get_Module_Flags ?
Could someone tell me the relevance of the new public API named FT_Get_Module_Flags that was introduced in the current CVS ? This might be answered best by Owen -- he has requested that feature, and he also provided the patch. If this function's purpose is to determine wether the bytecode interpreter is activated in a given FreeType build, I'd rather like to see a specific API that returns a boolean, or an enum, instead of asking users to understand our specific flags (which we may need to change in the future, btw) This is OK with me. Owen? Wasn't me... maybe it was George? Ah, sorry, it was Huw. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] about freetype-1.3.1 compile issue
How do you compile static library libttf.a for ARM7? our arm7 platform run linux 2.4, our cross compiler is arm-linux-uclibc-(3.4.2 version)! Why do you need FreeType 1.3? Due to the modular design of FreeType 2.x you probably get a smaller library because you can deactivate all unneeded stuff. Besides this, version 1.x is no longer supported. I download freetype-1.3.1.tar.gz, and uncompress it, cd freetype-1.3.1 ./configure --disable-shared --enable--static then make it can produce libttf.a in the lib/.libs directory! but how can I configure for my embedded arm7 system? Normally this is controlled with the --host, --build, and --target options of the configure script. I can't remember whether version 1.x supports cross compiling. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] OTB support broken
The attached font isn't displayed correctly with ftview from the CVS (using devel/ftoption.h). Werner Ambrosia.otb.bz2 Description: Binary data ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Relevance of new API FT_Get_Module_Flags ?
On Tue, Feb 21, 2006 at 07:03:15AM +0100, Werner LEMBERG wrote: Could someone tell me the relevance of the new public API named FT_Get_Module_Flags that was introduced in the current CVS ? This might be answered best by Owen -- he has requested that feature, and he also provided the patch. If this function's purpose is to determine wether the bytecode interpreter is activated in a given FreeType build, I'd rather like to see a specific API that returns a boolean, or an enum, instead of asking users to understand our specific flags (which we may need to change in the future, btw) This is OK with me. Owen? Wasn't me... maybe it was George? Ah, sorry, it was Huw. Yes it was me. Its purpose was exactly that, to determine whether the bytecode interpreter is enabled in a given build. A specific API that returns either a bool or an enum would be fine. Huw. ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] OTB support broken
Oops, that was my fault, I've commited a fix - David Werner LEMBERG a écrit : The attached font isn't displayed correctly with ftview from the CVS (using devel/ftoption.h). Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel *** Information contained in this email message is confidential and may be privileged, and is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the [EMAIL PROTECTED] and destroy the original message. *** ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] First FreeType 2.2.0 release candidate available
Hello, I've just tagged the first candidate for the FreeType 2.2.0 release and invite any brave soul and distribution maintainer to try it out in order to find any problems with it. This release candidate is intended to *not* break any desktop on not-too-old Unix distributions. By not-too-old, I mean anything that was provided and compiled against FreeType 2.1.7 or later. We've made considerable efforts to avoid breaking any ABI compatibility from well known rogue clients (i.e. libraries and programs that directly peek at font engine internals, or those who use beta/experimental APIs we didn't intend to be used in production code) There are two ways to get it: - the first one is to use anonymous CVS: - the CVSROOT is :pserver:[EMAIL PROTECTED]:/sources/freetype - the module name is 'freetype2' - the tag is 'VER-2-2-0-RC1' for example, use the following command: cvs -z3 -d:pserver:[EMAIL PROTECTED]:/sources/freetype co /freetype2 you'll need to regenerate the 'configure' script by doing the following: cd freetype2 sh autogen.sh install as usual: ./configure --prefix=yourprefix --disable-static make make install(eventually as root) - the second one is to download the pre-packaged tarball at: http://turnerdavid.neuf.fr/freetype/freetype-2.2rc1.tar.bz2 this one already contains a valid 'configure' script for Linux systems. You may need to run 'autogen.sh' on other systems though Please report any problem you encounter. We hope you'll not find a single one, but we don't have the time to test on a wide array of distributions at the moment. We'll release new candidates as soon as we get feedback. IMPORTANT NOTE: This release breaks *sources* compatibility for any rogue client. Fortunately, these are rather rare, and we provide some patches for most of them at the following address: http://www.freetype.org/freetype2/patches/rogue-patches.html Best Regards, - David Turner - The FreeType Project (www.freetype.org) / ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
