• 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: Core Audio PowerPC Intel Notes.rtf
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Audio PowerPC Intel Notes.rtf


  • Subject: Re: Core Audio PowerPC Intel Notes.rtf
  • From: William Stewart <email@hidden>
  • Date: Mon, 15 Aug 2005 15:37:00 -0700


On 13/08/2005, at 6:05 AM, Marc Poirier wrote:

On Aug 12, 2005, at 2:40 PM, William Stewart wrote:


As to this read me - it shouldn't have included this comment because there really is nothing in this file, so we didn't include it in the SDK.


Ah okay, thanks for confirming.

rdar://4215631



The main change (and this is detailed in the SDK's Readme file is the following:

In your Project's settings you need to add the following to the OTHER_REZ_FLAGS:
-d ppc_$ppc -d i386_$i386


What this line does is then use the settings you make elsewhere in XCode (whether to build ppc/i386 or both) to also decide which version of the resource needs to be built for the AU.


Actually, this is not detailed in such a manner in the readme file. What it does say there is: "you will need to define ppc_YES and i386_YES variables in your AU Projects." The fact that you can just do "-d ppc_$ppc -d i386_$i386" is quite nice in my opinion (it means that you don't need to adjust the settings in 2 different places and keep them in sync every time you want to make a change), and would be worth mentioning in the readme, I think.


rdar://4215632


Good suggestions



We urge AU developers to move their AU development over to the 1.4.x SDK as it contains a number of fixes. An AU built with this SDK will still continue to work on both Jaguar and Panther systems.


Actually, it won't.

There's a couple of points to clarify here. My original statement was not taking these OS Target macros into account. The intention of this is that the AU SDK has *no* dependencies that would cause runtime or link errors on a pre 10.4 system (presuming it was built on a 10.4 system). That is still a true statement: you can compile an AU using our latest SDK and use it on 10.2 or 10.3 with no problem. There are no run-time dependencies in our AU Support classes beyond 10.2.


As has been pointed out with previous 1.4.x releases, they won't build with a 10.2.x SDK because of kControlStaticTextIsMultilineTag in AUCarbonViewControl.cpp

We just built the view targeting 10.2 or later and it builds fine. In fact the constant kControlStaticTextIsMultilineTag is defined in 10.1 (look at the comments in Carbon/ControlDefinitions.h). So, I'm confused by this statement as it is fine for us.


and the kAudioFormatAppleLossless stuff in CAStreamBasicDescription.cpp. These need to be pre-processed out with something like:
#if MAC_OS_X_VERSION_MAX_ALLOWED > MAC_OS_X_VERSION_10_2

The pple lossless constants were definitely not defined in 10.2, so I can imagine this is a problem. This is not something that we had qualified (or to be honest) even thought about as we don't use these ourselves when we are going back.


in order to build with a 10.2.x SDK, and building with a 10.2.x SDK is necessary for making an AU that will run in Jaguar.

No this is not true. All that these macros will really do is to give you a compile error if you are referring to something that was not implemented on a particular version of the OS. But if you "know" that you are not using newer API, then whether you use these macros or not, your code will run (or not!). There are of course a collection of headers that don't and will never use these macros (BSD for instance) that has substantial differences. Yes, its helpful, but its not necessary.


rdar://4215634

OK - so here's what we'll do. Going forward, we will make sure that the AU, AudioFile and AudioCodec components will build in our latest SDK with earlier OS releases targeted - we'll also indicate when/if there is any change in these areas to the base level OS requirements. This will STILL assume that you are building on Tiger (or later) of course. This will give you what you are want I think.


Thanks

Bill

--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __


_______________________________________________
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: Core Audio PowerPC Intel Notes.rtf
      • From: Marc Poirier <email@hidden>
References: 
 >Core Audio PowerPC Intel Notes.rtf (From: Marc Poirier <email@hidden>)
 >Re: Core Audio PowerPC Intel Notes.rtf (From: William Stewart <email@hidden>)
 >Re: Core Audio PowerPC Intel Notes.rtf (From: Marc Poirier <email@hidden>)

  • Prev by Date: AudioUnitInputCallback callback frequency
  • Next by Date: Re: AudioUnitInputCallback callback frequency
  • Previous by thread: Re: Core Audio PowerPC Intel Notes.rtf
  • Next by thread: Re: Core Audio PowerPC Intel Notes.rtf
  • Index(es):
    • Date
    • Thread