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
I have a helper tool that needs to use both C-based QuickTime/QTKit as well
as AV Foundation to process things for the main app.
Currently I am actually using two helper tools - one 32bit app to work with
QuickTime (since some of the old API will not work in 64bit), and a second
32/64bit app to w
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
>
> On 09/09/2013, at 9:56 PM, Trygve Inda wrote:
>
>> am considering merging them into one app, but it would have to be 32bit
>> only (though of course it will run on 64bit systems).
>>
>> Is there any real drawback to this? I'd like to support 10.6 - 10.9 and I
>> know that if I merge them i
On 09/09/2013, at 9:56 PM, Trygve Inda wrote:
> am considering merging them into one app, but it would have to be 32bit
> only (though of course it will run on 64bit systems).
>
> Is there any real drawback to this? I'd like to support 10.6 - 10.9 and I
> know that if I merge them into one app
