RE: Building AudioUnits for Mac OS 10.4 on Snow Leopard
RE: Building AudioUnits for Mac OS 10.4 on Snow Leopard
- Subject: RE: Building AudioUnits for Mac OS 10.4 on Snow Leopard
- From: Muon Software Ltd - Dave <email@hidden>
- Date: Mon, 7 Sep 2009 10:42:33 +0100
- Acceptlanguage: en-US, en-GB
- Thread-topic: Building AudioUnits for Mac OS 10.4 on Snow Leopard
> That's the recommended way to do. The main disadvantage is that if you
> inadvertently call a method that is available on 10.5 only, the
> compiler will not warn you. Note that using 10.5 feature is perfectly
> valid even if you deploy on 10.4, as long as you check that the
> function exists before calling it:
>
> if (AFunctionAvailableOn105Only) {
> AFunctionAvailableOn105Only(args);
> } else {
> // 10.4 way to do this
> }
It seems to me that leaving the Base SDK on 10.4 is a much easier way to ensure that you only use relevant APIs even if its not the "recommended" way. Then the only thing you have to do is make sure that you use the version of the CoreAudio SDK that will actually compile against the Base SDK you are targetting, which isn't too hard to figure out once you look into it. That's where I'm at now.
The only downside I can see is that you could miss out on the differences between CoreAudioSDK 1.4.4 and 1.5. I've looked that the release notes and I can't see anything important that I'm missing, though I'm left wondering about some of the bug fixes. The ability to do 64-bit builds is irrelevent to me as I'm still on Carbon.
Does anyone have an opinion of the relative merits of moving from CoreAudioSDK 1.4.4 to CoreAudio SDK 1.5 (or whatever version ships with Snow Leopard, I'm *still* waiting for my copy Apple Store do you hear!)
Kind regards
David Waugh
Managing Director
Muon Software Ltd
http://www.muon-software.com
http://muonsoftware.blogspot.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden