Integration/Packaging of navigation, poi and mapviewer app needs to be redone
Description
Environment
blocks
is blocked by
relates to
Activity

Jose Bollo September 12, 2017 at 1:16 PM
considered as closed but moved to

Naoto YAMAGUCHI August 22, 2017 at 12:31 AM
10537 was rewritten as 10617.
It's marged.
Walt Miner August 21, 2017 at 3:45 PM
10537 abandoned. Now what?

Jose Bollo August 10, 2017 at 8:18 AM
in wait of review 10537

Jan-Simon Moeller August 8, 2017 at 8:02 AM
Hi and !
Thank for the explanation @ . Yes, we need to work-out what needs to end-up in the platform or not. This is will always be a 'WIP' item. We should facilitate a way to include libraries in the wgt. Worst-case this would be multiple.
The recipe should not have to specify any RDEPENDS. Either the wgt ships all necessary files for the app or the image / the packagegroup needs to pull-in the library as a platform library. This will break in the SDK if we do not enforce this.
The profiles will determine what libraries are in the mix. Everything on-top needs to be shipped with the app. Otherwise we must start a process to embed the library in question in the platform.
The recipe should in the end look like:
Details
Details
Assignee

Reporter

The current setup of
navigation,
poi,
mapviewer
is a mix of native library, native binary and application wgt
built using a single recipe.
This does not work with the SDK and needs to be redone.
, : please give us some hints how to untangle these
: please rework the package based on these suggestions