I like:
https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/classes/image-buildinfo.bbclass
Philip
On 04/12/2018 08:47 AM, Burton, Ross wrote:
> I think the message here is that we need to embed the oe-core version
> in the metadata somewhere...
>
> On 12 April 2018 at 13:11, Richard Collins
Hello Ross,
I have a different idea for poky versioning. Since, who ever does classical
poky, one will have at least three layers there from your reference poky
distro:
---
Build Configuration: |
---
DISTRO = poky
DISTRO_VERSION = 2.4
-
Hello Richard,
some of us are also around on the list.
You should find all documentation on the product page. Specifically, the
git tag of the release is "2.2.1-phy3" which indicates that the release
bundles poky morty 2.2.1. In future we will also have LAYERSERIES_COMPAT
set.
If the documentati
Thanks for the help. :)
Yes they are Phytec boards. I have inherited the project from a 3rd party
and so in the mids of chasing up the support contacts and our account
details for their site. I'm sure you've all played the "Q) What are the
support / login details? A) I don't know, ask X, ask Y, as
On Thu, Apr 12, 2018 at 01:11:17PM +0100, Richard Collins wrote:
> I get the following for DISTRO.
>
> DISTRO= "yogurt"
> DISTRO_VERSION= "BSP-Yocto-RK3288-PD17.1.1"
>
For further reference by anyone who is reading this in the archive: the
supplier is Phytec, and the distro layer
On 04/12/2018 03:11 PM, Richard Collins wrote:
I get the following for DISTRO.
DISTRO = "yogurt"
DISTRO_VERSION = "BSP-Yocto-RK3288-PD17.1.1"
Can't find any reference to yogurt so I assume this is something the
supplier of our SOM's has done. Looking on their Wiki it seems to be
That is an excellent suggestion, yes.
Ross
On 12 April 2018 at 13:54, Martin Jansa wrote:
> Cannot LAYERSERIES_CORENAMES added in rocko be used for that?
>
> On Thu, Apr 12, 2018 at 2:47 PM, Burton, Ross wrote:
>>
>> I think the message here is that we need to embed the oe-core version
>> in th
Cannot LAYERSERIES_CORENAMES added in rocko be used for that?
On Thu, Apr 12, 2018 at 2:47 PM, Burton, Ross wrote:
> I think the message here is that we need to embed the oe-core version
> in the metadata somewhere...
>
> On 12 April 2018 at 13:11, Richard Collins
> wrote:
> > I get the followi
I think the message here is that we need to embed the oe-core version
in the metadata somewhere...
On 12 April 2018 at 13:11, Richard Collins
wrote:
> I get the following for DISTRO.
>
> DISTRO= "yogurt"
> DISTRO_VERSION= "BSP-Yocto-RK3288-PD17.1.1"
>
> Can't find any reference to
I get the following for DISTRO.
DISTRO= "yogurt"
DISTRO_VERSION= "BSP-Yocto-RK3288-PD17.1.1"
Can't find any reference to yogurt so I assume this is something the
supplier of our SOM's has done. Looking on their Wiki it seems to be based
on 2.1.2 (Krogoth)
Thanks for the help. :)
On 04/12/2018 12:44 PM, Richard Collins wrote:
I've inherited a Yocto project that I know to be an old version. So one
of my tasks is to update to the latest version. Before I do this I would
like to know what version I have. The only information I can find is the
bitbake version, BB_VERSION
If your project also includes meta-poky then poky.conf will contain a
DISTRO_VERSION assignment. However,
https://wiki.yoctoproject.org/wiki/Releases indicates that bitbake
1.32 was part of 2.2/morty.
Ross
On 12 April 2018 at 10:44, Richard Collins
wrote:
> I've inherited a Yocto project that I
I've inherited a Yocto project that I know to be an old version. So one of
my tasks is to update to the latest version. Before I do this I would like
to know what version I have. The only information I can find is the bitbake
version, BB_VERSION= "1.32.0".
Many thanks,
Richard.
--
___
13 matches
Mail list logo