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 SPDX "notice file", along the lines of what
can be generated by black duck. it doesn't need t
On Fri, 22 Nov 2019, Robert P. J. Day wrote:
> 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 SPDX "notice file", along the lines of
On Sat, 23 Nov 2019, Richard Purdie wrote:
> On Fri, 2019-11-22 at 09:59 -0800, akuster808 wrote:
> >
> >
> > On 11/22/19 9:03 AM, rpj...@crashcourse.ca wrote:
> > > On Fri, 22 Nov 2019, Robert P. J. Day wrote:
> > >
> > >
> > >
On Sat, 23 Nov 2019, Richard Purdie wrote:
> On Fri, 2019-11-22 at 09:59 -0800, akuster808 wrote:
> >
> >
> > On 11/22/19 9:03 AM, rpj...@crashcourse.ca wrote:
> > > On Fri, 22 Nov 2019, Robert P. J. Day wrote:
> > >
> > >
> > >
On Fri, 31 Jan 2020, Richard Purdie wrote:
> I'm sorry to have to pass on the sad news that Scott Rifenbark, our
> tech writer for the project passed away on Wednesday after a battle
> with cancer.
... snip ...
Well, this is horrible news ... I got to know Scott from earlier days
of poring ov
(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
to others. if appropriate, i can submit patches to the official YP
docs if others think it's wo
On Sat, 8 Feb 2020, Leon Woestenberg wrote:
> Hello Robert,
>
> > i am *assuming* that, in the absence of a compelling reason, the use
> > of "+=" instead of "=" in this context is harmless, but unnecessary,
> > correct?
> >
> My understanding is that:
>
> > meta/recipes-support/libpcre/libpcre_
On Sat, 8 Feb 2020, Jonatan Palsson wrote:
> Hello Robert & Leon,
>
> > So I think it might be harmful to replace it with "=", as it would no
> > longer provide libpcre.
>
> I had a look at the variable expansions bitbake -e. Here are two
> examples. The vim recipe uses "PROVIDES = xxd" (which wou
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-examples
ironically, i am shortly going to ask a convoluted question about
this very thing --
(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 involving
packages like "foo" and "bar". to that end, i want to be able to
explain why some recipes a
On Sat, 8 Feb 2020, rpj...@crashcourse.ca 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
> the recipe with *exactly* the same name as the target -- in this case
moving on to the next nitpicky issue i want to clarify, and that's
*precisely* how overrides and appends are combined. i'm looking at
section 3.3 in the bitbake manual and i don't think the examples there
are as clear as they could be.
NOTE: in the YP docs, i would avoid examples that involve
On Mon, 10 Feb 2020, Richard Purdie wrote:
> On Sat, 2020-02-08 at 13:31 -0500, rpj...@crashcourse.ca wrote:
> >consider under recipes-devtools the two directories "pkgconfig"
> > and "pkgconf", and the respective .bb files:
> >
> > - pkgcon
On Mon, 10 Feb 2020, Richard Purdie wrote:
> On Sat, 2020-02-08 at 13:48 -0500, rpj...@crashcourse.ca wrote:
> > On Sat, 8 Feb 2020, rpj...@crashcourse.ca wrote:
> > ... snip ...
> > > which seems odd as there don't appear to be any other recipes that
> >
On Sat, 8 Feb 2020, Jonatan Palsson wrote:
> Hello Robert & Leon,
>
> > So I think it might be harmful to replace it with "=", as it would no
> > longer provide libpcre.
>
> I had a look at the variable expansions bitbake -e. Here are two
> examples. The vim recipe uses "PROVIDES = xxd" (which wou
Change the use of "+=" to the more proper "="; also, use a different
recipe example that actually exists in OE-Core at the moment.
Signed-off-by: Robert P. J. Day
---
diff --git a/documentation/ref-manual/ref-variables.xml
b/documentation/ref-manual/ref-variables.xml
index 02abc590c..c9b8c665
with the recent loss of scott rifenbark, since i used to be fairly
active in working on the docs, i figure it's time to get off my a**
and get involved again and contribute. to that end, i once made a
suggestion about being more precise about the docbook markup being
used in the YP manuals.
i
On Tue, 11 Feb 2020, Richard Purdie wrote:
> On Tue, 2020-02-11 at 05:32 -0500, rpj...@crashcourse.ca wrote:
> > second, i think we all agree that it is rarely necessary to use
> > "PROVIDES +=", although i did run across one case in
> > recipes-core/glib
On Tue, 11 Feb 2020, Ross Burton wrote:
> On Tue, 11 Feb 2020 at 11:13, rpj...@crashcourse.ca
> wrote:
> > first, yes, if something is a filename, then is the
> > obvious markup.
> >
> > on the other hand, variables should properly be marked up as
> > ,
On Tue, 11 Feb 2020, Ross Burton wrote:
> My problem with is that you need to keep on reviewing to
> verify it is the first usage. Better to post-process that, surely.
but that's not the way it's normally used ... doesn't
necessarily mean the physically first time a term is used, it's more
t
from the overview manual, section 2.5, "Reference Embedded
Distribution (Poky)", there is the note:
"While Poky is a "complete" distribution specification and is tested
and put through QA, you cannot use it as a product "out of the box" in
its current form."
sure, to be *generally* useful, you
Minor fixes:
- punctuation
- capitalization
- markup
- wording
Signed-off-by: Robert P. J. Day
---
diff --git
a/documentation/overview-manual/overview-manual-development-environment.xml
b/documentation/overview-manual/overview-manual-development-environment.xml
index 2f1bd1610..dd12
On Tue, 11 Feb 2020, Ross Burton wrote:
> Ah gotcha. My docbook-fu is somewhat hazy.
>
> Yes, seems sensible.
>
> Ross
>
> On Tue, 11 Feb 2020 at 14:43, Robert P. J. Day wrote:
> >
> > On Tue, 11 Feb 2020, Ross Burton wrote:
> >
> > > My problem with is that you need to keep on reviewing to
> >
Signed-off-by: Robert P. J. Day
---
diff --git a/documentation/overview-manual/overview-manual-concepts.xml
b/documentation/overview-manual/overview-manual-concepts.xml
index f085dd710..6ab783ce7 100644
--- a/documentation/overview-manual/overview-manual-concepts.xml
+++ b/documentation/overvi
Also removal of way too much unnecessary capitalization.
Signed-off-by: Robert P. J. Day
---
diff --git a/documentation/dev-manual/dev-manual-intro.xml
b/documentation/dev-manual/dev-manual-intro.xml
index 3a34094b8..5e231c6ac 100644
--- a/documentation/dev-manual/dev-manual-intro.xml
+++ b/do
in the YP dev manual, section 3.1.6, there is a maddeningly vague
note:
"It is possible for a recipe with a lower version number PV in a layer
that has a higher priority to take precedence."
so does it take precedence or not? just saying it's "possible"
doesn't clarify it for the reader.
rd
On Thu, 13 Feb 2020, Leon Woestenberg wrote:
> Hello Robert,
>
> On Thu, Feb 13, 2020 at 3:14 PM rpj...@crashcourse.ca
> wrote:
> > in the YP dev manual, section 3.1.6, there is a maddeningly vague
> > note:
> >
> > "It is possible for a recipe
Clarify that if there are multiple recipes with the same name, the
recipe with the highest PV from the highest priority layer will be the
one selected.
Signed-off-by: Robert P. J. Day
---
i'm using docbook's markup here, which renders in HTML as
both bold and italic.
diff --git a/documentat
again, some nitpickiness, but in the current YP dev manual, section
3.2.1, the manual is quite explicit about using "_append" with
IMAGE_INSTALL:
"Furthermore, you must use _append instead of the += operator if you
want to avoid ordering issues."
the way that's worded, that's not just a reco
On Thu, 13 Feb 2020, Jeremy A. Puhlman wrote:
> You are referring to section 5.2.1 if I am not correct, not 3.2.1?
no, section 3.2.1 in current git version of YP development tasks
manual. that manual doesn't even have a section 5. we better make sure
we're looking at the same manual.
> The con
On Thu, 13 Feb 2020, Jeremy A. Puhlman wrote:
> I was looking at th 1.6 version of the document, and the 5.2.1
> section is 3.2.1 in the 3.0 version. The section is about modifying
> images from the local.conf, so my comments are still the same. You
> need it to modify an image from the local.conf
just noticed in dev tasks manual in same paragraph i was whining
about earlier, section 3.1.6, Note:
"Also, the layer priority does not currently affect the precedence
order of .conf or .bbclass files. Future versions of BitBake might
address this."
um ... "currently"? wouldn't changing anyt
Signed-off-by: Robert P. J. Day
---
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml
b/documentation/dev-manual/dev-manual-common-tasks.xml
index 1e6addde4..d230ea90a 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-co
yes, yes, more obsessive-compulsive nitpickery, but YP dev tasks
manual, section 3.3.5, reads:
"Another way of specifying source is from an SCM. For Git
repositories, you must specify SRCREV and you should specify PV to
include the revision with SRCPV."
you *must* specify SRCREV? i don't thi
On Sat, 15 Feb 2020, Rudolf J Streif wrote:
> The wording might need improvement but both of your examples
> actually do provide SRC_REV but in the inline form with SRC_URI
> (rev/tag).
>
> The documentation should probably say something like SRC_REV needs
> to be provided but it can either be don
On Sat, 15 Feb 2020, Martin Jansa wrote:
> or not.. both were already
> fixedhttp://git.openembedded.org/meta-openembedded/commit/?id=2f6c043c0c99ccf71f9eb9088adbe42972b9d8a0
> http://git.openembedded.org/meta-openembedded/commit/?id=f61d9b3fd32dede5f2ab2aabbf0a8fb9fa75dd98
whoops, my fault, i
for wholly-unrelated reasons, i fell across devicetree.bbclass and
was inspired to check what inherited it, and noticed that nothing in
oe-core or meta-openembedded inherited it ... i had to dig around
through all the layers on my system until i found it inherited from
meta-xilinx, and nowhere e
On Sun, 16 Feb 2020, Peter Kjellerstedt wrote:
> We use tags in SRCREV for our own recipes since we have control over
> them and know that the tags won’t move. If one sets BB_SRCREV_POLICY
> = "cache", then bitbake will not do `git ls-remote` for the tags
> more than once. So as long as you have b
On Sun, 16 Feb 2020, Peter Kjellerstedt wrote:
> Wrong mailing list. Changes to (and discussions about) the
> documentation should go to d...@lists.yoctoproject.org since the end
> of January.
ah, i was unaware of that list, my apologies.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all mes
On Mon, 17 Feb 2020, Quentin Schulz wrote:
> Hi Philip,
>
> *Very* quick and vague answer as it's not something I'm doing right now.
> I can only give hints to where to look next.
>
> On Mon, Feb 17, 2020 at 04:27:17AM -0800, philip.le...@domino-uk.com wrote:
> > Hi,
> >
> > I'm looking for some a
i was just handed an issue that pops up under wind river linux 9
(effectively, "morty", YP 2.2), so i was hoping someone here might
have some thoughts.
there are a small number of ruby recipes that are part of this build
that, intermittently, choke during the install stage. one example is
som
Quoting Mikko Rapeli :
On Tue, Mar 10, 2020 at 11:37:55AM +, Richard Purdie wrote:
On Tue, 2020-03-10 at 11:33 +, mikko.rap...@bmw.de wrote:
> On Fri, Feb 28, 2020 at 11:25:59PM +, Richard Purdie wrote:
> > On Fri, 2020-02-28 at 22:51 +, Sean McKay wrote:
> > > This is probably
messing with docs some more, and just noticed that while all else
under poky uses the variable OEROOT, the toaster executable uses
OE_ROOT. works fine, of course, given that toaster is self-contained,
just wondering if there was a reason for the subtle renaming.
rday
--
=
i recall seeing (twitter?) that there are some yocto-related online
presentations associated with linaro connect, on march 24 and 25. is
there somewhere a full list of these things?
here's a complete schedule of talks for linaro tech days:
https://connect.linaro.org/linaro-tech-days/
where
On Thu, 26 Mar 2020, Matt Campbell wrote:
> HI All,
> We have a layer where we want to concurrently support two releases
> of Poky. There is an issue when we have bbappnds against recipes
> that have different versions in the two poky releases. for instance,
> imagine recipe foo that is version 1
looking at old YP project, wherein the ruby.bbclass class file for
working with ruby gems was in a now-removed meta-oe/meta-ruby classes
directory. AFAICT, these days, if you want to build ruby gems, the
only instance of ruby.bbclass i can see is in meta-cloud-services, is
that correct? or is th
46 matches
Mail list logo
