<Lachlan94>
Can anyone shed some light on how to handle `WORKDIR` not being updated when installing a recipe that has been moved to the workspace folder with `devtool modify`?
<Lachlan94>
e.g WORKDIR is pointing to the `/build/tmp/work/` path rather than the new `workspace/sources` path in the install phase meaning `cp -r ${WORKDIR}/git/server ${D}${sysconfdir}/` fails
<Lachlan94>
or is there a better way to move build artifacts to the device?
<Lachlan94>
nvm, missed the `WORKSPACE` changes since `kirkstone`
tec4 has quit [Quit: bye!]
tec4 has joined #yocto
cabazon has quit [Quit: Client closed]
Lachlan94 has quit [Quit: Client closed]
ablu has quit [Ping timeout: 252 seconds]
ablu has joined #yocto
vthor has joined #yocto
gyokhan29 has joined #yocto
vthor_ has quit [Ping timeout: 260 seconds]
gyokhan29 is now known as gyokhan
<gyokhan>
Hello people, I am quite new to the Yocto project, and IRC. How could I verify if I logged to my verified account in in this client?
<gyokhan>
I use directly web.libera.chat's web client, sorry, should mentioned that earlier.
gyokhan has quit [Quit: Client closed]
gyokhan has joined #yocto
<gyokhan>
Hey people, how can I check if my latest image build included the layers? I expect it to be around 100MBs, however, found it as 70MB. I need to investigate if everything really included. *Note: There was no error during the build.* PS. I'm a noob.
florian has joined #yocto
gyokhan has quit [Ping timeout: 272 seconds]
drv_ has joined #yocto
kevinrowland has quit [Quit: Client closed]
Kubu_work has joined #yocto
ptsneves has quit [Ping timeout: 248 seconds]
goliath has joined #yocto
gyokhan has joined #yocto
gyokhan has quit [Ping timeout: 248 seconds]
florian has quit [Ping timeout: 252 seconds]
gyokhan has joined #yocto
<yocton>
gyokhan: Hello! For your IRC account, you should see a message from NickServ telling you that you are identified.
<yocton>
gyokhan: as for your image: Usually, either the build is sucessful and everything you want (using IMAGE_INSTALL) is included or the build fails and you have an error message telling why. You can see the list of installed packages in the manifest file next to your image.
gyokhan has quit [Ping timeout: 264 seconds]
gyokhan has joined #yocto
gyokhan has quit [Ping timeout: 248 seconds]
florian has joined #yocto
gyokhan has joined #yocto
Bardon has quit [Ping timeout: 246 seconds]
florian has quit [Ping timeout: 248 seconds]
pbsds37 has joined #yocto
pbsds3 has quit [Ping timeout: 260 seconds]
pbsds37 is now known as pbsds3
gyokhan has quit [Ping timeout: 248 seconds]
gyokhan has joined #yocto
pbsds3 has quit [Ping timeout: 246 seconds]
reatmon_ has quit [Remote host closed the connection]
reatmon_ has joined #yocto
gyokhan has quit [Ping timeout: 276 seconds]
gyokhan has joined #yocto
druppy has joined #yocto
Daanct12 has quit [Quit: WeeChat 4.4.4]
ChristosG has joined #yocto
drv_ has quit [Ping timeout: 252 seconds]
gyokhan has quit [Ping timeout: 244 seconds]
florian has joined #yocto
drv_ has joined #yocto
gyokhan has joined #yocto
gyokhan has quit [Ping timeout: 264 seconds]
florian has quit [Ping timeout: 248 seconds]
ChristosG has quit [Quit: Client closed]
drv_ has quit [Ping timeout: 246 seconds]
gspbirel56 has quit [Ping timeout: 248 seconds]
gyokhan has joined #yocto
gyokhan has quit [Read error: Connection reset by peer]
gyokhan has joined #yocto
gyokhan has quit [Quit: gyokhan]
pbiel has joined #yocto
pbiel has quit [Read error: Connection reset by peer]
pbiel has joined #yocto
pbiel has quit [Remote host closed the connection]
pbiel has joined #yocto
bielpa_ has joined #yocto
pbiel has quit [Ping timeout: 260 seconds]
drv_ has joined #yocto
drv_ has quit [Remote host closed the connection]
drv_ has joined #yocto
Vonter has joined #yocto
druppy has quit [Ping timeout: 260 seconds]
drv_ has quit [Ping timeout: 265 seconds]
drv_ has joined #yocto
druppy has joined #yocto
drv_ has quit [Ping timeout: 244 seconds]
drv_ has joined #yocto
florian has joined #yocto
ChristosG has joined #yocto
ChristosG has quit [Client Quit]
<marex>
Hi, is it possible to stage something into sysroot right after do_compile and before do_install already ?
<marex>
basically I ran into dependency loop in oe-core between uboot-sign.bbclass and kernel-fitimage.bbclass if both UBOOT_SIGN_ENABLE and UBOOT_ENV are enabled
<marex>
if UBOOT_ENV is enabled , kernel-fitimage depends on virtual/bootloader:do_populate_sysroot which runs after u-boot do_install
<marex>
uboot-sign.bbclass do_uboot_assemble_fitimage depends on kernel-fitimage do_populate_sysroot , but has to run before u-boot do_install
<marex>
cambrian_invader: ^
<marex>
so I was thinking, if u-boot can stage the generated env blob into sysroot early, kernel-fitimage bbclass can depend on that early task instead of do_populate_sysroot and that would break the loop
fberton has joined #yocto
fberton has quit [Client Quit]
drv_ has quit [Ping timeout: 252 seconds]
ChristosG has joined #yocto
<jclsn>
Little late, but happy new year guys!
drv_ has joined #yocto
druppy has quit [Ping timeout: 244 seconds]
florian has quit [Ping timeout: 245 seconds]
druppy has joined #yocto
druppy has quit [Ping timeout: 246 seconds]
florian has joined #yocto
drv_ has quit [Ping timeout: 244 seconds]
drv_ has joined #yocto
kanavin_ has joined #yocto
kanavin has quit [Ping timeout: 265 seconds]
kanavin_ has quit [Remote host closed the connection]
kanavin_ has joined #yocto
kanavin_ has quit [Remote host closed the connection]
kanavin_ has joined #yocto
kanavin_ has quit [Read error: Connection reset by peer]
kanavin has joined #yocto
gspbirel56 has joined #yocto
kanavin has quit [Remote host closed the connection]