On Sat, 8 Feb 2020, rpjday@... wrote: ... snip ... > which seems odd as there don't appear to be any other recipes that > provide pkgconfig, and AIUI, the default provider for any recipe is

(part of the nitpickiness of some of these questions stems from that, in my updated courseware, i want to use actual examples out of, say, the openembedded layer, and not just contrived examples invol

On Sat, 8 Feb 2020, Jonatan Palsson wrote: .... snip ... > See the bottom example here: > https://www.yoctoproject.org/docs/3.1/bitbake-user-manual/bitbake-user-manual.html#variable-interaction-worked

argh ... that is, of course, what i should have done first, just check the environment for the recipe. ok, that pretty much confirms that, barring some exceptional circumstances, most instances of "PR

if that's true, then i've misunderstood it all this time. i guess i could always RTFS. rday

(currently updating my OE/YP courseware, so the first in a number of admittedly pedantic questions about simple stuff, just to make absolutely sure i understand things if i'm going to be explaining it

... snip ... Well, this is horrible news ... I got to know Scott from earlier days of poring over the docs and submitting patches. I'm not sure how documentation maintenance is now going to work but,

as one more followup to this, first, i was asked by a colleague about the possibility of generating an "SPDX notice file," and as i don't know what the format of one of those things is, it's hard for

yeah, that the impression i got ... is there a newer alternative to that, or just the standard license info that's been generated all this time? rday

a lilttle more progress, and then an error -- i installed fossology on my ubuntu 18.04 dev box, then added INHERIT += "spdx" to local.conf, and tried to build a simple qemuarmx86-64, and very quickly

i asked about this a couple months ago but didn't see any replies, so i'll ask again with a little more detail. colleague wants to, from YP (actually petalinux but should be irrelevant), some sort of

don't get me wrong, i have no problem with that, but a colleague asked me what the reason was for using sysvinit as the *default*. i hemmed and hawed and suggested it was for simplicity and reliabilit

colleague just asked how to generate an SPDX license "notice file" (whatever that is) from a build for a zynq ultrascale+ board, which shouldn't be hard other than that: 1) it's not pure YP, it's peta

yeah, i'm pretty sure you want MACHINEOVERRIDES: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-MACHINEOVERRIDES which has a nice example of how to invent a new "machine" cate

i know i did this once upon a time using the MACHINEOVERRIDES variable to "insert" a machine family into the sequence of machine definitions. as long as there is (i believe) a strictly hierarchical gr

that patch is already in thud branch of poky i'm using ... yes, that seems to have solved things for now: INHERIT_remove = "uninative" moving on to the next head-scratcher ... rday

the more i think about it, the more i'm nervous about the phrase "container layer", as it suggests a "layer" of some kind in the context of OE. the one distinction i think worth making is that a "BSP

as a followup, i would think that "meta-openembedded" is the canonical example of a container layer, no? rday

much snipping ... uh, i'm looking at meta-virtualization right now: https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/ and that looks like a regular BSP layer, not a container layer.

... snip ... ... snip ... just to summarize, if one wanted to (perhaps injudiciously) take advantage of host tools, that requires: 1) ASSUME_PROVIDED to specify the native package that no longer needs