Hi Alex, Adrian, thanks for the explanation. I checked the slides, watched the video and tried this workflow (partially - didn't try deploy-target and finish), and it seems to work, but still have some questions: * Alex, you write above: Classic esdk bundles will almost certainly not be developed further. - so am i getting this right, that there isn't gonna be a way to generate e/sdk installer in the future (and there will be only this workflow available)? * Adrian, you write above: The second thing you need is a shared sstate-cache. This feature is now available officially in Yocto. - do you mean by this publishing it via web server? So if have it published and it works for standalone esdk, will it also work for this new devtool workflow under normal yocto build environment? Do i need to do anything specific or will it work out of the box when someone else creates their own yocto build enironment? * in the presentation you talk about cmake and meson; what's the state of support for building recipes using other ways - for example makefiles and python packages (i tried to devtool modify and build a python app and it seems to work) * are there any plans to support other IDEs - specifically Eclipse? Or is it difficult to add support for them on our own? Or, If i understood correctly - if we use --ide=none, it means devtool just creates some scripts for building/debugging and then we basically can use any IDE, right? * what's the state of this new devtool workflow at the moment - do you have any idea when it's gonna be officially released?
Thanks a lot for your time :)
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63803): https://lists.yoctoproject.org/g/yocto/message/63803 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] -=-=-=-=-=-=-=-=-=-=-=-
