• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Moving our AU plugin to Leopard/Xcode3
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Moving our AU plugin to Leopard/Xcode3


  • Subject: Re: Moving our AU plugin to Leopard/Xcode3
  • From: Nick Dowell <email@hidden>
  • Date: Tue, 13 May 2008 16:00:15 +0100


On 13 May 2008, at 15:55, 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?)
* Core Audio SDK 1.5 is not available to download from Apple (http://
developer.apple.com/audio/download/)(Why BTW?)
* Core Audio SDK 1.5 cannot be installed on Tiger (Actually it cannot
be installed on any system since there is no download)
* 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.
* 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

I share your pain, as I'm sure most AU developers do.

The simplest solution I have found is to override both versions of AUCarbonViewBase::HandleEvent(), and then make one implementation call the other. Much easier and more robust than conditional compilation!

There are other virtual functions whose parameters have subtly changed, so watch out for them too!

Our goal are:
1) AU plugin should compile on both Tiger(Xcode 2.4.1) and Leopard
(Xcode 3) using the same Xcode project.
2) The compiled plugin should run on both Tiger and Leopard -  no
matter where it was compiled.

Are these goal feasible? Or should we just compile two version of the
plugin, one that will run on Tiger and be compiled on Tiger, and one
that will run on Leopard and will be compiled on Leopard?

Thanks for any help,


Shai Shasag Senior Software Engineer Waves Audio Ltd. Phone: +972-36084007; Fax: +972-36084056;

-----------------------------------------------------
Don’t Just Do Something, Stand There!


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40focusrite.com


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


  • Follow-Ups:
    • Re: Moving our AU plugin to Leopard/Xcode3
      • From: "tahome izwah" <email@hidden>
References: 
 >Moving our AU plugin to Leopard/Xcode3 (From: Shai Shasag <email@hidden>)

  • Prev by Date: Re: (no subject)
  • Next by Date: Re: Moving our AU plugin to Leopard/Xcode3
  • Previous by thread: Moving our AU plugin to Leopard/Xcode3
  • Next by thread: Re: Moving our AU plugin to Leopard/Xcode3
  • Index(es):
    • Date
    • Thread