Re: [ft-devel] Force PMingLiU like font do HINTING
One last (perhaps stupid) question: What happens (with or w/o the proposed change) for tricky fonts when ft is compiled with -DTT_CONFIG_OPTION_BYTECODE_INTERPRETER? OK. Two questions. What about the cases where autofitting or light autofitting is requested and the font is tricky? Do the instructions get run? -JimC (thinking up corner cases) (For the curious: it turned out to be 6 dm of snow in need of shoveling the other day; but at least it was mostly nice, soft powder.) -- James Cloos [EMAIL PROTECTED] OpenPGP: 1024D/ED7DAEA6 ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Invalid Preprocessor directive: #include FT_FREETYPE_H
Hi, thanky fior helping me. The only problem was that I diidnt link against the lib. I had to tell the gcc -I/usr/include/freetype2 and -lfreetype -lz now its working! ;) greetings -- View this message in context: http://www.nabble.com/Invalid-Preprocessor-directive%3A--include-FT_FREETYPE_H-tp19778956p20884552.html Sent from the Freetype - Dev mailing list archive at Nabble.com. ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Invalid Preprocessor directive: #include FT_FREETYPE_H
The only problem was that I diidnt link against the lib. I had to tell the gcc -I/usr/include/freetype2 and -lfreetype -lz now its working! ;) You should use `freetype-config --cflags' and `freetype-config --libs' for that. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Invalid Preprocessor directive: #include FT_FREETYPE_H
Werner LEMBERG wrote: The only problem was that I diidnt link against the lib. I had to tell the gcc -I/usr/include/freetype2 and -lfreetype -lz now its working! ;) You should use `freetype-config --cflags' and `freetype-config --libs' for that. Werner I got the paths with `freetype-config --cflags' and `freetype-config --libs' Then I added them to my Eclipse Project options. Is this the wrong way to do? How is the correct one? Lukas -- View this message in context: http://www.nabble.com/Invalid-Preprocessor-directive%3A--include-FT_FREETYPE_H-tp19778956p20886179.html Sent from the Freetype - Dev mailing list archive at Nabble.com. ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Invalid Preprocessor directive: #include FT_FREETYPE_H
I got the paths with `freetype-config --cflags' and `freetype-config --libs' Then I added them to my Eclipse Project options. Is this the wrong way to do? How is the correct one? It is the correct way; I only mean that you shouldn't add the values manually but use code like this within your makefile: freetype_cflags = `freetype-config --cflags` freetype_libs = `freetype-config --libs` CFLAGS += $freetype_cflags LDFLAGS += $freetype_libs Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Invalid Preprocessor directive: #include FT_FREETYPE_H
Werner LEMBERG wrote: I got the paths with `freetype-config --cflags' and `freetype-config --libs' Then I added them to my Eclipse Project options. Is this the wrong way to do? How is the correct one? It is the correct way; I only mean that you shouldn't add the values manually but use code like this within your makefile: freetype_cflags = `freetype-config --cflags` freetype_libs = `freetype-config --libs` CFLAGS += $freetype_cflags LDFLAGS += $freetype_libs Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel Ok, thats clear! ;) Thank you -- View this message in context: http://www.nabble.com/Invalid-Preprocessor-directive%3A--include-FT_FREETYPE_H-tp19778956p20886305.html Sent from the Freetype - Dev mailing list archive at Nabble.com. ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Force PMingLiU like font do HINTING
What happens (with or w/o the proposed change) for tricky fonts when ft is compiled with -DTT_CONFIG_OPTION_BYTECODE_INTERPRETER? The patented hinting is forced then. What about the cases where autofitting or light autofitting is requested and the font is tricky? Do the instructions get run? Yes, always, except if you use both `FT_LOAD_NO_HINTING' and FT_LOAD_NO_AUTOHINT. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
