[Automotive] Automotive Digest, Vol 16, Issue 3

Sanchez, Jack jsanche1 at jaguarlandrover.com
Thu Sep 15 00:47:19 CEST 2016


Hi Dominik,

Regarding the QtIVI behavior.

I've been busy and didn't get a chance to send out here that I'd figured
out my problem.

So currently, it seems, with QtIVI - the QIviServiceManager will *not*
register a given plugin as Simulation BackendType unless it is specifically
labeled with "_simulation"; "_simulator" does not work.
This isn't well documented that I had found and it wasn't until I had
familiarized myself with the guts of the QIviServiceManager and saw the
check in the private findServiceByInterface method that I found that answer.

So I have been able to achieve the expected/desired behavior simply by
having my plugin libs targeted as "lib_coollib_simulation" and any other
name will be registered as a Production BackendType.

Thanks for the response though!

I do have another question for the folks out here!

I've been trying to run GammaRay against our HMI system running appman.
Worked my way around a few basic issues but now I find that appman
segfaults when I launch with GammaRay under the different configuration
options. The meta-boot2qt layer and Automotive Suite docs/release notes
suggest this should be very obvious to do, but I suspect I'm missing
another nuance with a config either on appman or the gammaray binaries.

Thanks again!

Best Regards,

-- 
*Jack Sanchez*
Lead Qt Engineer

*M:* +1 503-608-8282
*E: jsanche1 at jaguarlandrover.com <jsanche1 at jaguarlandrover.com>*



*Jaguar Land Rover, 1419 NW 14th Ave, Portland, Oregon, 97209, USA*
*jaguar.com <http://jaguar.com/>  |  landrover.com <http://landrover.com/>*

Business Details:
Jaguar Land Rover Limited, Abbey Road, Whitley, Coventry CV3 4LF, UK
Registered in England Number: 1672070

This e-mail and any attachments contain confidential information for a
specific individual and purpose.  The information is private and privileged
and intended solely for the use of the individual to whom it is addressed.
If you are not the intended recipient, please e-mail us immediately.  We
apologize for any inconvenience caused but you are hereby notified that any
disclosure, copying or distribution or the taking of any action in reliance
on the information contained herein is strictly prohibited.

This e-mail does not constitute an order for goods or services unless
accompanied by an official purchase order.

On 14 September 2016 at 15:18, <automotive-request at qt-project.org> wrote:

> Send Automotive mailing list submissions to
>         automotive at qt-project.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.qt-project.org/mailman/listinfo/automotive
> or, via email, send a message with subject or body 'help' to
>         automotive-request at qt-project.org
>
> You can reach the person managing the list at
>         automotive-owner at qt-project.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Automotive digest..."
>
>
> Today's Topics:
>
>    1. QtIVI BackendType Switch/Registration (Sanchez, Jack)
>    2. Re: QtIVI BackendType Switch/Registration (Dominik Holland)
>    3. Qt Automotive Suite & Ubuntu (Jereme Lamothe)
>    4. please add me in the mail list ( Larry )
>    5. What is the proper process for building for release with
>       appman (Aras Balali Moghaddam)
>    6. appman IPC communication from System UI to app? (Eiche, Aaron)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 5 Sep 2016 13:39:28 -0700
> From: "Sanchez, Jack" <jsanche1 at jaguarlandrover.com>
> To: automotive at qt-project.org
> Subject: [Automotive] QtIVI BackendType Switch/Registration
> Message-ID:
>         <CAFWB3cR57PRPBp7z04E2W_cTdbnBwFtu16GGrB+3HSwzhG5jmQ@
> mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all,
>
> Working with the Qt Automotive Suite, running QtApplicationManager and
> using QtIVI.
>
> I'm currently working to implement the structure for switching the backends
> and I was curious if anyone had actually tried to do this yet.
>
> The documentation on this is very light and the behavior I'm experiencing
> feels counter intuitive.
>
> It seems that the "Simulator Plugin" in the QtIvi repository (and any
> installed service interfaces) is being registered as a Production backend
> by default and there seems to be no obvious way to tell the dynamic loader
> to switch to Simulation Backend type.
>
> The system seems to be setup such that I shouldn't need to manually operate
> the QIviServiceManager, however, as I'm investigating this backend
> switching functionality, it seems that I will have to in order to get the
> behavior I want.
>
> I feel like, in this example in QtIvi of the vehiclefunction_simulator
> plugin, I should be able to declare the object is a SimulationBackend.
>
> It would be great to hear if I'm missing something obvious, but either way
> I appreciate any feedback.
>
> Thanks!
> Best Regards,
>
> --
> *Jack Sanchez*
> Lead Qt Engineer
> *E: jsanche1 at jaguarlandrover.com <jsanche1 at jaguarlandrover.com>*
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.qt-project.org/pipermail/automotive/
> attachments/20160905/2d3ffda9/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 5 Sep 2016 23:08:44 +0200
> From: Dominik Holland <dominik.holland at pelagicore.com>
> To: automotive at qt-project.org
> Subject: Re: [Automotive] QtIVI BackendType Switch/Registration
> Message-ID: <e478f868-163c-6319-ca61-29d9d527526c at pelagicore.com>
> Content-Type: text/plain; charset=windows-1252
>
> Hi Jack,
>
> Am 05.09.16 um 22:39 schrieb Sanchez, Jack:
> > Hi all,
> >
> > Working with the Qt Automotive Suite, running QtApplicationManager and
> > using QtIVI.
> >
> > I'm currently working to implement the structure for switching the
> > backends and I was curious if anyone had actually tried to do this yet.
> >
> > The documentation on this is very light and the behavior I'm
> > experiencing feels counter intuitive.
> >
> > It seems that the "Simulator Plugin" in the QtIvi repository (and any
> > installed service interfaces) is being registered as a Production
> > backend by default and there seems to be no obvious way to tell the
> > dynamic loader to switch to Simulation Backend type.
>
> The current detection on whether a backend is a production backend or a
> simulation backend is done based on the file name. Once the backend
> contains the terms "_simulation" or "_simulator" it is currently
> detected as a simulation backend.
>
> Note there might be an issue in previous qtivi versions on this, which
> got fixed with this commit: 04cecf0f37af28b4b64e9575ca5ba9c6cfd26ea3
>
> >
> > The system seems to be setup such that I shouldn't need to manually
> > operate the QIviServiceManager, however, as I'm investigating this
> > backend switching functionality, it seems that I will have to in order
> > to get the behavior I want.
>
> That could well be without exactly knowing the behavior you want ;-)
>
> The best would be, if you could describe what you would expect, or what
> you want to achieve, so we either know about a feature-gap or what to
> improve in the documentation
>
> >
> > I feel like, in this example in QtIvi of the vehiclefunction_simulator
> > plugin, I should be able to declare the object is a SimulationBackend.
> >
> > It would be great to hear if I'm missing something obvious, but either
> > way I appreciate any feedback.
> >
> > Thanks!
> > Best Regards,
> >
> > --
> > *Jack Sanchez*
> > Lead Qt Engineer
> > *E: jsanche1 at jaguarlandrover.com <mailto:jsanche1 at jaguarlandrover.com>*
> >
>
> Best Regards
>  Dominik
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 09 Sep 2016 21:07:43 +0000
> From: Jereme Lamothe <jlamothe at docboxinc.com>
> To: "automotive at qt-project.org" <automotive at qt-project.org>
> Subject: [Automotive] Qt Automotive Suite & Ubuntu
> Message-ID:
>         <CA+dXhH-QHAwzbt4LBK3dsQ4UD5rfr_jph1HbZ4CdBm0sxt_eBg at mail.
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I got side tracked by other work, but wanted to write back to say I've
> successfully compiled / run both the Qt application manager and the neptune
> ui on Ubuntu Server 14.04. I noticed that a recent change relaxed the dbus
> requirements, thank you for that. After compiling + installing Wayland
> 1.10, Wayland protocols, and libyaml, I was able to build the Qt Wayland
> Compositor w/ Qt 5.7. Please note that this requires the latest hardware
> enablement stack to be installed (which satisfies an open gl version
> requirement).
>
> The compositor, and by extension the application manager, appears happy to
> run with an X11 back end ("startx /etc/X11/Xsession" and execute a script
> to run the neptune ui). I suspect the more typical use case w/ embedded
> hardware / a boot2qt image would have driver support to just run Wayland.
> I'm
> curious if anyone else has run the app manager in this manner (X11
> backend)? Are there any known issues or technical concerns proceeding in
> this direction if the intent is to deploy on a full-sized Linux distro such
> as Ubuntu?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.qt-project.org/pipermail/automotive/
> attachments/20160909/ef6bca5a/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 12 Sep 2016 13:24:22 +0800
> From: " Larry " <754833745 at qq.com>
> To: " automotive " <automotive at qt-project.org>
> Subject: [Automotive] please add me in the mail list
> Message-ID: <tencent_39E581C2440060D533EB65BF at qq.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> please add me in the mail list
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.qt-project.org/pipermail/automotive/
> attachments/20160912/7a32ecb5/attachment-0001.html>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 12 Sep 2016 15:31:34 -0700
> From: Aras Balali Moghaddam <arasbm at gmail.com>
> To: Qt Automotive List <automotive at qt-project.org>
> Subject: [Automotive] What is the proper process for building for
>         release with appman
> Message-ID:
>         <CACEPNZSnvC+K_HNSjK2zrNX3GpKPmQa-CQF8KVvrPvvXuhzD-w at mail.gmail.
> com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi automotive and appman people,
>
> I am wondering what the proper procedure is for creating a release
> distribution of an app that I am building that uses application manager to
> run. I am confused with the documentation. Do I need to use application
> package <https://doc.qt.io/QtApplicationManager/installer.html>r? How does
> one package and install the apps that run with appman on production
> devices?
>
> Cheers,
> Aras
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.qt-project.org/pipermail/automotive/
> attachments/20160912/0d27fdf3/attachment-0001.html>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 14 Sep 2016 15:18:23 -0700
> From: "Eiche, Aaron" <aeiche at jaguarlandrover.com>
> To: automotive at qt-project.org
> Subject: [Automotive] appman IPC communication from System UI to app?
> Message-ID:
>         <CA+xUqAO+29rwHXTW7OZCj8SKw3cDgSB17jkNCF
> aU4OHejdd7ZQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Everyone,
>
> I've been trying to implement IPC via appman (
> http://doc.qt.io/QtApplicationManager/qml-qtapplicationmanager-
> applicationipcmanager.html)
> in one of our projects. I've managed to get communication going from one of
> our apps to our System UI, but I haven't been able to figure out how to
> implement the opposite direction. I would like to be able to make the
> System UI send information to an application.
>
> Am I missing something obvious here? Is there a practical reason why this
> isn't already implemented (some other method of accomplishing this) or it's
> a bad idea?
>
> thanks
> -Aaron E.
>
> --
> *Aaron Eiche*
> Javascript Developer
>
> *T:* +1.971.256.9731  |  *M: *+1.503.334.9164
>
>
>
> Jaguar Land Rover North America, LLC
> 1419 NW 14th Ave, Portland, OR 97209
> JaguarUSA.com <http://www.jaguarusa.com/index.html>  |  LandRoverUSA.com
> <http://www.landrover.com/us/en/lr/>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.qt-project.org/pipermail/automotive/
> attachments/20160914/135c706e/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Automotive mailing list
> Automotive at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/automotive
>
>
> ------------------------------
>
> End of Automotive Digest, Vol 16, Issue 3
> *****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/automotive/attachments/20160914/352e3187/attachment-0001.html>


More information about the Automotive mailing list