[Development] New Module Request: QtGeniviExtras

Robert Griebl robert.griebl at pelagicore.com
Wed Aug 12 14:26:26 CEST 2015

On 12.08.2015 13:32, Thiago Macieira wrote:
> On Wednesday 12 August 2015 09:55:14 Dominik Holland wrote:
>> Every Process which wants to log using DLT needs to provide information
>> about it's Application, this needs to be a 4 characters long unique
>> identifier and a Description for it.
> Sounds stupid...

Many industry standards sound stupid, but they still are standards after 
Heck - there are even people who think that some things inside Qt are 
stupid! The world is larger than Qt.

>> Every LoggingCategory (In DLT it's called Context) needs to have a 3
>> characters long unique identifier and a Description.
> Stupid API limitation. Can you convince GENIVI to get rid of the 3-character
> identifier requirement? It should be an arbitrarily-long string, in which case
> we can use the logging category itself.

Again - calling other APIs stupid does not help. And no - this is an 
industry standard which cannot easily change, because Qt has a different 
logging API. Besides: have you tried yet to get changes into Genivi 
components? Good luck with that -- we tried to fix a few much bigger 
problems upstream and it ended in uphill battles you don't want to fight.

> qt_hash(the category name) then base64url-encode the result and cut to 3
> characters.

And this will be (a) unique and (b) human readable in the DLT viewer? 
(yes even 3 characters can be human readable)

 > By the way, doesn't GENIVI require systemd and thus journald anyway?
 > Why do they have their own logging mechanism?

Did you read the part about the back-channel from the DLT-Viewer to the 
application. But that is besides the point: DLT is used in much more 
than just systemd based IVI systems:

"DLT is a reusable open source software component for standardized 
logging and tracing in infotainment ECUs based on the AUTOSAR 4.0 
standard. The goal of DLT is the consolidation of the existing variety 
of logging and tracing protocols on one format." 


Robert Griebl

Pelagicore AG

More information about the Development mailing list