From: "Denys Dmytriyenko" <denis@denix.org>
To: Sebastian <sebastian.krahl@lacon.de>
Cc: meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] Setting up Build-Environment for BeagleBone Black with meta-ti
Date: Thu, 22 Apr 2021 15:28:06 -0400 [thread overview]
Message-ID: <20210422192806.GV15937@denix.org> (raw)
In-Reply-To: <25213.1619098225434298363@lists.yoctoproject.org>
On Thu, Apr 22, 2021 at 06:30:25AM -0700, Sebastian wrote:
> After a second, clean run it now works for the MACHINE ?= "beaglebone".
>
> The first run was on master for meta-ti and poky. It seems to be necessary
> to know witch meta-ti version is related to witch poky version because
> yocto-3.2 is not telling anything about the year of creation.
OpenEmbedded and the Yocto Project use codenames to name releases. Everyone
knows what for example Dunfell means, but very few actually remember which
number it corresponds to, e.g. 3.1 in this case for Dunfell, which is LTS.
https://wiki.yoctoproject.org/wiki/Releases
So, when you say yocto-3.2, I actually have to look it up in the list above
to figure out which release or branch it corresponds to, before saying that
meta-ti has no official support for Gatesgarth.
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
next prev parent reply other threads:[~2021-04-22 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 8:46 Setting up Build-Environment for BeagleBone Black with meta-ti Sebastian
2021-04-22 13:30 ` Sebastian
2021-04-22 19:28 ` Denys Dmytriyenko [this message]
2021-04-23 12:49 ` Sebastian
2021-04-23 17:16 ` Sebastian
2021-04-22 19:22 ` [meta-ti] " Denys Dmytriyenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210422192806.GV15937@denix.org \
--to=denis@denix.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=sebastian.krahl@lacon.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.