<DvorkinDmitry>
may I put LICENSE_FLAGS_WHITELIST statement anywhere, not to site.conf only?
<DvorkinDmitry>
except locla.conf too
starblue has quit [Ping timeout: 255 seconds]
starblue has joined #yocto
xmn has quit [Quit: ZZZzzz…]
sakoman has joined #yocto
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #yocto
xmn has joined #yocto
sakoman has quit [Ping timeout: 252 seconds]
sakoman has joined #yocto
sakoman has quit [Ping timeout: 255 seconds]
xmn has quit [Read error: Connection reset by peer]
Core3985 has joined #yocto
applepi has quit [Read error: Connection reset by peer]
applepi has joined #yocto
Core3985 has quit [Ping timeout: 255 seconds]
sakoman has joined #yocto
Core7717 has joined #yocto
applepi has quit [Ping timeout: 255 seconds]
sakoman has quit [Ping timeout: 246 seconds]
sakoman has joined #yocto
sakoman has quit [Client Quit]
applepi has joined #yocto
Core7717 has quit [Ping timeout: 255 seconds]
nerdboy has quit [Ping timeout: 256 seconds]
mattsm0 has joined #yocto
LocutusOfBorg has quit [Ping timeout: 256 seconds]
mattsm has quit [Ping timeout: 268 seconds]
mattsm0 is now known as mattsm
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
enok has joined #yocto
paulg has quit [Ping timeout: 256 seconds]
Minvera has quit [Ping timeout: 256 seconds]
thomas_34 has joined #yocto
enok has quit [Ping timeout: 256 seconds]
<thomas_34>
Good morning, maybe someone can help me on my packaging question? I have a recipe, which produces firmware in different variety. Lets say in this example firmware-release and firmware-debug. This firmware-blob (or file) has to be on a certain path in the rootfs under a certain name. Lets say /lib/firmware/firmware.elf
enok has joined #yocto
<thomas_34>
So when I build recipe in release variant, it installs firmware-release to /lib/firmware/firmware.elf
sakman_ has joined #yocto
<thomas_34>
Same with the debug variant. Now I wonder if it somehow possible, that I create two packages from that recipe - A release and a debug package which either one of these get deployed on my rootfs.
sakman_ has quit [Client Quit]
<thomas_34>
The problem is, that each variant has to be installed under the same name/path on the rootfs. But otherwise, I'm surely not the first person who encouters that kind of problem, or do I?
sakman has quit [Ping timeout: 252 seconds]
<mcfrisk_>
thomas_34: two different recipes, or different file names, or different file names but a common symlink name generated at package install or boot time
alessioigor has joined #yocto
<thomas_34>
mcfrisk_, hi - thanks for the ideas. I was thinking about common symlink. I wasn't sure if that is possible to create a symlink at package time. But it seems it is. Do you know some example how to do that?
<thomas_34>
So why i ask this: My knowledge about install/packaging is, that everything I want to package must exist after do_install on the image.
<mcfrisk_>
thomas_34: don't know examples. the post-install scripts are a bit tricky, afaik, due to multiple package formats. at boot time I've seen debug features tied to HW security features like fuses which are blown after product leaves factory.
<thomas_34>
Ah okay - so this is not a "widespread" solution
<mcfrisk_>
thomas_34: gconf.bbclass seems to be one complex example
<thomas_34>
mcfrisk_, okay thank you! I'll look into it
enok has quit [Ping timeout: 252 seconds]
sakman has joined #yocto
florian_kc has joined #yocto
enok has joined #yocto
rob_w has joined #yocto
zpfvo has joined #yocto
enok has quit [Ping timeout: 264 seconds]
florian_kc has quit [Ping timeout: 256 seconds]
albrod has joined #yocto
amitk has joined #yocto
LocutusOfBorg has joined #yocto
amitk has quit [Ping timeout: 264 seconds]
mvlad has joined #yocto
Kubu_work has joined #yocto
ablu has quit [Ping timeout: 256 seconds]
ablu has joined #yocto
rob_w_ has joined #yocto
albrod has quit [Quit: Client closed]
vladest has quit [Ping timeout: 264 seconds]
gsalazar has joined #yocto
alperak_ has joined #yocto
alperak_ has quit [Client Quit]
alperak_ has joined #yocto
alperak_ is now known as alperak
frieder has joined #yocto
vladest has joined #yocto
phako_ has joined #yocto
Daanct12 has quit [Quit: WeeChat 4.2.2]
mrpelotaz0 has quit [Read error: Connection reset by peer]
mrpelotazo has joined #yocto
LocutusOfBorg has quit [Remote host closed the connection]
LocutusOfBorg has joined #yocto
mrpelotazo has quit [Read error: Connection reset by peer]
Daanct12 has joined #yocto
mrpelotazo has joined #yocto
Kubu_work has quit [Quit: Leaving.]
Kubu_work has joined #yocto
luc4 has joined #yocto
starblue has quit [Ping timeout: 252 seconds]
LocutusOfBorg has quit [Ping timeout: 252 seconds]
starblue has joined #yocto
LocutusOfBorg has joined #yocto
mrpelotazo has quit [Read error: Connection reset by peer]
<thomas_34>
However it does not seem to get executed when creating the rootfs.
<thomas_34>
Which task of the recipe should normally reflect the pkg_postinst? When I check temp/log.task_order of my recipe, there is nothing like pkg_postinst.
<thomas_34>
When I grep the whole temp folder for a string which shows up in my postinst-Script, there is nothing.
<thomas_34>
Do I search in the correct place?
enok has joined #yocto
<qschulz>
thomas_34: if you can share the code snippet you wrote, it'd help
<zhmylove>
Hey everyone. I have two things. First of all, variable SDK_PRUNE_SYSROOT_DIRS is not documented at all, but it should be I think. I'm unable to send a PR now, so if anyone can work on this — it'd be nice!
sakoman has quit [Ping timeout: 252 seconds]
<zhmylove>
And I have a question. I'm trying to change some variable from anon. python() block like this: if 'compile' in str(d.getVar('BB_CURRENTTASK')): d.prependVar('MAKE', 'xxx '), but this results into "The metadata is not deterministic" error... Is there any way to override some variable only for do_compile?
sev99 has joined #yocto
<rburton>
zhmylove: FOO:task-compile = "fish"
<rburton>
eg bitbake.conf does EXTRA_OEMAKE:prepend:task-compile = "${PARALLEL_MAKE} "
<zhmylove>
rburton: Nice, thanks! Is there any way we can do the same from python? setVarFlag('FOO', 'task-compile', 'fish')?
<zhmylove>
BTW is there any way we can override function the same way? I mean like setVar('do_compile', 'exit 0') but only for task-compile?
<rburton>
zhmylove: functions are variables
applepi has joined #yocto
<sa7mfo>
Hello, I'm trying out devtool to build u-boot for a iMX8M-board. I'm able to build the bootloader with `devtool build u-boot-imx`. However, just building u-boot-imx is not enough, the "normal" build-process does some magic (not sure which tools involved) and the resulting bootloader image is called imx-boot, which i s not built by just building the
<sa7mfo>
u-boot-imx recipe. As imx-boot is not built, the `devtool build-image` does not work either. So,
<sa7mfo>
1. Is there any way to know which target that generates imx-boot?
<sa7mfo>
2. Can I trigger that build somehow?
<applepi>
Okay weird thing I'm running into that I haven't before. I need to patch a file, but it's a file that's not in the git source for the recipe, its a local file (in the recipes' files/ directory). I've got a patch file written, but it can't find the file, presumably because its trying to patch in the source tree, not in the local files/
<applepi>
directory.. Any ideas on how I can get around that?
<rburton>
applepi: why are you patching a file that you're already shipping?
<rburton>
if the file is in the recipe already then just change it directly?
<applepi>
It's in the open-embedded/ recipe. I could go in and modify it yes, I was trying to leave the "not my code" meta's alone.
<rburton>
ah so you have a bbappend?
<applepi>
Right yeah. I'm building chrony, and need to modify the chrony.conf file that it comes with. But that's in meta-openembedded/blahblahblah/chrony/files
<rburton>
if the bbappend prepends to FILESEXTRAPATHS then you can put a patched version of the file in your layer with the bbappend. bitbake will grab your version of the file instead of the one in meta-oe.
<applepi>
oh interesting
<applepi>
I hadn't thought of that
<applepi>
Let me try that right now
sakoman has joined #yocto
k1r0s has joined #yocto
sakoman has quit [Ping timeout: 256 seconds]
<k1r0s>
Hello, I have a doubt. Once my application is ready and tested, my dependencies are declared into yocto files. How do I include my application source within the yocto project?
<rburton>
k1r0s: the recipe will say where to get it from, so you'd tell it to fetch source from a git repo or something
<rburton>
best practise is to keep the layer/recipes and actual source code separate
<rburton>
like every other recipe, but with an internal git server assuming you mean closed source code.
ptsneves has joined #yocto
<applepi>
rburton - that worked, thanks! I am a yocto white belt at best so that really helped
sakoman has joined #yocto
Minvera has joined #yocto
sakoman has quit [Ping timeout: 260 seconds]
ptsneves has quit [Ping timeout: 246 seconds]
Daanct12 has quit [Quit: WeeChat 4.2.2]
Daanct12 has joined #yocto
<k1r0s>
rburton I guess the source code (if its private) may live within the building machine
k1r0s has quit [Quit: Client closed]
k1r0s has joined #yocto
Daanct12 has quit [Quit: WeeChat 4.2.2]
k1r0s has quit [Client Quit]
linfax has joined #yocto
sakoman has joined #yocto
vladest has quit [Ping timeout: 256 seconds]
sakoman has quit [Ping timeout: 252 seconds]
Saur_Home29 has quit [Quit: Client closed]
Saur_Home29 has joined #yocto
sotaoverride is now known as Guest6328
Guest6328 has quit [Killed (molybdenum.libera.chat (Nickname regained by services))]
ctraven is now known as sotaoverride
sotaover1ide has joined #yocto
imx has quit [Quit: Client closed]
goliath has joined #yocto
Saur_Home29 has quit [Quit: Client closed]
Saur_Home29 has joined #yocto
sakoman has joined #yocto
luc4 has quit [Ping timeout: 255 seconds]
sakoman has quit [Ping timeout: 256 seconds]
alperak has quit [Quit: Connection closed for inactivity]
vladest has joined #yocto
sakoman has joined #yocto
sa7mfo has quit [Quit: Client closed]
sakoman has quit [Ping timeout: 268 seconds]
<olani>
thomas_34: You can use the update-alternatives.bbclass to create symlinks.
<olani>
thomas_34: If you are building with RPMs, you can check the .spec file for your postinst function. If it is not included there, you probably messed up the syntax somehow.
<olani>
thomas_34: If you are using opkg it's in some similar file - I don't know which.
<olani>
thomas_34: postinst functions are typically shown in the do_rootfs log, at least for RPM. You should at least be able to find other functions as examples of what it should look like. Obviously, your package have to be installed for the function to trigger. Make sure it is actually included.
<rburton>
the postinsts are in pkgdata too, eg $ oe-pkgdata-util read-value pkg_postinst:coreutils coreutils
<rburton>
oh, add -u to that to unescape and get newlines
prabhakalad has quit [Read error: Connection reset by peer]
prabhakalad has joined #yocto
xmn has joined #yocto
sakoman has joined #yocto
<thomas_34>
olani, thank you I will look into that
<thomas_34>
yeah, rburton they are not existent in my pkgdata. That I know now
<thomas_34>
I'm wondering how I can debug that
sakoman has quit [Ping timeout: 268 seconds]
sakoman has joined #yocto
enok has joined #yocto
rob_w_ has quit [Remote host closed the connection]
sakoman has quit [Ping timeout: 260 seconds]
zhmylove has joined #yocto
<zhmylove>
rburton: BTW we've tried `d.setVarFlag('oe_runmake_call', 'task-compile', d.getVar("_oe_runmake_call_for_analysis"))` and this seems not working leaving oe_runmake_call intact for do_compile
Xagen has joined #yocto
<qschulz>
zhmylove: because it's not a varflag you should use
<qschulz>
what you did here is oe_runmake_call[task-compile] = "${@d.getVar("_oe_runmake_call_for_analysis")}"
<yudjinn>
hey all, trying to add a `postinst_ontarget` programmatically to a recipe via bbclass, but it doesnt end up propagating; any ideas? I'm effectively trying to `d.setVar('pkg_postinst_ontarget:%s' % d.getVar("PN"))` but I never see a script in `/etc/rpm-postinst`
<rburton>
zhmylove: explain what you're trying to actually do?
<qschulz>
I think you should be able to do d.setVar('oe_runmake_call:task-compile', whaterver)
<zhmylove>
qschulz: Uh, I see. Thanks!
<zhmylove>
rburton: I'm trying to override MAKE for do_compile with "my_analyzer_tool -some-parameters make"
<zhmylove>
Leaving MAKE intact for do_install
<rburton>
MAKE:task-compile = "my_analyzer_tool -some-parameters make" in your class?
<zhmylove>
I forgot to mention that I want to make this change from anon. python() block in order to make it controllable with some python logic
sakoman has joined #yocto
<qschulz>
zhmylove: what kind of logic? because you can also have python in here
<qschulz>
MAKE:task-compile = "${@<some-python}"
<qschulz>
MAKE:task-compile = "${@<some-python>}" * (without the <>)
<zhmylove>
qschulz: thx! I'll try that way
sakoman has quit [Ping timeout: 256 seconds]
thomas_34 has quit [Quit: Client closed]
phako_ has quit [Quit: Client closed]
linfax has quit [Ping timeout: 264 seconds]
sakoman has joined #yocto
zpfvo has quit [Remote host closed the connection]
sakoman has quit [Ping timeout: 246 seconds]
sakoman has joined #yocto
thomas_34 has joined #yocto
geoffhp has joined #yocto
sakoman has quit [Ping timeout: 240 seconds]
enok has quit [Ping timeout: 260 seconds]
<thomas_34>
rburton, do you have any idea, why a pkg_postinst:${packagename}() {...} does not show up in pkgdata?
Saur_Home29 has quit [Quit: Client closed]
Saur_Home29 has joined #yocto
<rburton>
thomas_34: without seeing the recipe, no
<rburton>
easy answer is because packagename is wrong