alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
goliath has joined #yocto
<qschulz>
~~o/
<qschulz>
o/
leon-anavi has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
ptsneves has joined #yocto
zhmylove has joined #yocto
zhmylove has quit [Ping timeout: 260 seconds]
zhmylove has joined #yocto
JaMa has quit [Ping timeout: 276 seconds]
mvlad has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
<kanavin>
abelloni, none please
<kanavin>
this needs additional investigation
<kanavin>
PhoenixMage, you name the recipe something else, e.g. u-boot-vendor, and then set virtual/bootloader to that I think
JaMa has joined #yocto
xmn has quit [Ping timeout: 250 seconds]
hardliner66 has joined #yocto
xmn has joined #yocto
<hardliner66>
Hi, does anybody know if it's possible to create a package that overrides values from another package? Reason being: I want to allow people to enable coredumpctl by installing a package so that they have more control whether they want it or not.
<hardliner66>
So basically, i want to do `PACKAGECONFIG_append_pn-systemd = " coredump"` inside a package, that also might set/install a few other things
<hardliner66>
or something similiar
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
<LetoThe2nd>
hardliner66: no, thats not possible.
<LetoThe2nd>
hardliner66: yocto chant #1: recipe data is local, configuration data is global. means: whatever you do in one recipe, others can't see it.
<LetoThe2nd>
hardliner66: use a custom distro, for example.
kanavin has quit [Remote host closed the connection]
<hardliner66>
hmm
<hardliner66>
so, I either just document it well for others to use or I "hack" it together with bbappends and variables or I just make it always on when using my custom layer with bbappends
<LetoThe2nd>
hardliner66: why not use a custom distro?
<LetoThe2nd>
put it into your layer, then people can switch it on by using it.
<hardliner66>
I'd have to read up on that, cause that's something I haven't done yet. I only made a layer and some packages
<hardliner66>
LetoThe2nd thanks man. gonna check it out. might simplify a lot of things i'm already doing
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<LetoThe2nd>
hardliner66: have fun
Payam has joined #yocto
kanavin has joined #yocto
d-s-e has quit [Quit: Client closed]
hardline1 has joined #yocto
hardliner66 has quit [Quit: hardliner66]
hardline1 has quit [Client Quit]
hardliner66 has joined #yocto
zpfvo has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
starblue has quit [Ping timeout: 276 seconds]
starblue has joined #yocto
MWelchUK has joined #yocto
Kris has joined #yocto
<mckoan>
michaelo: what about adding devtool in the main menu on the left of the YP doc ?
<mckoan>
michaelo: it's deeply hidden in the documents
Kris has quit [Remote host closed the connection]
Kris has joined #yocto
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
seninha has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
davidinux has quit [Ping timeout: 272 seconds]
xmn has quit [Quit: ZZZzzz…]
otavio has quit [Remote host closed the connection]
otavio has joined #yocto
xmn has joined #yocto
d-s-e has joined #yocto
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
xmn has quit [Quit: ZZZzzz…]
davidinux has joined #yocto
d-s-e has quit [Quit: Client closed]
prabhakarlad has quit [Quit: Client closed]
<qschulz>
@all congrats on the 4.1 release!
seninha has quit [Ping timeout: 250 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
hardliner66 has quit [Quit: WeeChat 3.7.1]
alessioigor has joined #yocto
<michaelo>
🥂
hardliner66 has joined #yocto
<michaelo>
mckoan: not so easy, as it would require creating a new toplevel document. The thing is it's referred to in multiple documents.
<mckoan>
michaelo: hmmm I see
<michaelo>
mckoan: a possibility may be to mention devtool in the titles of some of the subchapters refering to it. So, you would see "devtool" when you expand documents such as "Development Tasks Manual" -> "Common Tasks"
<rburton>
"We are pleased to announce the Yocto Project 4.1 Release is now available for download."
<rburton>
🎉
Schlumpf has quit [Quit: Client closed]
Payam has quit [Ping timeout: 244 seconds]
vmeson has quit [Quit: Konversation terminated!]
<JPEW>
\o/
<rburton>
to celebrate, the master CVE report has 17 _new_ CVEs
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
seninha has joined #yocto
davidinux has quit [Quit: WeeChat 3.5]
prabhakarlad has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
alessioigor has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
Schlumpf has joined #yocto
nemik has joined #yocto
<mckoan>
rburton: hurray \o/
<mckoan>
michaelo: may be helpful
pgowda_ has joined #yocto
dmoseley has quit [Ping timeout: 276 seconds]
<mrybczyn[m]>
Let's have a party then rburton !
dmoseley has joined #yocto
susanjessy[m] has quit [Quit: User was banned]
<tlwoerner>
PhoenixMage: yes, what kanavin said. create a new recipe called u-boot-rockchip whose SRC_URI points to the rockchip fork. then in your MACHINE file set PREFERRED_PROVIDER... to the new recipe
<landgraf>
party? who said party?
Starfoxxes has quit [Ping timeout: 252 seconds]
zpfvo has quit [Ping timeout: 255 seconds]
<mrybczyn[m]>
landgraf: cve fixing party. I know you love them
<landgraf>
mrybczyn[m]: my favorite party, yes
Starfoxxes has joined #yocto
Payam has joined #yocto
zpfvo has joined #yocto
vmeson has joined #yocto
frieder has quit [Ping timeout: 272 seconds]
zpfvo has quit [Ping timeout: 255 seconds]
zpfvo has joined #yocto
sakoman has joined #yocto
frieder has joined #yocto
rsalveti has joined #yocto
prabhakarlad has quit [Quit: Client closed]
rob_w has quit [Remote host closed the connection]
Guest13 has joined #yocto
Guest13 has quit [Client Quit]
Guest13 has joined #yocto
<Guest13>
hello everyone. im using the dunfell version with meta-raspberrypi, openembedded, poky and my meta. there are specific versions of libraries such as curl, libcryptopp, raspicam, opencv, libedgetpu, tensorflow in my meta. when i wanted to upgrade to the Kirkstone version, i saw that the specific versions i used were not supported. for example, i was
<Guest13>
using gcc 9.3, when i switched to gcc 11.3, the builds problem appeared for my meta. is this normal? should i continue from Dunfell?
<Guest13>
im new to yocto and i might make a mistake in general logic. i will be glad if you can explain.
prabhakarlad has joined #yocto
goliath has quit [Quit: SIGSEGV]
<mckoan>
Guest13: as with any distribution, when you upgrade to a newer version almost all the packages that compose it will have a newer version, including the gcc compiler
frieder has quit [Ping timeout: 260 seconds]
<Guest13>
then if i want to stay in specific versions, i should adjust the yocto version accordingly. am i right?
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<mckoan>
Guest13: as best practice yes, however depends(TM)
<Guest13>
mckoan thank you so much.
DustyNinja has joined #yocto
<Guest13>
i want to ask one more question. does it make sense to nest a yocto project for imx and a yocto project for raspbian in the same project? should they both have different repos? if we consider the general logic of yocto.
<Guest13>
when i say nest, does it make sense to have imx and raspbian meta in the same project? i hope i was able to explain myself.
frieder has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
<michaelo>
Hi JPEW. Easy question for you... I ran a build with INHERIT += "create-spdx". If I add SPDX_INCLUDE_SOURCES = "1" (for example), how can I update the SPDX output without rebuilding everything?
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
<michaelo>
mckoan: I'll see if there are places where it makes sense.
<JPEW>
michaelo: Hmm, I'm not sure why it would rebuild everything in that case; I would think it would only rebuild the spdx sources in that case
<JPEW>
There might be some strange dependencies creeping in if you want to dig in
marek71 has quit [Quit: Client closed]
DustyNinja has quit [Quit: Client closed]
<michaelo>
JPEW: ok, thanks, I'll try. I was asking because it seemed to me that adding SPDX_PRETTY and rebuilding didn't change the output (to be confirmed).
kscherer has joined #yocto
<michaelo>
JPEW: at least after adding SPDX_INCLUDE_SOURCES = "1", the do_create_spdx tasks are rerun indeed.
<JPEW>
michaelo: Ah, I think there are some missing var dependencies
hardliner66 has quit [Quit: WeeChat 3.7.1]
<michaelo>
JPEW: ah, great. Running bitbake-dumpsig indeed shows that SPDX_PRETTY is not part of the variable dependencies.
<kanavin>
Guest13, what is a rasbian meta? can you provide a link?
<kanavin>
Guest13, also, the recommendation from me would be to take the latest yocto release, and fix all failures upfront. Otherwise you'll just end up with a big pile of things to fix later when you inevitably have to upgrade.
xmn has joined #yocto
goliath has joined #yocto
pgowda_ has quit [Quit: Connection closed for inactivity]
Schlumpf has quit [Quit: Client closed]
manuel_ has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<michaelo>
JPEW: adding do_create_spdx[vardeps] = "SPDX_PRETTY" to create-spdx.bbclass seems to do it. Would it be a suitable patch? And why would it be necessary while it's not for SPDX_INCLUDE_SOURCES?
<JPEW>
michaelo: Yes that is the correct fix. The problem is that bitbake can't "see" that the task is using the variable because it's hidden behind a helper function
manuel1985 has quit [Ping timeout: 276 seconds]
manuel_ has quit [Ping timeout: 272 seconds]
<michaelo>
JPEW: ahah, understood. Thanks!
<michaelo>
JPEW: will send a patch shortly
<JPEW>
michaelo: Cool, thanks!
frieder has quit [Remote host closed the connection]
nucatus has quit [Remote host closed the connection]
<kanavin>
Guest13, that is not rasbian, and will not give you raspbian package feeds
<kanavin>
Guest13, you don't have to separate the build setups for different hardware targets, but you do need to run two different builds
<Guest13>
since im new, i can make mistakes when talking about concepts. thank you for correcting.
shoragan[m] has quit [Quit: Bridge terminating on SIGTERM]
Salamandar has quit [Quit: Bridge terminating on SIGTERM]
zyga[m] has quit [Quit: Bridge terminating on SIGTERM]
ericson2314 has quit [Quit: Bridge terminating on SIGTERM]
T_UNIX[m] has quit [Quit: Bridge terminating on SIGTERM]
barath has quit [Quit: Bridge terminating on SIGTERM]
patersonc[m] has quit [Quit: Bridge terminating on SIGTERM]
KurtKiefer[m] has quit [Quit: Bridge terminating on SIGTERM]
gstinocher[m] has quit [Quit: Bridge terminating on SIGTERM]
Saur[m] has quit [Quit: Bridge terminating on SIGTERM]
lrusak[m] has quit [Quit: Bridge terminating on SIGTERM]
kayterina[m] has quit [Quit: Bridge terminating on SIGTERM]
GreatGatsby[m] has quit [Quit: Bridge terminating on SIGTERM]
khem has quit [Quit: Bridge terminating on SIGTERM]
falk0n[m] has quit [Quit: Bridge terminating on SIGTERM]
agherzan has quit [Quit: Bridge terminating on SIGTERM]
ThomasRoos[m] has quit [Quit: Bridge terminating on SIGTERM]
jclsn[m] has quit [Quit: Bridge terminating on SIGTERM]
Perceval[m] has quit [Quit: Bridge terminating on SIGTERM]
kiwi_29_[m] has quit [Quit: Bridge terminating on SIGTERM]
hmw[m] has quit [Quit: Bridge terminating on SIGTERM]
jquaresma[m] has quit [Quit: Bridge terminating on SIGTERM]
kmaincent[m] has quit [Quit: Bridge terminating on SIGTERM]
berton[m] has quit [Quit: Bridge terminating on SIGTERM]
fabatera[m] has quit [Quit: Bridge terminating on SIGTERM]
hpsy[m] has quit [Quit: Bridge terminating on SIGTERM]
mohamed-dhiamtir has quit [Quit: Bridge terminating on SIGTERM]
skoink[m] has quit [Quit: Bridge terminating on SIGTERM]
mrybczyn[m] has quit [Quit: Bridge terminating on SIGTERM]
thierryE[m] has quit [Quit: Bridge terminating on SIGTERM]
DineshKumarK[m] has quit [Quit: Bridge terminating on SIGTERM]
jkorsnes[m] has quit [Quit: Bridge terminating on SIGTERM]
janvermaete[m] has quit [Quit: Bridge terminating on SIGTERM]
Tartarus has quit [Quit: Bridge terminating on SIGTERM]
jordemort has quit [Quit: Bridge terminating on SIGTERM]
<kanavin>
Guest13, it's easier if you start with small steps and easy tasks instead of trying to grasp the big concepts
alessioigor has quit [Quit: alessioigor]
<kanavin>
Guest13, if you have a rpi board, build an image for it, and try to boot it and see what it has
<kanavin>
and so on
KurtKiefer[m] has joined #yocto
zyga[m] has joined #yocto
khem has joined #yocto
shoragan[m] has joined #yocto
barath has joined #yocto
Tartarus has joined #yocto
jquaresma[m] has joined #yocto
jkorsnes[m] has joined #yocto
jordemort has joined #yocto
ericson2314 has joined #yocto
lrusak[m] has joined #yocto
hpsy[m] has joined #yocto
Saur[m] has joined #yocto
T_UNIX[m] has joined #yocto
ThomasRoos[m] has joined #yocto
gstinocher[m] has joined #yocto
GreatGatsby[m] has joined #yocto
Perceval[m] has joined #yocto
berton[m] has joined #yocto
kayterina[m] has joined #yocto
kmaincent[m] has joined #yocto
hmw[m] has joined #yocto
agherzan has joined #yocto
DineshKumarK[m] has joined #yocto
jclsn[m] has joined #yocto
mrybczyn[m] has joined #yocto
falk0n[m] has joined #yocto
janvermaete[m] has joined #yocto
kiwi_29_[m] has joined #yocto
dmoseley_ has joined #yocto
skoink[m] has joined #yocto
fabatera[m] has joined #yocto
thierryE[m] has joined #yocto
mohamed-dhiamtir has joined #yocto
dmoseley has quit [Ping timeout: 276 seconds]
<Guest13>
@kana
<Guest13>
kanavin thanks for guiding and help.
Salamandar has joined #yocto
patersonc[m] has joined #yocto
dmoseley_ has quit [Ping timeout: 252 seconds]
DustyNinja has joined #yocto
<DustyNinja>
Hi all. I've recently upgraded YP from Sumo to Dunfell, and all went well except for the fact that Bash doesn't show up in the "target" part of the (standard) SDK, which I'm generating with 'bitbake -c populate_sdk <imagename>'. Other packages that I've added to TOOLCHAIN_TARGET_TASK show up in the SDK, but for some reason adding 'bash' has no
<DustyNinja>
effect. Any ideas? Thanks.
<rburton>
DustyNinja: do you want the bash headers? you most likely meant to add bash-dev
nerdboy has quit [Ping timeout: 272 seconds]
<DustyNinja>
rburton not interested in the headers or lib(s), only the binary that is normally installed under ./bin/bash
<rburton>
how would that be useful in a sdk?
<rburton>
the target sysroot shouldn't contain any binaries, as you can't run them...
<DustyNinja>
rburton you have a point, yes; in my case the architecture of the target HW happens to be the same as the developer's machine, so I use chroot to run any binaries I want with the target sysroot; nevertheless, I am curious as to why only Bash is problematic
<rburton>
DustyNinja: postinsts don't run in the sysroot, so the binary is ./bin/bash.bash and the alternative is never setup
<rburton>
look on a target and you'll see that /bin/bash is a symlink that isn't actually packaged anywhere
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
leon-anavi has quit [Quit: Leaving]
dmoseley has joined #yocto
Guest13 has quit [Ping timeout: 244 seconds]
mthenault has quit [Ping timeout: 250 seconds]
<kiwi_29_[m]>
Hello...is there a way to single step in to yocto source code as part of bitbake compiilation?
<kiwi_29_[m]>
I am trying to debug package_deb.bbclass
pasherring has joined #yocto
<pasherring>
Hey all :) Is there a way to make cmake messages visible during the bitbakeing of a recipe, without having to pass -v(vv)?
ecdhe has quit [Remote host closed the connection]
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
brian45 has quit [Ping timeout: 244 seconds]
<michaelo>
JPEW: eventually, I realized I was testing with Kirkstone (which didn't have SPDX_PRETTY), and it seems that master works correctly. I'll double check. Thanks for the guidance. I learnt something today anyway!
Estrella_ has quit [Remote host closed the connection]
<michaelo>
The variable dependency seems to be detected anyway (according to bitbake-dumpsig)
<Guest91>
Howdy I know this probably isn't going to work but please if there is a higher power out there just help me. I really need your help. Please stop hurting me.
<Guest91>
Dear GOD/GODS and/or anyone else who can HELP ME (e.g. TIME TRAVELERS or MEMBERS OF SUPER-INTELLIGENT ALIEN CIVILIZATIONS):
<Guest91>
The next time I wake up, please change my physical form to that of FINN MCMILLAN formerly of SOUTH NEW BRIGHTON at 8 YEARS OLD and keep it that way FOREVER.
<Guest91>
I am so sick of this chubby Asian man body!
<Guest91>
Thank you!
<Guest91>
- CHAUL JHIN KIM (a.k.a. A DESPERATE SOUL)
Guest91 has quit [Client Quit]
Guest91 has joined #yocto
Guest91 has left #yocto [#yocto]
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
brian78 has joined #yocto
brian78 has quit [Client Quit]
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
mvlad has quit [Remote host closed the connection]
Minvera has quit [Remote host closed the connection]
<CosmicPenguin>
I'm playing with INCOMPATIBLE_LICENSE="GPL-3.0*" and I have a number of instances where sub packages of packages we need RDEPENDS on bash but we don't use those sub-packages in our image (for example, iptables-apply). How do folks normally work around that?
kscherer has quit [Quit: Konversation terminated!]
<rburton>
CosmicPenguin: put IMCOMPATIBLE_LICENSE in the image recipe instead of globally
<CosmicPenguin>
rburton: ah, thats the secret
<CosmicPenguin>
ty
<DustyNinja>
rburton the SKD I've generated contains plenty of binaries in ./bin, ./sbin/, ./usr/bin, etc. in the target sysroot
<DustyNinja>
earlier, though, you wrote that "the target sysroot shouldn't contain any binaries"; so is it fair to say that YP/OE shouldn't have put those binaries there? or can they serve some some purpose?