[agl-discussions] Referring AGL version

Takashi Matsuzawa tmatsuzawa at xevo.com
Tue Jan 24 13:04:01 UTC 2017


Thank you.

In fact DISTRO_xxxx variables may be changed for my customized one, but seeem like adding the original AGL DISTRO_XXX keys to OVERRIDES may work.

(And since it comes from the original DISTRO_CODENAME, could be a convention that can be shared among the recipes.)

________________________________
From: Jan-Simon Möller <dl9pf at gmx.de>
Sent: Tuesday, January 24, 2017 7:46 PM
To: automotive-discussions at lists.linuxfoundation.org
Cc: Takashi Matsuzawa
Subject: Re: [agl-discussions] Referring AGL version

Am Dienstag, 24. Januar 2017, 05:25:42 schrieb Takashi Matsuzawa:
> Hello AGL.
>
>
> I have several add-on recipes to be build with AGL BSP, and such add-ons are
> also used with other non-AGL recipes.
>
> And I want to use the same recipes with multiple versions (e.g. 2.0, 3.0,
> etc.) of AGL BSP.
>
>
> Then, what is the best way to test to know the AGL version within my add-on
> recipes?
>
>
> Of course examinig DISTRO_FEATURES, etc. to make conditional statements in
> my recipe could be one way, but alternatively, I want to say, s.t. "if this
> AGL 3.0, enable this option", etc.
>
>
> I could add my own OVERRIDES key in my local.conf, but if there already is a
> recommended way to judge, I want to know.

Check
 bitbake -e | grep ^DISTRO_

DISTRO_VERSION
DISTRO_CODENAME

and
 bitbake -e | grep ^OVERRIDES


So a few ideas:
SRC_URI_append_poky-agl   # agl's value for DISTRO
SRC_URI_append_blowfish   # DISTRO_CODENAME  (check or add to OVERRIDES)
SRC_URI_append_chinook    # DISTRO_CODENAME  (check or add to OVERRIDES)

The specific codenames plus version are not that easy but you could calculate
it in a python statement and set a flag or use OVERRIDES as you proposed.

--
--
Jan-Simon Möller
dl9pf at gmx.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/automotive-discussions/attachments/20170124/a526e257/attachment.html>


More information about the automotive-discussions mailing list