There's two "freetypes": freetype and freetype2. Likely your packaged freetype came with only the shared libraries used by applications when they run, and not the other files needed to actually compile something that wants to make use of freetype. Like the other post says, sometimes there's a "devel" version of the package as well which you may be able to install in addition to what you have already. Or you can build freetype from source yourself, which will then include the whole kit & kaboodle. If you do go that route, you'll have to uninstall any old freetype packages before you put the source built ones in its place. Be careful, as sometimes some of your apps will use those libraries that would get uninstalled. To make sure, check and see which files will be removed, then save a copy of the .so (shared object) libraries that would be removed. Go about your build, and install the new, complete freetype in the place of the old one. Run ldconfig to update the shared object cache, and test out some apps. that use freetype. They should work, but if anything goes wrong, you still have the old .so libs and can put them back temporarily, just make sure anything you're building from here on in uses the new libraries and not the old one, so that you can eventually phase the old version out. An alternative is to recompile things that used the old libraries using the new ones. This may end up being quite a bit of work, depending on the libraries you're dealing with. You can use
Code:
ldd <dynamically linked application>
to find out which libraries a certain application is needing.
If you are using GCC and it's a newer version, you may have trouble compiling freetype 1.3.1, in particular the file ftdump.c. However, I just posted a patch for this taken from the composite of several other patches I found while researching why my own freetype 1.3.1 build was failing on the make of ftdump.c.
