[Openal] Status of OpenAL 1.1 on OS X

[David Guthrie]

You can actually ship both with Frameworks, they have a versioning  
system built in. You can just switch a "Current" sym link to the one  
you want to build against.  That includes the header, the binary, and  
the associated resources.  Once the app is linked, the "install path"  
points to the one you linked against as an absolute path, so new  
versions can be added, but apps can always point to the version they  
want to use.  That's why I asked why this can't be done.  It's done  
for Java.

David

On Aug 17, 2006, at 5:09 AM, Sven Panne wrote:

>> -----Original Message-----
>> From: openal-bounces at opensource.creative.com
>> [mailto:openal-bounces at opensource.creative.com] On Behalf Of
>> David Guthrie
>> Sent: Mittwoch, 16. August 2006 22:57
>> To: openal at opensource.creative.com
>> Subject: Re: [Openal] Status of OpenAL 1.1 on OS X
>>
>> I don't understand why a never version just can't be added in
>> the existing framework.  The Current link would point to the
>> 1.1 version with NO alut symbols and the 1.0 would still be
>> there as version A so that older apps will still run.
>
> Good question. As I said: I don't know Mac OS X in detail, but I guess
> that exactly this should be possible. On e.g. Linux one can install
> several versions of the same library at the same time when the major
> version number differ (i.e. they have an incompatible API, which is
> exactly the case here).
>
> Another question is: What should be done about the headers? Again, the
> solution is easy: Just ship the new headers, because people want to  
> use
> the new stuff and legacy apps don't need the headers anyway (the old
> apps are already compiled).
>
> Cheers,
>    S.
>