Re: Quesa patch for partial 64 bit support on Mac OS X

[Roger H. <rog...@mi...>]

On 15 Aug, 2008, at 21:04, Sean McBride wrote:

> Hi all,
>
> So we've just downloaded Quesa CVS and tried to build it as 64  
> bit.  Not
> sure if we're the first to try...

Yes I think you are. I have thought about it and concluded it was  
doable but I didn't have the time to do it then.

> it doesn't compile.  :)

You thought it would? :-)

>
> Attached is a patch that fixes almost all compilation issues.  Could
> someone review it?

I know our tech support guy generates patch files so that users can  
update our products with minimal download time. I'll ask him to see  
if we can use your file with out program.
>

> Most changes are pretty straightforward.  Some comments:
>
> a) QUESA_SUPPORT_QUICKTIME is forced to 0 in 64 bit.
>
> b) Added a QUESA_SUPPORT_QUICKDRAW that is analogous to
> QUESA_SUPPORT_QUICKTIME.  It must be 0 in 64 bit since QuickDraw/
> HIToolbox is gone.  Changed some QUESA_OS_MACINTOSH to
> QUESA_SUPPORT_QUICKDRAW.

Is all the QuickDraw usage in the viewer code? If so, I'm not  
currently using it either.

>
> c) Removed FSSpec usage in 64 bit.

Not replaced? Have you disabled file I/O temporarily?

>
> d) various casts, tweaks, etc.
>
> Note that I have only compiled this on Mac OS X, no other platforms.

Personally that's all I want anyway. It could be that with the other  
platforms, 64 bit is not such an issue.

>
> Note that even with this patch, there are still compiler errors in 64
> bit (but not in 32 bit).  The remaining errors I am not comfortable
> fixing because it requires a better knowledge of Quesa than I have.  I
> thought I'd start with this patch before discussing remaining  
> problems....

Oh, I see.

>
> Lastly, I realise that removing the QuickDraw/HIToolbox usage in Quesa
> means that it will be missing major functionality.

It's a fair chunk of code, but I think it was all platform dependant.  
Maybe we need a new platform in Quesa for Mac OS-X 64 bit. It could  
use Cocoa and Objective C++ for the user interface.

> In our case however,
> we only need a small subset of Quesa and are happy to report that that
> subset runs just fine in x86_64!

Please explain how you get around the compiler errors in 64 bit mode.

There is another future problem to be addressed one day. It fine  
having 64 bit code, but the Quesa file structure uses 32 bit offsets,  
in fact everything including booleans are 32 bits. I am very happy to  
stay with 32 bit floating point values internally but I wonder if we  
should define a new file type, maybe .Q64 or .3DMF64 is Windoze  
allows more than 3 characters now. In the new file type everything  
would be 64 bits, even the floating point values, which would get  
converted to 32 bit floats when the file was read, until such time as  
64 bit floating point gets (almost) as quick as 32 bit. I suppose  
someone is now going to tell me it is already, well I have not  
checked the specs, I'm just assuming and if I'm wrong then thats  
great and I can go and change the another product's source code.

Well done Sean for being the first of us to put his head above the  
64bit parapet.

Roger

>
> Cheers,
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng                 se...@ro...
> Rogue Research                        www.rogue-research.com
> Mac Software Developer              Montréal, Québec,  
> Canada<quesa_64.patch>------------------------------------------------ 
> -------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/ 
> _______________________________________________
> Quesa-develop mailing list
> Que...@li...
> https://lists.sourceforge.net/lists/listinfo/quesa-develop