TINTU THOMAS | 21 May 13:32 2015
Picon

[ft] How to use freetype for embedded projects?

Hello freetype team ,


     I am a newbie to freetype and embedded system too. I want to use freetype functions in my embedded application (Details are given below).

At first i tried the instructions given in "http://www.freetype.org".

I could successfully complete a c project as in "example1.c" in ubuntu, which can display the raster image created by the freetype . 

But  I don't know how to link freetype library to keil ide or coocox ide.

I tried copying libfreetype.so file from ubuntu and linked it  in the coocox project. But it cannot identify the library.

Now I guess the library files are different for different toolchain. I read the documentation . Unfortunately didin't understand how to create library file for arm toolchain.

Can you please explain the way to link freetype to either keil or Coocox ide?


Project Details:
Controller : LPC1768
IDE : Keil uvision 4, uvision 5 or CoIDE 1.3.1



Thank you,

Tintu Thomas
         

_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
Jeffry Killen | 19 May 19:36 2015
Picon
Picon

[ft] Re running make fails

maybe I should have included the immediately preceding line:

/usr/bin/ld: /usr/local/lib/libz.a(inflate.o): relocation R_X86_64_32S  
against `zcalloc' can not be used when making a shared object;  
recompile with -fPIC

to
/usr/local/lib/libz.a: could not read symbols: Bad value
cc: error: linker command failed with exit code 1 (use -v to see  
invocation)
config.mk:55: recipe for target '/usr/local/freetype-2.5.5/objs/ 
libfreetype.la' failed
make: *** [/usr/local/freetype-2.5.5/objs/libfreetype.la] Error 1

JK
Jeffry Killen | 19 May 19:30 2015
Picon
Picon

[ft] running make fails

system: FreeBSD 10.1
Running /usr/local/bin/make (this make is GNU make) under sh

/usr/local/lib/libz.a: could not read symbols: Bad value
cc: error: linker command failed with exit code 1 (use -v to see  
invocation)
config.mk:55: recipe for target '/usr/local/freetype-2.5.5/objs/ 
libfreetype.la' failed
make: *** [/usr/local/freetype-2.5.5/objs/libfreetype.la] Error 1

Any explanations and what might be done about it?

Thanks for time and attention:
JK
Jeffry Killen | 18 May 01:40 2015
Picon
Picon

[ft] Ongoing Re: Installation issue

Original thread subject line
[ft] Installation issue

Hello
I have followed advice about getting freetype 2.5.5
downloaded it and unpacked it

change shell to sh

MAKE=/usr/local/bin/make ./configure ran fine

Make did not

Here are the gory details:

# MAKE=/usr/local/bin/make ./configure

FreeType build system -- automatic system detection

The following settings are used:

   platform                    unix
   compiler                    cc
   configuration directory     ./builds/unix
   configuration rules         ./builds/unix/unix.mk

If this does not correspond to your system or settings please remove  
the file
`config.mk' from this directory then read the INSTALL file for help.

Otherwise, simply type `/usr/local/bin/make' again to build the library,
or `/usr/local/bin/make refdoc' to build the API reference (this needs  
python >= 2.6).

----------------------------------
annotated comment from me:
Is the above why make failed?
------------------------------------

Generating modules list in ./objs/ftmodule.h...
* module: truetype  (Windows/Mac font files with extension *.ttf or  
*.ttc)
* module: type1     (Postscript font files with extension *.pfa or  
*.pfb)
* module: cff       (OpenType fonts with extension *.otf)
* module: cid       (Postscript CID-keyed fonts, no known extension)
* module: pfr       (PFR/TrueDoc font files with extension *.pfr)
* module: type42    (Type 42 font files with no known extension)
* module: winfnt    (Windows bitmap fonts with extension *.fnt or *.fon)
* module: pcf       (pcf bitmap fonts)
* module: bdf       (bdf bitmap fonts)
* module: sfnt      (helper module for TrueType & OpenType formats)
* module: autofit   (automatic hinting module)
* module: pshinter  (Postscript hinter module)
* module: raster    (monochrome bitmap renderer)
* module: smooth    (anti-aliased bitmap renderer)
* module: smooth    (anti-aliased bitmap renderer for LCDs)
* module: smooth    (anti-aliased bitmap renderer for vertical LCDs)
* module: psaux     (Postscript Type 1 & Type 2 helper module)
* module: psnames   (Postscript & Unicode Glyph name handling)
done.
cd builds/unix; /bin/sh ./configure
checking build system type... x86_64-unknown-freebsd10.1
checking host system type... x86_64-unknown-freebsd10.1
checking for gcc... no
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking how to run the C preprocessor... cc -E
checking for pkg-config... no
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by cc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 196608
checking how to convert x86_64-unknown-freebsd10.1 file names to  
x86_64-unknown-freebsd10.1 format... func_convert_file_noop
checking how to convert x86_64-unknown-freebsd10.1 file names to  
toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver  <at> FILE support... no
checking for strip... strip
checking for ranlib... ranlib
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if cc supports -fno-rtti -fno-exceptions... yes
checking for cc option to produce PIC... -fPIC -DPIC
checking if cc PIC flag -fPIC -DPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking if cc supports -c -o file.o... (cached) yes
checking whether the cc linker (/usr/bin/ld) supports shared  
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... freebsd10.1 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for rmdir... rmdir
checking for a BSD-compatible install... /usr/bin/install -c
checking for ANSI C header files... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking size of int... 4
checking size of long... 8
checking whether cpp computation of bit length in ftconfig.in works...  
yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for sys/param.h... yes
checking for getpagesize... yes
checking for working mmap... yes
checking whether munmap is declared... yes
checking for munmap's first parameter type... void *
checking for memcpy... yes
checking for memmove... yes
checking gcc compiler flag -ansi to assure ANSI C works correctly...  
ok, add it to XX_ANSIFLAGS
checking for ZLIB... no
checking for gzsetparams in -lz... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for BZIP2... no
checking for BZ2_bzDecompress in -lbz2... yes
checking bzlib.h usability... yes
checking bzlib.h presence... yes
checking for bzlib.h... yes
checking for LIBPNG... no
checking for libpng-config... yes
checking for HARFBUZZ... no
configure: creating ./config.status
config.status: creating unix-cc.mk
config.status: creating unix-def.mk
config.status: creating ftconfig.h
config.status: executing libtool commands
configure:

Library configuration:
   external zlib: yes (autoconf test)
   bzip2:         yes (autoconf test)
   libpng:        yes (libpng-config)
   harfbuzz:      no

make: Nothing to be done for 'unix'.
# make
make: "./builds/./builds/toplevel.mk" line 41: Need an operator
make: "./builds/./builds/toplevel.mk" line 42: Missing dependency  
operator
make: "./builds/./builds/toplevel.mk" line 43: Missing dependency  
operator
make: "./builds/./builds/toplevel.mk" line 44: Need an operator
make: "./builds/./builds/toplevel.mk" line 60: Need an operator
make: "./builds/./builds/toplevel.mk" line 62: Missing dependency  
operator
make: "./builds/./builds/toplevel.mk" line 64: Need an operator
make: "./builds/./builds/toplevel.mk" line 65: Need an operator
make: "./builds/./builds/toplevel.mk" line 74: Could not find ./objs/ 
modules.cfg
make: "./builds/./builds/toplevel.mk" line 96: Missing dependency  
operator
make: "./builds/./builds/toplevel.mk" line 98: Need an operator
make: "./builds/./builds/toplevel.mk" line 102: Missing dependency  
operator
make: "./builds/./builds/toplevel.mk" line 104: Need an operator
make: "./builds/./builds/toplevel.mk" line 109: Need an operator
make: "./builds/./builds/toplevel.mk" line 113: Need an operator
make: "./builds/./builds/toplevel.mk" line 127: Missing dependency  
operator
make: "./builds/./builds/toplevel.mk" line 138: Need an operator
make: "./builds/./builds/toplevel.mk" line 145: Need an operator
make: "./builds/./builds/toplevel.mk" line 152: Need an operator
make: "./builds/./builds/toplevel.mk" line 154: Need an operator
make: "./builds/./builds/modules.mk" line 31: Missing dependency  
operator
make: "./builds/./builds/modules.mk" line 35: Need an operator
make: "./builds/./builds/modules.mk" line 39: Need an operator
make: "./builds/./builds/modules.mk" line 42: Need an operator
make: "./builds/./builds/modules.mk" line 43: Need an operator
make: "./builds/./builds/modules.mk" line 44: Need an operator
make: "./builds/./builds/modules.mk" line 45: Need an operator
make: "./builds/./builds/modules.mk" line 46: Need an operator
make: "./builds/./builds/modules.mk" line 52: Need an operator
make: "./builds/./builds/modules.mk" line 53: Need an operator
make: "./builds/./builds/modules.mk" line 54: Need an operator
make: "./builds/./builds/modules.mk" line 55: Need an operator
make: "./builds/./builds/modules.mk" line 57: Need an operator
make: "./builds/./builds/modules.mk" line 58: Need an operator
make: "./builds/./builds/modules.mk" line 59: Need an operator
make: "./builds/./builds/modules.mk" line 60: Need an operator
make: "./builds/./builds/" line 1: warning: Zero byte read from file,  
skipping rest of line.
make: "./builds/./builds/" line 1: Need an operator
make: "./builds/./builds/" line 3: warning: Zero byte read from file,  
skipping rest of line.
make: "./builds/./builds/" line 3: Need an operator
make: "./builds/./builds/" line 5: Need an operator
make: "./builds/./builds/toplevel.mk" line 178: Missing dependency  
operator
make: "./builds/./builds/toplevel.mk" line 187: Need an operator
make: Fatal errors encountered -- cannot continue
make: stopped in /usr/local/freetype-2.5.5
#
Jeffry Killen | 17 May 23:38 2015
Picon
Picon

[ft] Installation issue

Hello;

I am trying to compile and install freetype 2.4.0 on FreeBSD v10.1  
system

I have not installed gui software. This is for the sake of php gd  
extension only

Viewing the requirement for GNU make, I downloaded, compiled and  
installed it.
(GNU make v4.1)

In the /usr/local/bin dir I ran make -v and got the version
# and info. So I know that it exists and is working.

Now when I cd into the freetype dir and run
GNUMAKE=/usr/local/bin/make ./configure

I am greeted with the statement
  GNUMAKE=/usr/local/bin/make command not found

The shell is csh.

Any guidance on this issue?

The machine is not connected to the internet, so I
cannot use ports. And if I download an place the
tarball in the ports install dir and the port set to
look for a different version, it will ignore what I put
in the install dir and try to get the version it wants
from the net.

I am in the for-dummies-learn-by-doing
phase, so please have patience.

Thank you for time and attention
JK
Lewis Pike | 15 May 21:38 2015
Picon

[ft] Tahoma rendering differently on Freetype & Windows

I've noticed a rendering discrepancy between Freetype and the Windows
font engine.  I'm comparing output from Freetype 2.5.5 and Windows
XP's native rendering.

The font in question is Tahoma 12pt rendered at 96 dpi.  Note the bowl
of the lowercase 'a' differs between the two in the attached image.
IMHO Freetype's rendering isn't quite as nice.

I'm not sure if this qualifies as a bug, but to my eyes, it does seem
to look wrong.  It's amazing how a one-pixel difference can sometimes
be so immediately noticeable.

If this isn't a bug, is there a way for me to 'tune' the hinting to
match the results produced by Windows XP's native rendering?

.lewis
_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
Grissiom | 15 May 13:11 2015
Picon

[ft] A suspicious memory leak in src/truetype/ttgload.c: tt_loader_init

Hi all,

I'm porting FreeType-2.5.5 to an embedded RTOS. However, I found memory leak in looped `FT_Load_Char(fft->face, *text_ptr, FT_LOAD_RENDER)` while the memory won't leak if I set the load_flags ORed with FT_LOAD_NO_HINTING.

So I dive into the source code and found in the tt_loader_init, the `size->bytecode_ready` and `size->cvt_ready` are always -1, causing `tt_size_ready_bytecode` run on the same `size` repeatedly. So the previous content of size will be leaked.

I don't whether it is a bug in FreeType or a mis-using of the lib. So any guidance will be appreciated and I will provide anything I could if you need.

P.S. Great thanks to the FreeType devs! World get rendered and hinted because of you. ;)

--
Cheers,
Grissiom
_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
mathog | 13 May 22:44 2015
Picon

[ft] Working around a bad ascender value?

Greetings,

I am attempting to fix a bug in Inkscape related to the use of this
truetype font:

   http://www.1001freefonts.com/harrington.font

The bug is that a bounding box used when glyphs are drawn is roughly 
half the height of the glyphs, so they are cut off at the knees, so to 
speak.

After much debugging it was determined that the ascender and descender 
values returned by Freetype for the problem font are not good.

Ascender:750
Descender:-170
Bbox: xMin  -430 xMax  3162 yMin  -885 yMax  3080
UpEM: 4096

The ascender is much smaller than yMax, and the descender much greater 
than
yMin.  (The height value also  looks wrong, it is only 929.)  The values 
are small enough to account for the problem, because the bounding box in 
question is derived from the Ascender and Descender values.

For comparison, here are the same values for Arial (which like most 
fonts, works fine
with Inkscape)

Ascender:1854
Descender:-434
Bbox: xMin -1361 xMax  4154 yMin  -665 yMax  2124
UpEM: 2048

In the Freetype documentation there are references to sTypoAscender, 
which is said to
be pretty reliable.  However, I do not see how to retrieve this value 
through
the Freetype API.

How does one retrieve information from the OS/2 table (assuming one is 
present)?

Is there some other common workaround for this sort of problem?

Thank you,

David Mathog
mathog <at> caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
Stanislav Baiduzhyi | 26 Apr 13:24 2015
Picon

[ft] Emboldening monospaced fonts

Good day,

There are some good looking programmer fonts without bold variant available 
[1]. Makes those fonts little inconvenient for code editors where bold is used 
as highlight. I went for FT_GlyphSlot_Embolden, but it breaks the 
"monospaceness" of the font. Is there a way to embolden the font without 
breaking the monospaced font?

[1]: http://en.wikipedia.org/wiki/Monaco_(typeface)
--

-- 
Regards,
    Stas
Semeriak, AleksandraX | 24 Apr 16:08 2015
Picon

[ft] Freetype x86

Dear FreeType Team,

My name is Aleksandra Semeriak and I am an account manager within the Software & Services Group (SSG) at Intel Corporation. We have come across several great Android apps that are taking advantage of Freetype.

As far as I found out the Freetype does support Android x86 platforms natively, although this option is not set by default. This might become a roadblock for some developers who are working to port their applications to Android x86. We would like to know if there would be an interest from your side and opportunity to make the x86 version the default version of Freetype. If you have any additional questions or requests, I would be happy to help.

 

Looking forward to hearing back from you.

 

Sincerely,

Aleksandra Semeriak

Intel Software Partner Program

+44 3300088836

aleksandrax.semeriak <at> intel.com

aleksandra.semeriak.work

P Please consider the environment before printing this email.

Intel is committed to protecting your privacy. For more information about Intel's Privacy Notice, please visit www.intel.com/privacy

or write Intel Corporation, ATTN Privacy, Mailstop RNB4-145, 2200 Mission College Blvd., Santa Clara, CA 95054 USA.

 

_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
Wojciech Mamrak | 15 Apr 11:06 2015
Picon

[ft] FT_FloorFix and FT_CeilFix

Hello,

FT_FloorFix does not round towards minus infinity and FT_CeilFix
towards plus infinity for fractional
negative values. This is inconsistent with expected semantics as well
as the docs, according to which these functions work as expected. The
problem with the docs is, that FT_RoundFix is semantically correct,
yet the description is incorrect w.r.t. to its semantics.
Werner pointed me out these are solitary (legacy?) functions not used
in FT anywhere, added back in 2001.

Example for FT_FloorFix: http://coliru.stacked-crooked.com/a/5f2b10846110c3d7

Please comment.

Gmane