jwillikers has quit [Remote host closed the connection]
Vonter_ has joined #yocto
Vonter_ has quit [Ping timeout: 265 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 265 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 265 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 265 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 265 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 265 seconds]
pidge95 has joined #yocto
pidge has quit [Ping timeout: 256 seconds]
Net147 has quit [Quit: Quit]
Net147 has joined #yocto
Net147 has joined #yocto
Net147 has quit [Changing host]
Net147 has quit [Quit: Quit]
pidge957 has joined #yocto
pidge95 has quit [Ping timeout: 256 seconds]
Net147 has joined #yocto
Net147 has joined #yocto
Net147 has quit [Changing host]
Net147 has quit [Remote host closed the connection]
Net147 has joined #yocto
Net147 has joined #yocto
Net147 has quit [Changing host]
Net147 has quit [Quit: Quit]
Net147 has joined #yocto
Net147 has joined #yocto
Net147 has quit [Changing host]
Net147 has quit [Client Quit]
<manuel1985>
Which compositor for wayland would you recommend for embedded use case? Will run gtk+3 applications.
Net147 has joined #yocto
Net147 has joined #yocto
Net147 has quit [Changing host]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 252 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 265 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 252 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 265 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 252 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 252 seconds]
goliath has joined #yocto
Vonter has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
vladest has joined #yocto
kroon has joined #yocto
<kroon>
I'm using the Yocto sstate mirrors and uninative in dunfell. Not getting much of sstate reuse though, some of the native builds yes, but for instance "pseudo-native" is being built, which I didn't expect. Any ideas how to debug why this is happening ? Some way to compare the siginfos ?
wwilly has quit [Read error: Connection reset by peer]
<manuel1985>
When I build for quemux86-64, bitbake runs both do_image_ext4 and do_image_tar. Do I need both?
florian__ has quit [Ping timeout: 264 seconds]
<RP>
manuel1985: depends which output format you end up using
<RP>
manuel1985: you can configure with IMAGE_FSTYPES
goliath has joined #yocto
florian__ has joined #yocto
<manuel1985>
RP: Thanks. Which is the architectonically right place to set this variable?
<JaMa>
RP: would you mind restoring meta/classes/reproducible_build_simple.bbclass, just showing a warning that DISTRO should be included not to inherit this and that it's ON by default?
<manuel1985>
RP: Figure, the cleanest approach were to create my own machine and set IMAGE_FSTYPES there. Can I append to the qemux86-64 machine?
<JaMa>
I wouldn't call it cleanest, but yes you can "append" see openembedded-core/meta-selftest/conf/machine/qemux86copy.conf as an example
<JaMa>
it really depends on why you want to change it, if it's your DISTRO policy, than it can obviously go to DISTRO, if you want to just disable it for local builds to save some time of image build then local.conf is fine, if it's your CI job testing just one of these IMAGE_FSTYPES then it should go there
<JaMa>
creating own MACHINE config just to adjust IMAGE_FSTYPE value is huge overkill and will cause more work in future as well
<JaMa>
the only tricky part is that you cannot easily override with IMAGE_FSTYPES:<MACHINE>, because then it will be applied to initramfs images etc, so I usually use IMAGE_FSTYPES:<MACHINE>:pn-<IMAGE_NAMES_I_USUALLY_BUILD>
GillesM has joined #yocto
<manuel1985>
JaMa: Thanks, that explains it very well.
florian__ has quit [Ping timeout: 264 seconds]
xmn has joined #yocto
<manuel1985>
Think I'll still try out this own-MACHINE-config approach for once. I want my project to have a few officially supported targets and also have developers build and runqemu them regularly. As I see, qemux only mounts the .ext4 fs, so I figure it would be clean if I'd introduce a ourproject-vm machine building .ext4 only.
<manuel1985>
JaMa: Had problems setting it from local.conf, qemu.inc does IMAGE_FSTYPES += "tar.bz2 ext4" unconditionally
<manuel_>
Last time I checked, there was no nice emacs available in Yocto world. Was surprised.
florian__ has quit [Read error: Connection reset by peer]
florian__ has joined #yocto
dmoseley has joined #yocto
<manuel1985>
JaMa: Thanks, I'm building it now. Then perhaps the problem was that it's pulling so many depencies in. We'll see.
<manuel1985>
Is someone building Yocto-Images in the cloud and preserving sstate-cache?
<manuel1985>
Looking for ideas on how to do that properly
Vonter has joined #yocto
camus has quit [Quit: camus]
florian__ has quit [Read error: Connection reset by peer]
Vonter has quit [Ping timeout: 252 seconds]
florian__ has joined #yocto
Vonter has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
hpsy has joined #yocto
zyga-mbp has joined #yocto
Vonter has joined #yocto
Vonter has quit [Ping timeout: 252 seconds]
sb27 has joined #yocto
<sb27>
I have a yocto recipe for uwsgi 2.0.20. When I finish bitbaking and run the executable, it complains saying that I should rebuild it with pcre support. I already have 'include DEPENDS += "libpcre"' in the recipe. Is that not sufficient?
<JaMa>
RP: not sure if it's caused by recent repr() change, but I got first do_patch failure and it doesn't look well in knotty https://pastebin.com/t3xDxvHu it ended all in one-line with \n printed in the text
<RP>
JaMa: I guess we need to unescape those newlines :/
florian__ has quit [Ping timeout: 264 seconds]
Vonter_ has joined #yocto
Vonter_ has quit [Ping timeout: 252 seconds]
bluelightning has joined #yocto
mvlad has quit [Remote host closed the connection]
florian__ has joined #yocto
dev1990 has quit [Quit: Konversation terminated!]
zyga-mbp has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
GillesM has quit [Quit: Leaving]
zyga-mbp has joined #yocto
Vonter_ has joined #yocto
Vonter_ has quit [Ping timeout: 265 seconds]
Vonter_ has joined #yocto
florian__ has quit [Ping timeout: 264 seconds]
Vonter_ has quit [Ping timeout: 252 seconds]
florian__ has joined #yocto
zyga-mbp has quit [Read error: Connection reset by peer]