Dear Sirs,
Thank you for correcting my misunderstanding.
On Sat, 24 Mar 2007 16:39:43 +0800
Jjgod Jiang [EMAIL PROTECTED] wrote:
2007/3/23, [EMAIL PROTECTED] [EMAIL PROTECTED]:
Excuse me, please let me alter the phraseology:
Mac OS X 10.4.x on Intel Mac can execute 64bit Intel Mac binary?
On 3/26/07 4:47 PM, [EMAIL PROTECTED] said:
Just I've updated ftconfig.in and ftconfig.h (for
some building system without running configure) as
following:
#if ( defined( __APPLE__ ) !defined( DARWIN_NO_CARBON ) ) || \
( defined( __MWERKS__ ) defined( macintosh ))
/* no Carbon
Hi,
2007/3/23, [EMAIL PROTECTED] [EMAIL PROTECTED]:
Excuse me, please let me alter the phraseology:
Mac OS X 10.4.x on Intel Mac can execute 64bit Intel Mac binary?
Yes, I can confirm that, Intel Core 2 Duo (now all upgraded MacBook Pro,
MacBook and iMac using) is 64-bit CPU. Xcode Tools
On 3/23/07 7:04 AM, [EMAIL PROTECTED] said:
I see. Yet I've not checked 10.4.9, can it run 64bit Intel
Mac executables? I think Mac OS X upto 10.4.8 cannot execute
64bit Intel Mac executables.
In the other word, the case we have to exclude is building
64bit Intel Mac binary ON 10.4.9, not
Dear Sir,
Sean McBride wrote:
On 3/23/07 7:04 AM, [EMAIL PROTECTED] said:
I see. Yet I've not checked 10.4.9, can it run 64bit Intel
Mac executables? I think Mac OS X upto 10.4.8 cannot execute
64bit Intel Mac executables.
In the other word, the case we have to exclude is building
64bit
Dear Sir,
Sean McBride wrote:
On 3/24/07 12:02 AM, [EMAIL PROTECTED] said:
I see. Yet I've not checked 10.4.9, can it run 64bit Intel
Mac executables? I think Mac OS X upto 10.4.8 cannot execute
64bit Intel Mac executables.
In the other word, the case we have to exclude is building
64bit
On 3/24/07 1:48 AM, [EMAIL PROTECTED] said:
64bit-x86 Carbon will be provided in future
Yes.
it is possible that ppc64 Carbon is still missing in future.
No. Apple has already said that 64 bit Carbon will be for both Intel
and PPC. See:
http://www.apple.com/macosx/leopard/64bit.html
Thus,
On Thu, 22 Mar 2007 11:43:58 +0900, Miles Bader [EMAIL PROTECTED] said:
David Turner [EMAIL PROTECTED] writes:
this will generate an error with certain compilers/pre-processors if
__LP64__ is not defined. generally speaking #if X is not a
portable statement, except if you ensure that
The relevant part is where it says how to handle incorrect expression
syntax in an #if statement. Because where FOO is undefined, #if FOO
expands to a null expression which is not a valid one...
I have not found anything in the document that discusses this case; maybe I
missed it, but it's
On 3/22/07 10:17 AM, [EMAIL PROTECTED] said:
Now I'm going to commit your patch to CVS head,
but I have small question.
Your patch to builds/unix/ftconfig.in will disable
Carbon support on 64bit ABI in Intel Mac.
It means that the resource-fork based font support
(ftmac.c) are unavailable
Quoting David Turner [EMAIL PROTECTED]:
I haven't looked at other compilers, but I wouldn't be surprised to see that
this is
a GNU-specific extension, or it may come from a tradition of various Unix
pre-processors,
but certainly can't be generalized...
KR C allowed that syntax.
I had
David Turner [EMAIL PROTECTED] writes:
I had correct compilation, without warnings with all the following compilers
though:
MingW (GCC)
Visual C++ 6
Visual C++ 7
Borland C++ 5.5
OpenWatcom C++ (don't remember version)
Win32-LCC (don't remember version)
I also tried several
I have been working on updating VTK (www.vtk.org) from freetype
2.1.9 to the 2.3.2. It has gone pretty smoothly, thanks in part to
the detailed changelogs you guys keep, thank you!
I invest a considerable amount of time to maintain them...
Werner
Dear Sir,
Now I'm going to commit your patch to CVS head,
but I have small question.
Your patch to builds/unix/ftconfig.in will disable
Carbon support on 64bit ABI in Intel Mac.
It means that the resource-fork based font support
(ftmac.c) are unavailable completely. Not only
deprecated QuickDraw
David Turner [EMAIL PROTECTED] writes:
this will generate an error with certain compilers/pre-processors if
__LP64__ is not defined. generally speaking #if X is not a
portable statement, except if you ensure that the macro is always
defined beforehand.
Is this true according to the C
15 matches
Mail list logo
