Skip to:

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

Create a repository of lib navigation API.

Description

Currently, the navigation service API repository is one.
In this repository, libNaviAPIService.so and libnaviapi-agl.so are created.
We want to separate these.

The repository of libNaviAPIService.so was created as we asked for recently
https://gerrit.automotivelinux.org/gerrit/gitweb?p=apps%2Fagl-service-navigation.git;a=shortlog;h=refs%2Fheads%2Fmaster

The repository of libnaviapi-agl.so is also needed.

Environment

None

Activity

Jan-Simon Moeller 
August 27, 2018 at 3:09 PM

Created.

Yoshito Momiyama 
August 3, 2018 at 4:55 AM

Thank you for your idea.
I would like to do the following

Project name
libaglnavigation

Jan-Simon Moeller 
July 16, 2018 at 10:21 AM

Ok.  I'd propose to stick with  "agl-service-navigation" and similar    libaglnavigation or libnavigation-agl. Tnx.

 

Wei Chen 
July 6, 2018 at 1:30 PM

Currently, recipe agl-service-navigation means binding API and recipe libnaviapi-agl means client library for applications.

If there is a name policy, please tell me, thanks.

Jan-Simon Moeller 
July 6, 2018 at 1:05 PM

Ok, so we should keep the agl-service-navigation.

 

But I'm confused about the names. Which one is the agl-service-navigation now and what does the other library provide ?

 

Note: it makes sense to use the same names ... e.g. agl-service-navigation for the API and  e.g. libaglnavigation for a possible client library.

That way we stay consistent in naming across all APIs and help the user to understand what components we have.

 

Thank you.

Fixed

Details

Assignee

Reporter

Components

Priority

Parent

Created July 5, 2018 at 12:56 PM
Updated August 28, 2018 at 12:42 AM
Resolved August 27, 2018 at 3:09 PM

Flag notifications