On 26/06/2019 21:10, [email protected] wrote:
g++ `pkg-config freetype2 --cflags --libs` test.cpp

This works for me (Debian Unstable). Output was

   Initialised OK!

Same for me ...

I'm not sure what to try next. Does anyone have any suggestions?

Try compiling it as C, rather than C++ code? (Both worked for me, by the way.)

I was thinking that as well;  also, are you sure that whatever resides in 
`/lib/x86_64-linux-gnu/libfreetype.so' actually exports `FT_Init_FreeType' 
(there's a chance that this was overwritten with an ill-formed install)?

Armin


Thanks very much for your replies, everyone!

If you can compile that code correctly, then presumably that means you have a package I don't, or a path setup that I don't.

If I use "nm" to examine libfreetype.a then that gives me a list of symbols (including FT_Init_FreeType) :

$ nm /lib/x86_64-linux-gnu/libfreetype.a | grep FT_Init_FreeType

0000000000000210 T FT_Init_FreeType



But I get nothing when I do the same for the .so:

$ nm /lib/x86_64-linux-gnu/libfreetype.so

nm: /lib/x86_64-linux-gnu/libfreetype.so: no symbols

... is that my problem?



 ls -l /lib/x86_64-linux-gnu/ | grep free
lrwxrwxrwx 1 root root 17 Feb 19 11:04 libfreebl3.so -> nss/libfreebl3.so lrwxrwxrwx 1 root root 21 Feb 19 11:04 libfreeblpriv3.so -> nss/libfreeblpriv3.so
-rw-r--r--  1 root root  1055516 Nov 22  2018 libfreetype.a
lrwxrwxrwx 1 root root 21 Nov 22 2018 libfreetype.so -> libfreetype.so.6.16.1 lrwxrwxrwx 1 root root 21 Nov 22 2018 libfreetype.so.6 -> libfreetype.so.6.16.1
-rw-r--r--  1 root root   759720 Nov 22  2018 libfreetype.so.6.16.1

Kris.

_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype

Reply via email to