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: William Stewart <email@hidden>
- Date: Tue, 8 Sep 2009 17:38:26 -0700
I'll reply to this one.
On Sep 7, 2009, at 1:58 AM, Muon Software Ltd - Dave wrote:
Bill,
I just got around to trying to build one of the demo AUs (sinSynth)
against Core Audio SDK 1.5 (as deployed with XCode 3.1.3) and it
definately fails when the Base SDK and Deployment Target are both
set to 10.4. Changing the Base SDK to 10.5 and leaving Deployment
Target on 10.4 allows the build to succeed. Target architecture is
32-bit Universal in both cases.
This is correct. The SDK being left to "current" (which includes
moving over to the SL, 10.6 source) means that we don't have to
continually backport constants and other literals that are defined in
headers, but don't have linking ramifications. Audio units use
properties and as such they aren't really tied as closely to a given
OS release as you are when you use an actual API call.
The deployment target takes care of all kinds of linking issues (for
instance, there was a big change to C++ between 10.3.9 and 10.4.x)) so
you should set this to the lowest OS version you want to support.
If this isn't the desired behaviour I'm happy to file a bug.
We are examining the reports that the 10.6 sources do not build to a
deployment target of 10.4 - this should still work.
However, if I am understanding cross-development correctly (and
there's a good chance I am not!) then surely changing the Deployment
Target to 10.4 and leaving the Base SDK at 10.5 *should* give you an
AU that will work fine on Tiger, right? what would be the possible
disadvantages of doing things this way?
Yes. The only disadvantage is that you don't get compiler errors for
function calls that are not in 10.4. You just need to keep that in
mind (and there are ways around that). You can have a look at
CAAudioUnit.h - there's some "games" there that we play to use a new
API when it is available and so we hide that test behind a method call.
Bill
Kind regards
David Waugh
Managing Director
Muon Software Ltd
http://www.muon-software.com
http://muonsoftware.blogspot.com
-----Original Message-----
From: William Stewart [mailto:email@hidden]
Sent: Friday, September 04, 2009 12:15 AM
To: Muon Software Ltd - Dave
Cc: coreaudio-api API; Mehul Trivedi
Subject: Re: Building AudioUnits for Mac OS 10.4 on Snow Leopard
Well, we should look into this as it wasn't intended that this would
be broken.
Can someone please file a bug report - if one of the sample au's fail
in this way, then that would be good information to add.
Thanks
Bill
_______________________________________________
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
_______________________________________________
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