> Am 28.05.2018 um 21:12 schrieb Alexander Kanavin <alex.kana...@gmail.com>: > > 2018-05-28 21:41 GMT+03:00 Jens Rehsack <rehs...@gmail.com>: >> When I log into my build machine, I just do >> >> $ oe_builddir use ~/gpw-community-bsp/gpw-yocto-platform/ >> >> and I'm in the right location and have all environment settings prepared to >> start a bitbake immediately. > > oe-init-build-env does the same thing, how is this better?
It allows you to do things like changing to build-dir and setup shell environment atomically - for example. >> $ oe_builddir help >> oe_builddir <command> [argument] >> Available commands: >> use use specified build-dir, setup when local.conf and/or >> bblayers.conf are missing >> setup create default builddir >> avail list possible build-dir's >> layers list layers used in BSP >> repos list repositories used in BSP >> prune prune old builds >> off remove all settings from oe from shell environment >> >> Tells you, what could be expected (very short). >> >> It's all plain shell - so everyone can adopt it easily to local >> requirements. Further, it supports setting flags and tools within >> ''oe_builddir use''. > > I'd say you should look at existing tools, specifically > oe-init-build-env and/or oe-setup-builddir, and add any desired > functionality to them. I did. They don't do so much. It's even not the same concept. And - what is even more important: it is one tool, it does init and setup and much more - for the same thing. It is much easier teach people one tool than teaching them pick the right out of 8. Cheers -- Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
