Generally speaking, this is what <ft2build.h> should be used for. it should include either a 32-bit or 64-bit version of ftconfig.h depending on the compiling environment. Ideally, this should be the only file that knows about OS-specific files like <bits/wordsize.h>
- David 2008/6/30 Peter Breitenlohner <[EMAIL PROTECTED]>: > Hi, > > For various reasons I have to install on our linux-x86_84 systems > the 64 bit version of libfreetype (in /usr/lib64/) as well as the > 32 bit (linux-i686) version (in /usr/lib/). > > So far, no problem. > > However, the headers installed in /usr/include/freetype2/freetype/ differ > at > one point: > > config/ftconfig.h contains (SIZEOF_LONG being replaced by 8 or 4) > #define FT_SIZEOF_LONG 8 > for the 64 bit version, and > #define FT_SIZEOF_LONG 4 > for the 32 bit version. > > Of course, the same kind of problem occurs for other biarch systems such as > ppc/ppc64, sparc32/sparc64, etc. > > In order to have headers usable for both 32 and 64 bit mode, that ought to > be replaced by something like > > (1) for systems with <bits/wordsize.h> (should include all biarch systems) > > #include <bits/wordsize.h> > #if __WORDSIZE == 64 > #define FT_SIZEOF_LONG 8 > #else > #define FT_SIZEOF_LONG 4 > #endif > > (2) for systems without <bits/wordsize.h> > > #define FT_SIZEOF_LONG SIZEOF_LONG > > Getting this result might require some autoconf magic, but should not be > overly difficult. > > Best regards > Peter Breitenlohner <[EMAIL PROTECTED]> > > > _______________________________________________ > Freetype-devel mailing list > Freetype-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/freetype-devel >
_______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
