<yokto>
Can you name a few advanced methods that advanced yocto users use, besides creating recipe and configuration files? For example, configuring the linux kernel using devtool etcetera?
<LetoThe2nd>
yokto: it depends a bit on your needs and use case - a creating a recipe can be very advanced, while using devtool can be super basic.
<yokto>
LetoThe2nd true and I understand what you're getting at. Then I should rephrase my question (I have gone through the manual), what are some advanced yocto features/methods that advanced yocto users use / can use (creating recipes, working with devtool are two examples), what else is there available?
<yokto>
What else is there available that is either not stated in the manual or not clearly addressed in the manual (this is a better rephrasing)
KareemZarka[m] has quit [Remote host closed the connection]
lorenzog[m] has quit [Remote host closed the connection]
simonew has joined #yocto
<simonew>
Hi, we had some interest in fuzzing a yocto built linux kernel and have written a syzkaller recipes providing the needed host and qemu stuff. I'd like to upstream those but I have some doubts which layer would be best. Any thoughts?
<rburton>
tomzy_0[m]: remove that line, we work around that issue globally anyway
<simonew>
mcfrisk Could be an idea true
<LetoThe2nd>
simonew: either meta-security, or create your own and submit to the layerindex
<tomzy_0[m]>
rburton: thank you very much, I had meta-imx locally without whole history so did not saw that commit with git blame - is there a way to fix that with bbappend?
<tomzy_0[m]>
we have custom layer that is using meta-imx and I do not like to make changes in any "external" layers
<rburton>
a bbappend would be tricky. tell nxp that they've broken their layer.
<LetoThe2nd>
rburton: we should apply a different strategy. praising people when their vendor bsp layers are not broken. immediately reduces our workload ;-D
<tomzy_0[m]>
> tell nxp that they've broken their layer
<tomzy_0[m]>
again should be at the end of that statement
<tomzy_0[m]>
Heh
<tomzy_0[m]>
Could rewriting whole do_compile work?
<rburton>
its do_install, and its in an :append
<rburton>
tomzy_0[m]: do you need the python support in omxruntime? turn it off in the packageconfig if not, that will make this go away
<tomzy_0[m]>
yea, so it will be applied no matter what..
<rburton>
Entei[m]: what distribution are you using? and I meant _broken_ ram, quantity isn't relevantr.
<tomzy_0[m]>
maybe creating "custom" version of this recipe in our layer and set PREFERRED_VERSION?
<rburton>
tomzy_0[m]: easiest fix is turn off python if you don't need it.
<tomzy_0[m]>
Thank you
<simonew>
LetoThe2nd Ok, i'll think some about whats best of those options
Zaid has joined #yocto
florian__ has quit [Ping timeout: 250 seconds]
gsalazar has joined #yocto
thomasd13 has quit [Ping timeout: 256 seconds]
Zaid has quit [Quit: Client closed]
Zaid has joined #yocto
florian__ has joined #yocto
goliath has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
seninha has joined #yocto
Thorn_ has joined #yocto
Thorn has quit [Ping timeout: 240 seconds]
RobertBerger has quit [Ping timeout: 240 seconds]
rber|res has joined #yocto
florian__ has quit [Ping timeout: 246 seconds]
yokto has quit [Quit: Client closed]
florian__ has joined #yocto
florian__ is now known as florian
barometz has quit [Quit: you can't fire me!]
barometz has joined #yocto
<Entei[m]>
<rburton> "Entei: what distribution are you..." <- Fedora 37
<Entei[m]>
How do I prevent the build system to generate tons of locale packages for each package? I just want en_US packages
<rburton>
the generation of those packages is almost no time, just don't install them
mateuszmar2 has joined #yocto
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
michalsieron has joined #yocto
michalsieron has quit [Client Quit]
michalsieron has joined #yocto
camus has quit [Ping timeout: 240 seconds]
simonew has quit [Quit: Client closed]
seninha has quit [Quit: Leaving]
seninha has joined #yocto
simonew has joined #yocto
Zaid has quit [Quit: Client closed]
florian has quit [Ping timeout: 240 seconds]
kscherer has joined #yocto
xmn has joined #yocto
<rburton>
abelloni: so the libnl one is genuine, it doesn't output any tests running
<rburton>
abelloni: curious that it doesn't happen every time, there's definitely a bug somewhere
<zeddii>
it's the SRC_URI ordering that matters now. The searching of patches, etc, has all been dropped.
<__ad>
on zeus, is it mandatory to use python 2.7 ?
<rburton>
__ad: you might want to clarify what you mean. the docs says python 3.4.
philmd has joined #yocto
<__ad>
ok- i have a container with python 2.7 that works fine. But have "repo" issues, since getting repo, i get the last one, not working with python 2.7
<__ad>
where can i see what pyhton is required for a specific yocto version ?