Howdy!
Robert P. J. Day schrieb am So., 5. Juli 2020,
23:27:
>
> Quoting Richard Purdie :
>
> > On Sun, 2020-07-05 at 15:24 -0400, Robert P. J. Day wrote:
> >> Quoting Ross Burton :
> >>
> >> > On Sun, 5 Jul 2020 at 11:50, Robert P. J. Day
> >> wrote:
> >> > >however, one can also generate
Quoting Richard Purdie :
On Sun, 2020-07-05 at 15:24 -0400, Robert P. J. Day wrote:
Quoting Ross Burton :
> On Sun, 5 Jul 2020 at 11:50, Robert P. J. Day
wrote:
> >however, one can also generate a standard SDK with the generic
> > (image-independent):
> >
> >$ bitbake
Hi
My comments are in-line
On 05/07/2020 22:24, Robert P. J. Day wrote:
i'd assumed as much, but is there a reason that the meta-toolchain
target
is not mentioned at all in the SDK manual? Would that not be the right
place to mention it, even briefly?
I guess it depends on the
On Sun, 2020-07-05 at 15:24 -0400, Robert P. J. Day wrote:
> Quoting Ross Burton :
>
> > On Sun, 5 Jul 2020 at 11:50, Robert P. J. Day wrote:
> > >however, one can also generate a standard SDK with the generic
> > > (image-independent):
> > >
> > >$ bitbake meta-toolchain
> > >
> > >
Quoting Ross Burton :
On Sun, 5 Jul 2020 at 11:50, Robert P. J. Day wrote:
however, one can also generate a standard SDK with the generic
(image-independent):
$ bitbake meta-toolchain
which clearly does not identify an image (all that recipe does,
really, is "inherit populate_sdk"),
On Sun, 5 Jul 2020 at 11:50, Robert P. J. Day wrote:
>however, one can also generate a standard SDK with the generic
> (image-independent):
>
>$ bitbake meta-toolchain
>
> which clearly does not identify an image (all that recipe does,
> really, is "inherit populate_sdk"), so i *guessed*
colleague asked what should have been an easy question, but as i've
never spent a lot of time digging into the intricacies of generating
SDKs (i guess i will now), i didn't have an immediate answer.
current SDK manual in section 3 regarding standard SDKs states
that, "The Standard SDK
