...@yoctoproject.org [mailto:yocto-
>> boun...@yoctoproject.org] On Behalf Of Eystein Måløy Stenberg
>> Sent: Tuesday, November 10, 2015 8:29 PM
>> To: Khem Raj
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] Run-time discovery of machine for image compatibility
>> c
rg [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Eystein Måløy Stenberg
> Sent: Tuesday, November 10, 2015 8:29 PM
> To: Khem Raj
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Run-time discovery of machine for image compatibility
> check
>
> Thanks to everyon
Thanks to everyone on the input on this issue. I eventually solved it by
using an image feature called "buildinfo".
In case someone come across a similar need in the future I've created
these two blog post to advertise buildinfo it a bit more and show how to
use it:
* https://www.mender.io/blog/b
> On Sep 30, 2015, at 2:31 PM, Eystein Måløy Stenberg wrote:
>
> Hi,
>
> Before starting a bitbake build, we input the MACHINE variable in
> local.conf (e.g. MACHINE ?= beaglebone).
>
> Is there a way to detect this variable at run-time? I.e. if I have built
> the image, written it to a device
Hi in my case I have a machine for each board and I choose the right
device-tree at "machine".conf. So MACHINE can be determined by the device
tree Im running.
Other option would be echoing the machine to /etc/issue of the image. I do
this with DISTRO_VERSION. You can use ROOTFS_POSTPROCESS_COMMA
Hi,
Before starting a bitbake build, we input the MACHINE variable in
local.conf (e.g. MACHINE ?= beaglebone).
Is there a way to detect this variable at run-time? I.e. if I have built
the image, written it to a device, and I'm now logged in to it.
The reason I want this is that I'm working on a
