Re: [ft-devel] how to forbid to link public-but-unrecommended function in libfreetype.dylib?

2006-10-13 Thread David Turner
Hello mpsuzuki, The trick is ugly, but it is pretty commonly done :-) I would recommend the following though: - don't protect the header files with #ifdef FT2_BUILD_LIBRARY, this ensures that no user will be tempted to defined the macro by hand just to get it to compile. - at the start of s

[ft-devel] how to forbid to link public-but-unrecommended function in libfreetype.dylib?

2006-10-12 Thread mpsuzuki
Dear Sirs, As I've written in previous post, for MacOSX, I want to replace Carbon-based MacOS font support by Carbon-free implementation. However, a few functions using MacOS specific legacy datatypes (like FSSpec which cannot handle long UTF-8 filename) in their arguments cannot be replaced. When