Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Migrate 4A from DYNAPI to APIv3 model

Fixed

Description

Current 4A bindings use the dynapi mechanism introduced in appfw binder after EE to create APIs and audio controls/streams dynamically.

At the same time, for FF, the binder now exposes APIv3 which has the same functionnlities than Dynapi, but not the same semantics.

The 4A stack has been integrated quite directly from EE to FF.rc1, without any change on dynapi calls. So as a workaround for FF.rc1, we introduced the option -DINCLUDE_LEGACY_BINDING_VDYN=ON in the binder recipe. But that should disappear.

Environment

FF.rc1, 4A layer enabled

Activity

Show:

Walt Miner 
December 7, 2018 at 11:53 PM

Close for GG RC2

Walt Miner 
November 1, 2018 at 1:18 AM

Does this need to be cherry picked to flounder?

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Affects versions

Priority

Created June 29, 2018 at 7:53 PM
Updated December 7, 2018 at 11:53 PM
Resolved October 30, 2018 at 3:54 PM

Flag notifications