Re: (no subject)
Re: (no subject)
- Subject: Re: (no subject)
- From: William Stewart <email@hidden>
- Date: Tue, 13 May 2008 11:38:20 -0700
On May 13, 2008, at 7:51 AM, Shai Shasag wrote:
We're moving our development system to Leopard/Xcode3 and I'm not
sure what to do about our AU plugin.
The main difficulty seem to be the Core Audio SDK 1.5.
* Core Audio SDK is not part of the /Developer/SDKs/ hierarchy (Why
BTW?)
The OS SDKs are the headers and link binaries for the system
frameworks. The Core Audio Examples is source code that is licensed
for general use. The main difference to understand is that this is
source code, not API. How you use that example code is your concern.
This is why the code is to be found in /Developer/Examples...
On an historical note, we have been calling our releases the CoreAudio
SDK since 10.0 - the use of SDK to represent system headers was co-
opted by the developer tools team in Panther (10.3) - but these are
different things and should not be confused. We are more generally now
referring to the Core Audio example code in the developer tools as
well, the core audio example code. I don't have a good name for this.
* Core Audio SDK 1.5 is not available to download from Apple (http://developer.apple.com/audio/download/)(Why
BTW?)
It is distributed as source code with the developer tools
* Core Audio SDK 1.5 cannot be installed on Tiger (Actually it
cannot be installed on any system since there is no download)
That is because this example code requires Leopard headers and APIs.
* Core Audio SDK 1.5 has differences from version 1.4.4 that
require changes in our code. For example
AUCarbonViewBase::HandleEvent has another parameter added.
Yes - we will continue to modify this source code and provide
modifications with the development example code. You have two choices:
(1) Maintain your own copy of the code you are using to build your
audio units and apply diffs from our distributed code to yours
(2) Stay up to date with the revisions that we release.
The revisions that we release are the result of the changes this code
goes through as we continue to work on it, adding features, fixing
bugs, etc. The revisions that we release are also the same code that
we build our audio units on. So, our recommendation is to keep up to
date with our releases. We certainly try to minimise the impact that
these changes will have on existing code, but we will not guarantee
that this is going to require zero work from you.
* There is no way to tell which version of the Core Audio SDK is
currently being compiled, e.g. some #define to tell the version, so
we cannot write code that will compile under both SDKs
There should be no need to compile this code under that kind of
condition. In each release (and it is true for this one as well) we
describe how to build the current SDK so that it can run on previous
systems. So, this is achieved by setting the deployment target
appropriately (as Tahome described). This is also described in the
readme.
Our goal are:
1) AU plugin should compile on both Tiger(Xcode 2.4.1) and
Leopard(Xcode 3) using the same Xcode project.
We won't meet that goal. You will have work to do if you want to do
this.
2) The compiled plugin should run on both Tiger and Leopard - no
matter where it was compiled.
That is easily accomplished through the use of the Deployment target
as described in the read me or the CA Examples.
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
| References: | |
| | >(no subject) (From: Shai Shasag <email@hidden>) |