[ft-devel] ftconfig.h in LSB

[Camp, TracyX E]

For libraries in LSB we generally avoid importing things like 'config.h'
since they tend to define macros that are of interest when building the
library but not of direct relevance to the API or ABI.

Are there any cases where (say macros), depend on the defines in
ftconfig.h?

fttypes.h seems to nicely encapsulate the API/ABI types independantly
from ftconfig.h.  Bad/Good assumption?

Thanks,

Tracy Camp