Hi, thanks for reply and sorry, been busy with other stuff. Regarding esdk - what is their purpose now, when there is this new workflow? I mean, in what use cases would you use esdk instead of this new workflow?
For example, i'm now trying to setup ci/cd pipeline for testing using qemu. Is it good idea to run devtool runqemu or just runqemu from esdk? Cause i tried that and it failed - specifically, i run MACHINE=qemuarm devtool runqemu nographic and get "runqemu - ERROR - IMAGE_LINK_NAME wasn't set to find corresponding .qemuboot.conf file" (i get similar error even when just running MACHINE=qemuarm runqemu). MACHINE=qemuarm runqemu command runs fine under normal yocto environment (devtool runqemu subcommand doesn't exist under this environment). Also, tmp/deploy/images/qemuarm/*.qemuboot.conf exist in esdk. Changing MACHINE to runqemu in conf/local.conf doesn't work either. Is this expected? Thanks, rado.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63910): https://lists.yoctoproject.org/g/yocto/message/63910 Mute This Topic: https://lists.yoctoproject.org/mt/108301955/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
