summaryrefslogtreecommitdiffstats
path: root/meta-skeleton/recipes-multilib/images
diff options
context:
space:
mode:
authorEnrico Scholz <enrico.scholz@sigma-chemnitz.de>2018-02-27 19:46:48 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-03-01 22:13:56 +0000
commit98aff12d9cd104d39cdff815ee0c5194efa438f6 (patch)
tree365b979e639026aa38e779b37ec97356cc283cf5 /meta-skeleton/recipes-multilib/images
parent4118603777ca24be0982bb0893d4902d239ca2a4 (diff)
downloadpoky-98aff12d9cd104d39cdff815ee0c5194efa438f6.tar.gz
oe-init-env: search 'bitbake' outside of oe-core
atm, 'oe-init-build-env' expects 'bitbake' to be within the OE core git repository. This complicates the project setup because you have to manage the 'bitbake' directory or symlink manually (or specify the bitbake location explicitly). Looking for 'bitbake' outside the main git repository will ease project management significantly. Now, you can put everything into git submodules, clone the project with | git clone --recursive ... and continue immediately with | ..../oe-init-build-env E.g. when you had previously | . | |-- build/ | `-- sources/ | `-- org.openembedded.core/ | `-- bitbake -> ../bitbake (where 'bitbake' must be created manually after cloning the project), you can have now | . | |-- build/ | `-- sources/ | |-- bitbake/ | `-- org.openembedded.core/ which is completely managed by 'git'. Patch adds $OEROOT/.. to the search path for 'bitbake' (From OE-Core rev: 5b3afc9cfe38a9fb435fbe5fcabc59b9a60f4657) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-skeleton/recipes-multilib/images')
0 files changed, 0 insertions, 0 deletions