Possible JACK ABI changes between 0.118 and 1.9.5

[Reinhard Tartler]

On Fri, Apr 09, 2010 at 13:00:14 (CEST), Adrian Knoth wrote:

> On Fri, Apr 09, 2010 at 08:25:43AM +0200, Reinhard Tartler wrote:
>
>> >     /*************************************************************
>> >      * NOTE: JACK_WEAK_EXPORT ***MUST*** be used on every function
>> >      * added to the JACK API after the 0.116.2 release.
>> >      * 
>> >      * Functions that predate this release are marked with 
>> >      * JACK_WEAK_OPTIONAL_EXPORT which can be defined at compile
>> >      * time in a variety of ways. The default definition is empty,
>> >      * so that these symbols get normal linkage. If you wish to
>> >      * use all JACK symbols with weak linkage, include 
>> >      * <jack/weakjack.h> before jack.h.
>> >      *************************************************************/
>> 
>> is there a rationale for this? I can guess some reasons, but certainity
>> would help.
>
> 12:22 < torbenh3> adi: it provides binary compatibility of an app built against 
>                   a higher version of jack against a 0.116.2 jack. 
> 12:24 < torbenh3> in other words. a session enabled program will not complain 
>                   if you downgrade to 0.116.2 .. (you just wont have session 
>                   support)

But applications using the session feature must then check at runtime if
the jack library is new enough, no?

Anyway, in debian we don't support downgrades anyway, so strictly
speaking, we don't need to follow this argument.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4