Hello Alexei,
On Thu, Jan 19, 2012 at 4:08 AM, Alexei Podtelezhnikov
apodt...@gmail.comwrote:
On Fri, Jan 13, 2012 at 2:13 PM, Werner LEMBERG w...@gnu.org wrote:
3. Grant of Patent License.
Do freetype authors hold or have they filed for a patent? Don't you
need it first before
I'm using freetype2 on an embedded device. When I run my application
on device with 7-inch display all the glyphs are rendered fine [...]
If I run the same application on a device with 9-inch or 12-inch
display some glyphs (V, v, Y and y) are not rendered correctly.
It looks like a font
Hello Alexei,
On Thu, Jan 19, 2012 at 4:08 AM, Alexei Podtelezhnikov
apodt...@gmail.comwrote:
On Fri, Jan 13, 2012 at 2:13 PM, Werner LEMBERG w...@gnu.org wrote:
3. Grant of Patent License.
Do freetype authors hold or have they filed for a patent? Don't you
need it first before
I'm interested in building an amalgamated version of FreeType. Specifically,
I would like to use an in-house tool to combine all the FreeType headers and
source files into a set consisting of a single .h and .c (or a couple of .c
files if they are too large). This amalgamation would be much
On Jan 19, 2012, at 8:32 AM, Vinnie wrote:
I'm interested in building an amalgamated version of FreeType.
I would love to be able to use that. Currently I don't build FreeType as a
library, I add twenty-five FreeType C files directly to the project or makefile
in which they are used. (For
On Jan 19, 2012, at 8:32 AM, Vinnie wrote:
I'm interested in building an amalgamated version of FreeType.
I would love to be able to use that. Currently I don't build FreeType as a
library, I add twenty-five FreeType C files directly to the project or makefile
in which they are used. (For
I have no objection to the statement compiling single C
source to single object is much easier than compiling much
single file is easier than compiling multiple C sources
to single library, and I have to accept that many newbies
had a difficulty to understand the process how to build
libfreetype.
On Fri, 20 Jan 2012 06:04:04 +0100 (CET)
Werner LEMBERG w...@gnu.org wrote:
BTW, during the overhaul of PIC mode building, I found there are
several macros that would not work if all sources are concatenated.
Werner, should we care the inter-module namespace separation of cpp
macros?
This is
2012/1/19 mpsuz...@hiroshima-u.ac.jp:
However, the source structure of FreeType2 is related with
the modularization of each features and binary compatibilities,
so the official support of the concatenated C source can be
slightly difficult (sorry!).
Can you use this?
1) Some FreeType #include statements use angle brackets instead of
double quotes. e.g. #include ft2build.h Why?
This is to control inclusion with the -I command line flag of the
compiler. Think of build_dir != src_dir (which is very common on Unix
boxes).
2) Some FreeType #include
Can you give an example? Perhaps we can rename macros if it is not
too cumbersome.
An example is GET_PIC() macro defined by src/xxx/yyypic.h.
Aah, this is stuff written by a contributor, and which I've never had
the energy to fully integrate (including formatting) because it is
disabled by
Werner LEMBERG wrote:
Can you give an example? Perhaps we can rename macros if it is not
too cumbersome.
An example is GET_PIC() macro defined by src/xxx/yyypic.h.
Aah, this is stuff written by a contributor, and which I've never had
the energy to fully integrate (including formatting)
Werner LEMBERG wrote:
3) A new ftconfig.h should be created that has a preamble for
decoding the platform, [...]
How shall this work? There are dozens of platforms, and you want to
hard-code them all in a configuration header file?
I'm afraid that MacOS specific ugly hacks (detecting Mac
13 matches
Mail list logo
