Re: 32bit vs 64bit and QuickTime/AVFoundation
Re: 32bit vs 64bit and QuickTime/AVFoundation
- Subject: Re: 32bit vs 64bit and QuickTime/AVFoundation
- From: João Varela <email@hidden>
- Date: Tue, 10 Sep 2013 16:07:51 +0100
- Thread-topic: 32bit vs 64bit and QuickTime/AVFoundation
I second what Mark said. I did exactly as he suggested. To move to 64-bit
I isolated all QuickTime dependent code in a 32-bit only helper. The main
app, the other helpers and a private framework are now fat binaries and I
migrated all the media code to AVFoundation and related APIs. The 32-bit
only helper is only used to handle legacy media that AVFoundation cannot
handle.
For reasons we cannot discuss publicly in this list there is help on our
way that will allow us to get rid of this 32-bit only dependence for good.
So do follow what Mark suggested. It is how I did. And if you check how
Finder works with legacy media, you will notice that Apple itself followed
the same strategy.
HTH
Joao
>
>To me, this seems like the wrong direction to move. This is sort of like
>saying you want to convert your OS X app to a Classic Mac OS app maintain
>support for some Mac OS API.
>
>I'd go 64-bit only for your main app. I'd leave the 32-bit helper
>separate.
>Isolate your dependence on this component. If you're lucky, it will become
>obsolete and you'll be able to replace it without affecting your app
>significantly. Setup an API layer in your 64-bit app that calls
>AVFoundation, but can optionally call out to your 32-bit helper app.
>
>As a general rule, I try to write more for the future and less for the
>past. That means moving to 64-bit apps as quickly as possible.
>My guess, 32-bit frameworks will go away in the not too distant future,
>see: 68K code & PPC code, Carbon APIs, etc.
>
>Mark
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden