[agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi)
stephen.lawrence at renesas.com
Tue Jun 14 12:27:23 EDT 2016
> -----Original Message-----
> From: automotive-discussions-bounces at lists.linuxfoundation.org
> [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On
> Behalf Of phongtran
> Sent: 14 June 2016 14:36
> To: automotive-discussions at lists.linuxfoundation.org
> Cc: genivi-projects at lists.genivi.org; automotive at qt-project.org
> Subject: [agl-discussions] Introduce Qt IVI layer (meta-qt5-ivi)
> Hi ALL,
> I would like to share the meta-qt5-ivi which provides qtapplicationmanager,
> qtivi and qt-apps-neptune-ui.
> The repo is on github here:
> I applied this layer to AGL distro and It can start up QEMU x86-64 KVM
> Ubuntu 14.04 host PC.
> Please refer README for detail:
> I uploaded the images here:
> I attached some screenshoots of Neptune UI.
> Please review and give your feedbacks.
Looks interesting. Thank you for sharing.
One question from reading the Readme. I see it does not use the existing meta-qt5 layer .
Whilst trying to avoid drawing you into politics could you summarise technically why your layer
has its own base Qt 5 parts? From a quick look the two layers seem to have a somewhat different focus
and you've provided recipes presumably for just what you need.
I am not thinking so much about a feature by feature comparison but the practicalities about
layer architecture and adoption. To give one example the Genivi Development Platform (GDP)
uses  for the base Qt 5 parts for its Qt based HMI. So if say someone wanted to adopt your work
into GDP the question arises as to how best to do that. Adopting your Qt5 layer instead for the base Qt5
raises questions of maintenance going forward and whether all requirements are met, whilst just adopting
the apps/HMI (I realise I am probably simplifying there) means masking out parts for it to work on .
More information about the genivi-projects