Re: Building AU for pre 10.4 with Tiger
Re: Building AU for pre 10.4 with Tiger
- Subject: Re: Building AU for pre 10.4 with Tiger
- From: Marc Poirier <email@hidden>
- Date: Tue, 24 May 2005 16:26:06 -0400 (EDT)
I have found that it can be a little more complicated than this, though
not with anything specific to AUs and CoreAudio, the following is generic
to any C++ development using gcc.
One thing is noting the version of gcc that you are using. C++ code
produced by certain versions of gcc are only supported in certain versions
of the OS. I think that gcc 3.3 is only supported in 10.2 and above and
4.0 (the default in Tiger) is only supported in 10.3.9 and above. You
should double check that all, though, I'm totally just pulling that out
from (fuzzy) memory.
The other thing has to do with the the standard C++ library (libStd-C++ or
something like that). I posted something about this recently where I
found that my code built in 10.3 wouldn't load in 10.2. This was because
of statically linking against 10.3's version of that library which was
dynamically linked to some 10.3 system library with symbols that aren't in
the 10.2 version of that library, and so the code would fail to load. I
believe I read something from one of the Tiger seed notes or something
that, in Tiger with Xcode 2.0, you can now dynamically link to the
standard C++ library. But I haven't really looked into that yet. If you
can do that, and then choose gcc 3.3 as your compiler, then I think your
code should load in 10.2 or above. But maybe the C++ library dynamic
linking only loads in 10.4, I don't know. If that doesn't work, then what
you have to do is choose the 10.2 SDK in your project if you want your
code to load in 10.2 or higher, 10.3 SDK for 10.3 or higher, etc.
Marc
On Tue, 24 May 2005, William Stewart wrote:
Yes
Because AU's use the "dynamic typing" mechanism with properties, we can add
new functionality that doesn't have problems going backwards - the component
manager also does this generically in any case with the Component Selectors
We try to avoid adding dependencies in AUBase on API outside of the AU
generally
So, the only problem a developer should need to consider is the dependencies
their code is introducing - if you use an API that is only available on Tiger
for instance, then you should soft link this in..
Bill
On 21/05/2005, at 2:20 PM, Mark's Studio wrote:
Can i compile a AU with tiger that works on pre 10.4 if i don't use any new
features?
Peter Mark
_______________________________________________
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