tnovotny has quit [Remote host closed the connection]
<kayterina[m]>
dall-e? "make an octapus using tools in each tentacle"
<kanavin>
rburton, I posted on linked in about it:
<kayterina[m]>
"replace tools with teddy bears"
<kanavin>
"Ta-daa! My schedule is already fully packed with exciting talks, presentations and keynotes.
<kanavin>
...haha, not really. Or really not. The most value these events provide is in the 'hallway track', where you simply hang out with a snack and a drink (Dublin, I count on you!) and meet people. See you there?"
chrysh has joined #yocto
<rburton>
kanavin: my last conference in dublin was in trinity college, which was an amazing venue. a boring conference hotel is just a bit meh really.
<kanavin>
rburton, I think it's a conference center, but yes
<chrysh>
Hello everyone! Do you guys know, should content from sysroots-components end up in the rootfs?
<kanavin>
chrysh, no. that content is for building other recipes that depend on it
<jclsn[m]>
rburton: Does any one hold on to that?
<kanavin>
rootfs is composed from packages via a gigantic package manager transaction
<jclsn[m]>
I was thinking of a mascot, which also serves as a logo
<rburton>
jclsn[m]: i've a couple
<kanavin>
yoctopus is a cool idea
<jclsn[m]>
It bugs me that there is not logo on my Firefox tab when I have Yocto pages open
<jclsn[m]>
There should be some kind of Yocto icon
<jclsn[m]>
Maybe I will draw one when my X1 Yoga has arrived :P
<chrysh>
kanavin: So should I be able to find my mylib.so file and symbolic link to it in the rootfs folder after do_install task of the mylib recipe?
<jclsn[m]>
<kanavin> "yoctopus is a cool idea" <- Thought so :)
<kanavin>
chrysh, not really. do_install executes 'make install' with a recipe-specific destination. Then that destination is used by two independent tasks running in parallel. do_populate_sysroot further copies items needed for building dependencies, and do_package creates packages out of the same items.
<kanavin>
chrysh, to get those packages into a rootfs, you need to list them in your image recipe
<kanavin>
(unless they get pulled in though package dependencies, and libraries usually do - if you need to list them explicitly, something might be wrong)
mvlad has joined #yocto
<chrysh>
kanavin: I am still not sure, after which step should the content of ./tmp-glibc/sysroots-components/aarch64/mylib end up in the the rootfs/ folder ?
<kanavin>
chrysh, that content never ends up in the rootfs
<kanavin>
it's only for building other recipes
<Hutchinson[m]1>
Hello, Are you interested in making $1,500 plus additional $500 for diligence and hardwork in two weeks (legit) by sparing just 15/30 minutes of your time every 48hrs without no start up fee ? If yes get back to me for more details
<DarkKnight>
Is there a way that I can generate eSDK for only one recipe? I need to deliver an eSDK for compiling java sources with Open JDK8 to customer.
neverpan1c is now known as neverpanic
pasherring has joined #yocto
<pasherring>
Hey all. Is there a way to ask bitbake to run commands for all variants of a given recipe? I noticed that if I bitbake -c cleanall recipe, recipe-native will not be affected, for instance.
DarkKnight has quit [Quit: Client closed]
<pasherring>
(not sure if the "variant" naming is technically correct though :)
<pasherring>
Ah, and this is a farily old bitbake release (1.32, morty/rdk), not sure if the behavior is already changed
<chrysh>
qschulz: Thanks! I saw that, but I still don't see how my changes will end up in the rootfs. oe_soinstall only puts my lib into ./tmp-glibc/sysroots-components/aarch64/, but the next step of copying those files into the rootfs never happens
<qschulz>
the issue is that .so files are typically symlinks (that's what Bitbake expects) and make it to the -dev package
<qschulz>
the -dev package is not installed except if explicitly added to your image
<qschulz>
so we need to tell Bitbake to put the .so file into the "normal" package
starblue has quit [Ping timeout: 268 seconds]
starblue has joined #yocto
<chrysh>
so the steps are actually bitbake -c install mylib, then bitbake -c package myimage, bitbake -c rootfs myimage?
<chrysh>
qschulz: and also, if I create a test directory in do_install install -m 0755 -d ${D}${libdir}/abcdtest, this will also never make it into the rootfs?
<LetoTheII>
yo dudX
florian_kc has quit [Ping timeout: 252 seconds]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
LetoTheII is now known as LetoThe2nd
camus has quit [Quit: camus]
camus has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
tnovotny has joined #yocto
<chrysh>
qschulz: In any case, it worked! Thanks a lot!
jakew009 has joined #yocto
florian_kc has joined #yocto
<jakew009>
Can anyone point me in the right direction of how I include an "extra" with a pypi package?
<jakew009>
For instance, if the pip install string is `pip install --upgrade 'sentry-sdk[flask]'`
<jakew009>
How do I do this in a recipe?
<jakew009>
I am guessing maybe `PYPI_PACKAGE = "sentry-sdk[flask]"`?
<qschulz>
chrysh: bitbake my-image should be plenty enough
<qschulz>
chrysh: probably not without adding it to FILES:${PN}
<sotaoverride>
reposting my link incase someone wants to help me understand exactly why this happens. Apparently bitbake -c clean <recipe_name> got rid of the error. bitbake -c clean rpb-bi-image
<jclsn[m]>
sotaoverride: Because you are cleaning the work directory with that command
<sotaoverride>
I cant figure where / what in that error log is indicative of the error being a work dir error. I just stumbled upon that fix on stackoverflow. Trying to figure out what made it happen etc
jakew009 has quit [Quit: Client closed]
<jclsn[m]>
sotaoverride: No idea. I thought the command solved the error
<sotaoverride>
jclsn[m]: it did solve it, but I was just trying to figure out an explanation as to how/why...
<qschulz>
jclsn[m]: DISTRO_FEATURES need to be modified in configuration files
<qschulz>
jclsn[m]: ah my bad, that's your machine conf file
<qschulz>
is it actually possible to inherit overlayfs in a conf file? I don't think so?
<qschulz>
aaah
<qschulz>
damn matrix splitting the message in two
<jclsn[m]>
qschulz: No idea if that is even necessary
<jclsn[m]>
But without that nothing happens
<jclsn[m]>
With those added it complains about var-lib.mount and var-lib-systemd.mount missing
<jclsn[m]>
In the description it says
<jclsn[m]>
The class assumes you have a data.mount systemd unit defined in your
<jclsn[m]>
systemd-machine-units recipe and installed to the image.
<jclsn[m]>
No idea what is meant by that
<jclsn[m]>
systemd-machine-units.bb look pretty empty to me
<jclsn[m]>
Could also not find a documenation on it
<jclsn[m]>
I also thought that this recipe creates those systemd units
<jclsn[m]>
It is really not well documented. I would like to understand it and update the documentation for the class
<jclsn[m]>
Using an overlayfs manually in /etc/fstab did indeed solve my issue
<jclsn[m]>
and this recipe automatically creates the mount points for upper and workdir etc, which is nice
<jclsn[m]>
Ah yes I guess the only thing missing are those mount units
<kergoth>
hash style compatibility breaking abi. oops.
<kergoth>
lack of, that is
florian_kc has quit [Ping timeout: 260 seconds]
<hushmone1>
qschulz: lol thanks, i forgot to check back here and that is what i ended up doing, with exactly the same name even
hushmone1 is now known as hushmoney
justDeez is now known as justache
fabatera[m] has quit [Quit: You have been kicked for being idle]
kscherer has joined #yocto
<vvn>
wic create an extended mbr partition of 1.2G size, overlapping with following partitions. Why and how to prevent/fix that?
<vvn>
ok I get it, it has to overlap in order to contain the following partition, thus in order to resize the last partition, one must resize the extended partition first then the last partition, that makes sense.
pasherring has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<pasherring>
Hey there! Is there any trick to get the ${AUTOREV} SRCREV to work while working with a git local repository? I have a recipe with SRC_URI = "git:///path/to/local/git/;protocol=file;branch=branch-name". Setting SRCREV = "${AUTOREV}", the behavior depends if I am using local repo, or if I am using remote repo (as in git://url)
brazuca has quit [Quit: Client closed]
ecdhe has quit [Read error: Connection reset by peer]