**** BEGIN LOGGING AT Sat Mar 16 02:59:57 2019
Mar 16 04:44:21 <yocti> New news from stackoverflow: Unable to start bitbake server <https://stackoverflow.com/questions/48132054/unable-to-start-bitbake-server>
Mar 16 15:44:10 * RP is pleased to make it home
Mar 16 15:52:32 <armpit> glad to hear you got home in one piece
Mar 16 15:58:11 <SimoneNascivera> Hi everyone
Mar 16 15:58:20 <SimoneNascivera> I have a question to make
Mar 16 15:58:40 <SimoneNascivera> if I build an image, core-image-sato for example
Mar 16 15:59:19 <SimoneNascivera> Then I'll get an *gpt.img file in /build/tmp/deploy/
Mar 16 16:00:17 <SimoneNascivera> but if I do a single packet build, example "bitbake git" will it be added to the image automatically? How could I recreate the .img file with the new package?
Mar 16 16:00:20 <SimoneNascivera> Thank you
Mar 16 16:08:36 <armpit> add IMAGE_INSTALL_append = " git" and build your image
Mar 16 16:08:46 <armpit> that will include git
Mar 16 16:09:32 <armpit> local.conf... forgot that part
Mar 16 16:09:43 <SimoneNascivera> I'm trying
Mar 16 16:10:48 <armpit> git is the recipe being built when you run bitbake git so you might need to double check out it splits out the packages
Mar 16 16:11:24 <SimoneNascivera> the problem is that I have already an  IMAGE_INSTALL_append entry in local.conf and even if I change it, when I do bitbake core-image-sato it doesn't seem to compile/add anything
Mar 16 16:12:00 <SimoneNascivera> if I check the packages in the .manifest file in the same directory as the .img file, the new packages are not listed
Mar 16 16:15:10 <armpit> you might need to look in tmp/work/{arch}/git/{version}/package-splits to see the name of the package needing to be add to the IMAGE_INSTALL*
Mar 16 16:16:57 <SimoneNascivera> armpit: thank you. I found the package-splits directory. Should all the packages in there be listed in local.conf?
Mar 16 16:19:48 <armpit> SimoneNascivera, only the ones that contain the binaries you want to install
Mar 16 16:20:08 <armpit> you can start with all and then scale back
Mar 16 16:23:56 <SimoneNascivera> armpit: even if I added all the package-splits nothing changed
Mar 16 16:25:24 <SimoneNascivera> armpit: I'm sure if I clean build everything it'll work, it happened also weeks ago but I would like to learn how to add packages without clean buildingthe image every time
Mar 16 16:39:04 <armpit> SimoneNascivera, you may want to look in the image itself, maybe the binaries are there just not showing up in the manafest
Mar 16 16:46:35 <SimoneNascivera> armpit: I tried mounting the img but there isn't any git binaries in the path specified in package_splits
Mar 16 16:49:10 <aduskett> Quick question: For cross-compiled python libraries, how does Yocto handle the cross compile? For example: Using Buildroot, I am porting gst-python, and it makes _gi_gst.cpython-37m-x86_64-linux-gnu.so, which is actually a ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, not stripped file.
Mar 16 16:49:36 <aduskett> So I guess a better question is, how does Yocto prevent the x86_64-linux-gnu naming schema from happening?
Mar 16 16:49:56 <SimoneNascivera> armpit: it does also make sense, since the last modification to the .img file  seems to be very old
Mar 16 16:54:57 <aduskett> ah, there's a qemu wrapper involved
**** ENDING LOGGING AT Sun Mar 17 02:59:57 2019