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
Could you agree with the restriction of the current scope to
FT_SIZEOF_INT FT_SIZEOF_LONG?
I agree with everything since I don't have the means to test by
myself :-) Please go ahead.
Werner
___
Freetype-devel mailing list
On Thursday, July 10th, 2008, Werner LEMBERG wrote:
Freetype effectively expects 8-bit char (I am not sure 9-bit chars
or 16-bit chars could work or not, but I believe nobody checks it
anyway).
This is not correct. Some time ago a guy asked for support of 16-bit
chars, and support for it has
On Tuesday, July 1st, 2008, Sean McBride wrote:
On 7/1/08 10:19 PM, Werner LEMBERG said:
Can freetype use C99 features?
Not in general, but I don't object to put it into proper
#ifdef...#endif blocks -- AFAIK, C99 can be checked by a preprocessor
macro, right?
Yes. __STDC_VERSION__ is
Hi Suzuki-san,
On Tue, 8 Jul 2008 22:39:58 +0200
Antoine Leca wrote:
There is a real defect with the above approach: imagine a conforming C90
compiler with 32 bits being the widest type; on such a compiler, cpp would
evaluate the quantities using 32-bit arithmetic
snip
So my revised
On Wednesday, July 9th, 2008 , mpsuzuki wrote:
On Tue, 8 Jul 2008 22:56:12 +0200
Antoine Leca wrote:
On Wednesday, July 2nd, 2008, mpsuzuki noted:
On many platforms, gcc does not set the value __STDC_VERSION__
by default. Users have to set by -std=xxx option.
On the other hand, it does not
On a historical perspective, the real stuff was about detecting
32-bit int's, because several parts of the library could not be
handled with 16-bit int, so we (well, DavidWerner;-)) decided long
ago to use (now named as) FT_Int32 everywhere, requesting it to be
at least 32 bits.
Hmm.
Hi Suzuki-san,
On Tue, 8 Jul 2008 22:39:58 +0200
Antoine Leca wrote:
There is a real defect with the above approach: imagine a conforming C90
compiler with 32 bits being the widest type; on such a compiler, cpp would
evaluate the quantities using 32-bit arithmetic
snip
So my revised
On Tuesday, July 1st, 2008, Sean McBride wrote:
On 7/1/08 10:19 PM, Werner LEMBERG said:
Can freetype use C99 features?
Not in general, but I don't object to put it into proper
#ifdef...#endif blocks -- AFAIK, C99 can be checked by a preprocessor
macro, right?
Yes. __STDC_VERSION__ is
On Tue, 8 Jul 2008 22:39:58 +0200
Antoine Leca [EMAIL PROTECTED] wrote:
On Monday, June 30th, 2008, mpsuzuki wrote:
So, I think, using traditional ANSI C header limits.h
is more generic than using modern headers bits/wordsize.h, like...
#ifdef HAVE_LIMITS_H
# if ( UINT_MAX ==
On Tue, 8 Jul 2008 22:56:12 +0200
Antoine Leca [EMAIL PROTECTED] wrote:
On Wednesday, July 2nd, 2008, mpsuzuki noted:
On many platforms, gcc does not set the value __STDC_VERSION__
by default. Users have to set by -std=xxx option.
On the other hand, it does not seem unreasonable to me to
As I've written, I will join the discussion tomorrow,
but I have to note:
On many platforms, gcc does not set the value __STDC_VERSION__
by default. Users have to set by -std=xxx option.
Regards,
mpsuzuki
On Wed, 02 Jul 2008 06:43:41 +0200 (CEST)
Werner LEMBERG [EMAIL PROTECTED] wrote:
Yes.
On 6/30/08 10:11 PM, [EMAIL PROTECTED] said:
One of my anxiety is that the sizes obtained by AC_CHECK_SIZEOF()
would be more reliable than the sizes deduced by limits.h (although
yet I've not checked the detail that how configure script checks
the sizes).
I want to check the sizes by
Can freetype use C99 features?
Not in general, but I don't object to put it into proper
#ifdef...#endif blocks -- AFAIK, C99 can be checked by a preprocessor
macro, right?
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
On 7/1/08 10:19 PM, Werner LEMBERG said:
Can freetype use C99 features?
Not in general, but I don't object to put it into proper
#ifdef...#endif blocks -- AFAIK, C99 can be checked by a preprocessor
macro, right?
Yes. __STDC_VERSION__ is defined as 199901L. See for example:
Yes. __STDC_VERSION__ is defined as 199901L. See for example:
http://lists.debian.org/debian-mentors/2002/10/msg00216.html
Thanks. However, I think it would be better to test for `greater or
equal' than just for `equal'.
Werner
___
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:
In order to have headers usable for both 32 and 64 bit mode, that
ought to be replaced by something like [...]
You've already reported this:
https://savannah.nongnu.org/bugs/index.php?21250
unfortunately, it hasn't been handled yet. Maybe Suzuki-san (who has
access to a 64bit-system,
Dear Peter,
# also I Cc: this message to [EMAIL PROTECTED]
# who recently asked about 64bit support of FreeType2.
I have to apologize to all people waiting for the terminal fix
for the solution. While I was waiting for the stabilization of
Mac OS X 64bit development style, I guess GNU/Linux
19 matches
Mail list logo
