Remove unused sample-file bblayers-zeus-browser.conf.sample
PATCH 1/6 Remove unused sample-file bblayers-zeus-browser.conf.sample
--- sample-files/bblayers-zeus-browser.conf.sample | 12 ------------ 1 file changed, 12 deletions(-) delete mode 100644 sample-files/bblayers-zeus-browser.conf.sample
sample-files/bblayers-zeus-browser.conf.sample deleted +0 -12
@@ -1,12 +0,0 @@ -# This template file was created by taking the oe-core/meta/conf/bblayers.conf -# file and removing the BBLAYERS section at the end. - -# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -LCONF_VERSION = "6" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -OVERRIDES = "forcevariable" -LAYERSERIES_COMPAT_browser-layer_forcevariable = "zeus"
Signature · 1 line
2.17.1
PATCH 2/6 Add layers for split meta-ti master branch
The latest master meta-ti split into two layers, add new layers here.
--- configs/arago-master-config.txt | 2 +- configs/distroless-master-config.txt | 2 +- configs/poky-master-config.txt | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
configs/arago-master-config.txt +1 -1
@@ -7,7 +7,7 @@ meta-arago,git://git.yoctoproject.org/meta-arago,master,HEAD,layers=meta-arago-d meta-qt5,https://github.com/meta-qt5/meta-qt5.git,master,HEAD,layers= meta-virtualization,git://git.yoctoproject.org/meta-virtualization,master,HEAD,layers= meta-openembedded,git://git.openembedded.org/meta-openembedded,master,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sample
configs/distroless-master-config.txt +1 -1
@@ -1,7 +1,7 @@ # This file takes repo entries in the format # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] bitbake,git://git.openembedded.org/bitbake,master,HEAD -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sample
configs/poky-master-config.txt +1 -1
@@ -2,7 +2,7 @@ # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] bitbake,git://git.openembedded.org/bitbake,master,HEAD poky,git://git.yoctoproject.org/poky,master,HEAD,layers=meta:meta-poky:meta-yocto-bsp -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain OECORELAYERCONF=./sample-files/bblayers.conf.sample OECORELOCALCONF=./sample-files/local-poky-v2.conf.sample
Signature · 1 line
2.17.1
Re: [meta-arago][oe-layersetup PATCH 2/6] Add layers for split meta-ti master branch
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
The latest master meta-ti split into two layers, add new layers here.
Can you swap the order of layers in meta-ti? Other repos usually have the main repo listed first.
Quoted 48 lines
Signed-off-by Andrew Davis <[email protected]>--- configs/arago-master-config.txt | 2 +- configs/distroless-master-config.txt | 2 +- configs/poky-master-config.txt | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)configs/arago-master-config.txt +1
-1@@ -7,7 +7,7 @@ meta-arago,git://git.yoctoproject.org/meta-arago,master,HEAD,layers=meta-arago-d meta-qt5,https://github.com/meta-qt5/meta-qt5.git,master,HEAD,layers= meta-virtualization,git://git.yoctoproject.org/meta-virtualization,master,HEAD,layers= meta-openembedded,git://git.openembedded.org/meta-openembedded,master,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sampleconfigs/distroless-master-config.txt +1
-1@@ -1,7 +1,7 @@ # This file takes repo entries in the format # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] bitbake,git://git.openembedded.org/bitbake,master,HEAD -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sampleconfigs/poky-master-config.txt +1
-1@@ -2,7 +2,7 @@ # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] bitbake,git://git.openembedded.org/bitbake,master,HEAD poky,git://git.yoctoproject.org/poky,master,HEAD,layers=meta:meta-poky:meta-yocto-bsp -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain OECORELAYERCONF=./sample-files/bblayers.conf.sample OECORELOCALCONF=./sample-files/local-poky-v2.conf.sampleSignature · 1 line
2.17.1
Re: [meta-arago][oe-layersetup PATCH 2/6] Add layers for split meta-ti master branch
Quoted 6 lines · Denys Dmytriyenko
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
The latest master meta-ti split into two layers, add new layers here.
Can you swap the order of layers in meta-ti? Other repos usually have the main repo listed first.
That changes the order they go into to bblayers, don't we want meta-ti-bsp to be the bottom layer?
Andrew
Quoted 49 lines
Quoted 49 lines
Signed-off-by Andrew Davis <[email protected]>--- configs/arago-master-config.txt | 2 +- configs/distroless-master-config.txt | 2 +- configs/poky-master-config.txt | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)configs/arago-master-config.txt +1
-1@@ -7,7 +7,7 @@ meta-arago,git://git.yoctoproject.org/meta-arago,master,HEAD,layers=meta-arago-d meta-qt5,https://github.com/meta-qt5/meta-qt5.git,master,HEAD,layers= meta-virtualization,git://git.yoctoproject.org/meta-virtualization,master,HEAD,layers= meta-openembedded,git://git.openembedded.org/meta-openembedded,master,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sampleconfigs/distroless-master-config.txt +1
-1@@ -1,7 +1,7 @@ # This file takes repo entries in the format # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] bitbake,git://git.openembedded.org/bitbake,master,HEAD -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sampleconfigs/poky-master-config.txt +1
-1@@ -2,7 +2,7 @@ # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] bitbake,git://git.openembedded.org/bitbake,master,HEAD poky,git://git.yoctoproject.org/poky,master,HEAD,layers=meta:meta-poky:meta-yocto-bsp -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain OECORELAYERCONF=./sample-files/bblayers.conf.sample OECORELOCALCONF=./sample-files/local-poky-v2.conf.sampleSignature · 1 line
2.17.1
Denys Dmytriyenko
Reviewed-byRe: [meta-arago][oe-layersetup PATCH 2/6] Add layers for split meta-ti master branch
Quoted 10 lines · Andrew Davis
Quoted 5 lines · Denys Dmytriyenko
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
The latest master meta-ti split into two layers, add new layers here.
Can you swap the order of layers in meta-ti? Other repos usually have the main repo listed first.
That changes the order they go into to bblayers, don't we want meta-ti-bsp to be the bottom layer?
Right, the order of entries in bblayers.conf affects the way "shadowed" config files are parsed/visible.
So, if you eventually want a same-named config file from meta-ti-extras to override the same config file from meta-ti-bsp, then this order is correct. But I'd be very cautious overriding each other config files from layers in the same repo...
Anyway, I retract my comment:
Signature · 1 line
Denys
Quoted 50 lines
Quoted 49 lines
Quoted 49 lines
Signed-off-by Andrew Davis <[email protected]>--- configs/arago-master-config.txt | 2 +- configs/distroless-master-config.txt | 2 +- configs/poky-master-config.txt | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)configs/arago-master-config.txt +1
-1@@ -7,7 +7,7 @@ meta-arago,git://git.yoctoproject.org/meta-arago,master,HEAD,layers=meta-arago-d meta-qt5,https://github.com/meta-qt5/meta-qt5.git,master,HEAD,layers= meta-virtualization,git://git.yoctoproject.org/meta-virtualization,master,HEAD,layers= meta-openembedded,git://git.openembedded.org/meta-openembedded,master,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sampleconfigs/distroless-master-config.txt +1
-1@@ -1,7 +1,7 @@ # This file takes repo entries in the format # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] bitbake,git://git.openembedded.org/bitbake,master,HEAD -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sampleconfigs/poky-master-config.txt +1
-1@@ -2,7 +2,7 @@ # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] bitbake,git://git.openembedded.org/bitbake,master,HEAD poky,git://git.yoctoproject.org/poky,master,HEAD,layers=meta:meta-poky:meta-yocto-bsp -meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers= +meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain OECORELAYERCONF=./sample-files/bblayers.conf.sample OECORELOCALCONF=./sample-files/local-poky-v2.conf.sampleSignature · 1 line
2.17.1
PATCH 3/6 Remove image-prelink from sample USER_CLASSES
In reply to Andrew DavisPrelinking hasn't worked on ARM in a while so this class was removed in the latests core master. Remove it here.
--- sample-files/local-arago64-v2.conf.sample | 4 +--- sample-files/local-poky-v2.conf.sample | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-)
sample-files/local-arago64-v2.conf.sample +1 -3
@@ -112,11 +112,9 @@ EXTRA_IMAGE_FEATURES = "debug-tweaks" # enable extra features. Some available options which can be included in this variable # are: # - 'buildstats' collect build statistics -# - 'image-prelink' in order to prelink the filesystem image # - 'image-swab' to perform host system intrusion detection -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-prelink" +USER_CLASSES ?= "buildstats" # By default disable interactive patch resolution (tasks will just fail instead): PATCHRESOLVE = "noop"
sample-files/local-poky-v2.conf.sample +1 -3
@@ -109,11 +109,9 @@ EXTRA_IMAGE_FEATURES = "debug-tweaks" # enable extra features. Some available options which can be included in this variable # are: # - 'buildstats' collect build statistics -# - 'image-prelink' in order to prelink the filesystem image # - 'image-swab' to perform host system intrusion detection -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-prelink" +USER_CLASSES ?= "buildstats" # By default disable interactive patch resolution (tasks will just fail instead): PATCHRESOLVE = "noop"
Signature · 1 line
2.17.1
Re: [meta-arago][oe-layersetup PATCH 3/6] Remove image-prelink from sample USER_CLASSES
Quoted 2 lines · Andrew F. Davis via lists.yoctoproject.org
Prelinking hasn't worked on ARM in a while so this class was removed in the latests core master. Remove it here.
This file is used for both dunfell and master. Maybe this change calls for v3 of the corresponding sample files?
Quoted 42 lines
Signed-off-by Andrew Davis <[email protected]>--- sample-files/local-arago64-v2.conf.sample | 4 +--- sample-files/local-poky-v2.conf.sample | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-)sample-files/local-arago64-v2.conf.sample +1
-3@@ -112,11 +112,9 @@ EXTRA_IMAGE_FEATURES = "debug-tweaks" # enable extra features. Some available options which can be included in this variable # are: # - 'buildstats' collect build statistics -# - 'image-prelink' in order to prelink the filesystem image # - 'image-swab' to perform host system intrusion detection -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-prelink" +USER_CLASSES ?= "buildstats" # By default disable interactive patch resolution (tasks will just fail instead): PATCHRESOLVE = "noop"sample-files/local-poky-v2.conf.sample +1
-3@@ -109,11 +109,9 @@ EXTRA_IMAGE_FEATURES = "debug-tweaks" # enable extra features. Some available options which can be included in this variable # are: # - 'buildstats' collect build statistics -# - 'image-prelink' in order to prelink the filesystem image # - 'image-swab' to perform host system intrusion detection -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-prelink" +USER_CLASSES ?= "buildstats" # By default disable interactive patch resolution (tasks will just fail instead): PATCHRESOLVE = "noop"Signature · 1 line
2.17.1
Re: [meta-arago][oe-layersetup PATCH 3/6] Remove image-prelink from sample USER_CLASSES
Quoted 7 lines · Denys Dmytriyenko
Quoted 2 lines · Andrew F. Davis via lists.yoctoproject.org
Prelinking hasn't worked on ARM in a while so this class was removed in the latests core master. Remove it here.
This file is used for both dunfell and master. Maybe this change calls for v3 of the corresponding sample files?
I only see these v2 files referenced in master configs.
Andrew
Quoted 43 lines
Quoted 43 lines
Signed-off-by Andrew Davis <[email protected]>--- sample-files/local-arago64-v2.conf.sample | 4 +--- sample-files/local-poky-v2.conf.sample | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-)sample-files/local-arago64-v2.conf.sample +1
-3@@ -112,11 +112,9 @@ EXTRA_IMAGE_FEATURES = "debug-tweaks" # enable extra features. Some available options which can be included in this variable # are: # - 'buildstats' collect build statistics -# - 'image-prelink' in order to prelink the filesystem image # - 'image-swab' to perform host system intrusion detection -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-prelink" +USER_CLASSES ?= "buildstats" # By default disable interactive patch resolution (tasks will just fail instead): PATCHRESOLVE = "noop"sample-files/local-poky-v2.conf.sample +1
-3@@ -109,11 +109,9 @@ EXTRA_IMAGE_FEATURES = "debug-tweaks" # enable extra features. Some available options which can be included in this variable # are: # - 'buildstats' collect build statistics -# - 'image-prelink' in order to prelink the filesystem image # - 'image-swab' to perform host system intrusion detection -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-prelink" +USER_CLASSES ?= "buildstats" # By default disable interactive patch resolution (tasks will just fail instead): PATCHRESOLVE = "noop"Signature · 1 line
2.17.1
Denys Dmytriyenko
Reviewed-byRe: [meta-arago][oe-layersetup PATCH 3/6] Remove image-prelink from sample USER_CLASSES
Quoted 11 lines · Andrew Davis via lists.yoctoproject.org
Quoted 7 lines · Denys Dmytriyenko
Quoted 2 lines · Andrew F. Davis via lists.yoctoproject.org
Prelinking hasn't worked on ARM in a while so this class was removed in the latests core master. Remove it here.
This file is used for both dunfell and master. Maybe this change calls for v3 of the corresponding sample files?
I only see these v2 files referenced in master configs.
Ah, v2 wasn't that old and was still not used in dunfell (it felt like eternity for some reason):
https://lists.yoctoproject.org/g/meta-arago/message/13289
Ok, no need for v3:
Quoted 40 lines
Quoted 40 lines
Quoted 40 lines
Signed-off-by Andrew Davis <[email protected]>--- sample-files/local-arago64-v2.conf.sample | 4 +--- sample-files/local-poky-v2.conf.sample | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-)sample-files/local-arago64-v2.conf.sample +1
-3@@ -112,11 +112,9 @@ EXTRA_IMAGE_FEATURES = "debug-tweaks" # enable extra features. Some available options which can be included in this variable # are: # - 'buildstats' collect build statistics -# - 'image-prelink' in order to prelink the filesystem image # - 'image-swab' to perform host system intrusion detection -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-prelink" +USER_CLASSES ?= "buildstats" # By default disable interactive patch resolution (tasks will just fail instead): PATCHRESOLVE = "noop"sample-files/local-poky-v2.conf.sample +1
-3@@ -109,11 +109,9 @@ EXTRA_IMAGE_FEATURES = "debug-tweaks" # enable extra features. Some available options which can be included in this variable # are: # - 'buildstats' collect build statistics -# - 'image-prelink' in order to prelink the filesystem image # - 'image-swab' to perform host system intrusion detection -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-prelink" +USER_CLASSES ?= "buildstats" # By default disable interactive patch resolution (tasks will just fail instead): PATCHRESOLVE = "noop"Signature · 1 line
2.17.1
PATCH 4/6 Rename BB_ENV_EXTRAWHITE to BB_ENV_PASSTHROUGH_ADDITIONS
In reply to Andrew DavisThis variable was renamed upstream, rename it in our setenv file.
--- oe-layertool-setup.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
oe-layertool-setup.sh +1 -1
@@ -853,7 +853,7 @@ unset BITBAKEDIR unset SCRIPTS export PATH export BUILDDIR=${builddir} -export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD SOCKS5_USER OEBASE META_SDK_PATH TOOLCHAIN_TYPE TOOLCHAIN_BRAND TOOLCHAIN_BASE TOOLCHAIN_PATH TOOLCHAIN_PATH_ARMV5 TOOLCHAIN_PATH_ARMV7 TOOLCHAIN_PATH_ARMV8 EXTRA_TISDK_FILES TISDK_VERSION ARAGO_BRAND ARAGO_RT_ENABLE ARAGO_SYSTEST_ENABLE ARAGO_KERNEL_SUFFIX TI_SECURE_DEV_PKG_CAT TI_SECURE_DEV_PKG_AUTO TI_SECURE_DEV_PKG_K3 ARAGO_SYSVINIT SYSFW_FILE" +export BB_ENV_PASSTHROUGH_ADDITIONS="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD SOCKS5_USER OEBASE META_SDK_PATH TOOLCHAIN_TYPE TOOLCHAIN_BRAND TOOLCHAIN_BASE TOOLCHAIN_PATH TOOLCHAIN_PATH_ARMV5 TOOLCHAIN_PATH_ARMV7 TOOLCHAIN_PATH_ARMV8 EXTRA_TISDK_FILES TISDK_VERSION ARAGO_BRAND ARAGO_RT_ENABLE ARAGO_SYSTEST_ENABLE ARAGO_KERNEL_SUFFIX TI_SECURE_DEV_PKG_CAT TI_SECURE_DEV_PKG_AUTO TI_SECURE_DEV_PKG_K3 ARAGO_SYSVINIT SYSFW_FILE" EOM }
Signature · 1 line
2.17.1
Re: [meta-arago][oe-layersetup PATCH 4/6] Rename BB_ENV_EXTRAWHITE to BB_ENV_PASSTHROUGH_ADDITIONS
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
This variable was renamed upstream, rename it in our setenv file.
This will break dunfell...
Quoted 17 lines
Signed-off-by Andrew Davis <[email protected]>--- oe-layertool-setup.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)oe-layertool-setup.sh +1
-1@@ -853,7 +853,7 @@ unset BITBAKEDIR unset SCRIPTS export PATH export BUILDDIR=${builddir} -export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD SOCKS5_USER OEBASE META_SDK_PATH TOOLCHAIN_TYPE TOOLCHAIN_BRAND TOOLCHAIN_BASE TOOLCHAIN_PATH TOOLCHAIN_PATH_ARMV5 TOOLCHAIN_PATH_ARMV7 TOOLCHAIN_PATH_ARMV8 EXTRA_TISDK_FILES TISDK_VERSION ARAGO_BRAND ARAGO_RT_ENABLE ARAGO_SYSTEST_ENABLE ARAGO_KERNEL_SUFFIX TI_SECURE_DEV_PKG_CAT TI_SECURE_DEV_PKG_AUTO TI_SECURE_DEV_PKG_K3 ARAGO_SYSVINIT SYSFW_FILE" +export BB_ENV_PASSTHROUGH_ADDITIONS="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD SOCKS5_USER OEBASE META_SDK_PATH TOOLCHAIN_TYPE TOOLCHAIN_BRAND TOOLCHAIN_BASE TOOLCHAIN_PATH TOOLCHAIN_PATH_ARMV5 TOOLCHAIN_PATH_ARMV7 TOOLCHAIN_PATH_ARMV8 EXTRA_TISDK_FILES TISDK_VERSION ARAGO_BRAND ARAGO_RT_ENABLE ARAGO_SYSTEST_ENABLE ARAGO_KERNEL_SUFFIX TI_SECURE_DEV_PKG_CAT TI_SECURE_DEV_PKG_AUTO TI_SECURE_DEV_PKG_K3 ARAGO_SYSVINIT SYSFW_FILE" EOM }
Re: [meta-arago][oe-layersetup PATCH 4/6] Rename BB_ENV_EXTRAWHITE to BB_ENV_PASSTHROUGH_ADDITIONS
Quoted 5 lines · Denys Dmytriyenko
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
This variable was renamed upstream, rename it in our setenv file.
This will break dunfell...
And not doing it breaks master...
There is a check for BB_ENV_EXTRAWHITE, having it set will halt build (think the check is in bitbake but haven't looked).
Quoted 18 lines
Quoted 18 lines
Signed-off-by Andrew Davis <[email protected]>--- oe-layertool-setup.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)oe-layertool-setup.sh +1
-1@@ -853,7 +853,7 @@ unset BITBAKEDIR unset SCRIPTS export PATH export BUILDDIR=${builddir} -export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD SOCKS5_USER OEBASE META_SDK_PATH TOOLCHAIN_TYPE TOOLCHAIN_BRAND TOOLCHAIN_BASE TOOLCHAIN_PATH TOOLCHAIN_PATH_ARMV5 TOOLCHAIN_PATH_ARMV7 TOOLCHAIN_PATH_ARMV8 EXTRA_TISDK_FILES TISDK_VERSION ARAGO_BRAND ARAGO_RT_ENABLE ARAGO_SYSTEST_ENABLE ARAGO_KERNEL_SUFFIX TI_SECURE_DEV_PKG_CAT TI_SECURE_DEV_PKG_AUTO TI_SECURE_DEV_PKG_K3 ARAGO_SYSVINIT SYSFW_FILE" +export BB_ENV_PASSTHROUGH_ADDITIONS="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD SOCKS5_USER OEBASE META_SDK_PATH TOOLCHAIN_TYPE TOOLCHAIN_BRAND TOOLCHAIN_BASE TOOLCHAIN_PATH TOOLCHAIN_PATH_ARMV5 TOOLCHAIN_PATH_ARMV7 TOOLCHAIN_PATH_ARMV8 EXTRA_TISDK_FILES TISDK_VERSION ARAGO_BRAND ARAGO_RT_ENABLE ARAGO_SYSTEST_ENABLE ARAGO_KERNEL_SUFFIX TI_SECURE_DEV_PKG_CAT TI_SECURE_DEV_PKG_AUTO TI_SECURE_DEV_PKG_K3 ARAGO_SYSVINIT SYSFW_FILE" EOM }
Re: [meta-arago][oe-layersetup PATCH 4/6] Rename BB_ENV_EXTRAWHITE to BB_ENV_PASSTHROUGH_ADDITIONS
Quoted 4 lines · Andrew Davis
Quoted 3 lines · Denys Dmytriyenko
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
This variable was renamed upstream, rename it in our setenv file.
Quoted 9 lines
Quoted 2 lines
This will break dunfell...
And not doing it breaks master...
There is a check for
BB_ENV_EXTRAWHITE, having it set will halt build (think the check is in bitbake but haven't looked).
This one patch seems to be the only hold out. We clearly cannot break our current production. Do you want to resubmit the series without this patch and we can keep looking in this issue separately?
Quoted 20 lines
Quoted 20 lines
Quoted 20 lines
Signed-off-by Andrew Davis <[email protected]>---
oe-layertool-setup.sh| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)oe-layertool-setup.sh +0
-0@@ -853,7 +853,7 @@ unset BITBAKEDIRunset SCRIPTS
export PATH
export BUILDDIR=${builddir}
-export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBChttp_proxyftp_proxyhttps_proxyall_proxyALL_PROXYno_proxySSH_AGENT_PIDSSH_AUTH_SOCKBB_SRCREV_POLICYSDKMACHINEBB_NUMBER_THREADSPARALLEL_MAKEGIT_PROXY_COMMANDGIT_PROXY_IGNORESOCKS5_PASSWDSOCKS5_USEROEBASEMETA_SDK_PATHTOOLCHAIN_TYPETOOLCHAIN_BRANDTOOLCHAIN_BASETOOLCHAIN_PATHTOOLCHAIN_PATH_ARMV5TOOLCHAIN_PATH_ARMV7TOOLCHAIN_PATH_ARMV8EXTRA_TISDK_FILESTISDK_VERSIONARAGO_BRANDARAGO_RT_ENABLEARAGO_SYSTEST_ENABLEARAGO_KERNEL_SUFFIXTI_SECURE_DEV_PKG_CATTI_SECURE_DEV_PKG_AUTOTI_SECURE_DEV_PKG_K3ARAGO_SYSVINITSYSFW_FILE" +export BB_ENV_PASSTHROUGH_ADDITIONS="MACHINE DISTRO TCMODE TCLIBChttp_proxyftp_proxyhttps_proxyall_proxyALL_PROXYno_proxySSH_AGENT_PIDSSH_AUTH_SOCKBB_SRCREV_POLICYSDKMACHINEBB_NUMBER_THREADSPARALLEL_MAKEGIT_PROXY_COMMANDGIT_PROXY_IGNORESOCKS5_PASSWDSOCKS5_USEROEBASEMETA_SDK_PATHTOOLCHAIN_TYPETOOLCHAIN_BRANDTOOLCHAIN_BASETOOLCHAIN_PATHTOOLCHAIN_PATH_ARMV5TOOLCHAIN_PATH_ARMV7TOOLCHAIN_PATH_ARMV8EXTRA_TISDK_FILESTISDK_VERSIONARAGO_BRANDARAGO_RT_ENABLEARAGO_SYSTEST_ENABLEARAGO_KERNEL_SUFFIXTI_SECURE_DEV_PKG_CATTI_SECURE_DEV_PKG_AUTOTI_SECURE_DEV_PKG_K3ARAGO_SYSVINITSYSFW_FILE" EOM
}
Signature · 3 lines
Ryan Eatmon [email protected] ----------------------------------------- Texas Instruments, Inc. - LCPD - MGTS
Re: [meta-arago][oe-layersetup PATCH 4/6] Rename BB_ENV_EXTRAWHITE to BB_ENV_PASSTHROUGH_ADDITIONS
Quoted 10 lines · Ryan Eatmon
Quoted 8 lines · Andrew Davis
Quoted 5 lines · Denys Dmytriyenko
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
This variable was renamed upstream, rename it in our setenv file.
This will break dunfell...
Quoted 9 lines
Quoted 5 lines
And not doing it breaks master...
There is a check for
BB_ENV_EXTRAWHITE, having it set will halt build (think the check is in bitbake but haven't looked).This one patch seems to be the only hold out. We clearly cannot break our current production. Do you want to resubmit the series without this patch and we can keep looking in this issue separately?
Not sure what your tooling looks like, but could you just take all the other patch in this series skipping this one?
Or do you need a full resend?
Andrew
Quoted 20 lines
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Signed-off-by Andrew Davis <[email protected]>---
oe-layertool-setup.sh| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)oe-layertool-setup.sh +0
-0@@ -853,7 +853,7 @@ unset BITBAKEDIRunset SCRIPTS
export PATH
export BUILDDIR=${builddir}oe-layertool-setup.sh +1
-1-export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD SOCKS5_USER OEBASE META_SDK_PATH TOOLCHAIN_TYPE TOOLCHAIN_BRAND TOOLCHAIN_BASE TOOLCHAIN_PATH TOOLCHAIN_PATH_ARMV5 TOOLCHAIN_PATH_ARMV7 TOOLCHAIN_PATH_ARMV8 EXTRA_TISDK_FILES TISDK_VERSION ARAGO_BRAND ARAGO_RT_ENABLE ARAGO_SYSTEST_ENABLE ARAGO_KERNEL_SUFFIX TI_SECURE_DEV_PKG_CAT TI_SECURE_DEV_PKG_AUTO TI_SECURE_DEV_PKG_K3 ARAGO_SYSVINIT SYSFW_FILE" +export BB_ENV_PASSTHROUGH_ADDITIONS="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD SOCKS5_USER OEBASE META_SDK_PATH TOOLCHAIN_TYPE TOOLCHAIN_BRAND TOOLCHAIN_BASE TOOLCHAIN_PATH TOOLCHAIN_PATH_ARMV5 TOOLCHAIN_PATH_ARMV7 TOOLCHAIN_PATH_ARMV8 EXTRA_TISDK_FILES TISDK_VERSION ARAGO_BRAND ARAGO_RT_ENABLE ARAGO_SYSTEST_ENABLE ARAGO_KERNEL_SUFFIX TI_SECURE_DEV_PKG_CAT TI_SECURE_DEV_PKG_AUTO TI_SECURE_DEV_PKG_K3 ARAGO_SYSVINIT SYSFW_FILE"EOM
}
Re: [meta-arago][oe-layersetup PATCH 4/6] Rename BB_ENV_EXTRAWHITE to BB_ENV_PASSTHROUGH_ADDITIONS
Quoted 22 lines · Andrew Davis
Quoted 10 lines · Ryan Eatmon
Quoted 8 lines · Andrew Davis
Quoted 5 lines · Denys Dmytriyenko
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
This variable was renamed upstream, rename it in our setenv file.
This will break dunfell...
Quoted 9 lines
Quoted 5 lines
And not doing it breaks master...
There is a check for
BB_ENV_EXTRAWHITE, having it set will halt build (think the check is in bitbake but haven't looked).This one patch seems to be the only hold out. We clearly cannot break our current production. Do you want to resubmit the series without this patch and we can keep looking in this issue separately?
Quoted 4 lines
Not sure what your tooling looks like, but could you just take all the other patch in this series skipping this one?
Or do you need a full resend?
Full resend as v2 would be best. Cleanest for the mailing list history and for Patchwork.
Quoted 25 lines
Andrew
Quoted 22 lines
Quoted 21 lines
Quoted 21 lines
Quoted 21 lines
Signed-off-by Andrew Davis <[email protected]>---
oe-layertool-setup.sh| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)oe-layertool-setup.sh +0
-0@@ -853,7 +853,7 @@ unset BITBAKEDIRunset SCRIPTS
export PATH
export BUILDDIR=${builddir}
-export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBChttp_proxyftp_proxyhttps_proxyall_proxyALL_PROXYno_proxySSH_AGENT_PIDSSH_AUTH_SOCKBB_SRCREV_POLICYSDKMACHINEBB_NUMBER_THREADSPARALLEL_MAKEGIT_PROXY_COMMANDGIT_PROXY_IGNORESOCKS5_PASSWDSOCKS5_USEROEBASEMETA_SDK_PATHTOOLCHAIN_TYPETOOLCHAIN_BRANDTOOLCHAIN_BASETOOLCHAIN_PATHTOOLCHAIN_PATH_ARMV5TOOLCHAIN_PATH_ARMV7TOOLCHAIN_PATH_ARMV8EXTRA_TISDK_FILESTISDK_VERSIONARAGO_BRANDARAGO_RT_ENABLEARAGO_SYSTEST_ENABLEARAGO_KERNEL_SUFFIXTI_SECURE_DEV_PKG_CATTI_SECURE_DEV_PKG_AUTOTI_SECURE_DEV_PKG_K3ARAGO_SYSVINITSYSFW_FILE" +export BB_ENV_PASSTHROUGH_ADDITIONS="MACHINE DISTRO TCMODE TCLIBChttp_proxyftp_proxyhttps_proxyall_proxyALL_PROXYno_proxySSH_AGENT_PIDSSH_AUTH_SOCKBB_SRCREV_POLICYSDKMACHINEBB_NUMBER_THREADSPARALLEL_MAKEGIT_PROXY_COMMANDGIT_PROXY_IGNORESOCKS5_PASSWDSOCKS5_USEROEBASEMETA_SDK_PATHTOOLCHAIN_TYPETOOLCHAIN_BRANDTOOLCHAIN_BASETOOLCHAIN_PATHTOOLCHAIN_PATH_ARMV5TOOLCHAIN_PATH_ARMV7TOOLCHAIN_PATH_ARMV8EXTRA_TISDK_FILESTISDK_VERSIONARAGO_BRANDARAGO_RT_ENABLEARAGO_SYSTEST_ENABLEARAGO_KERNEL_SUFFIXTI_SECURE_DEV_PKG_CATTI_SECURE_DEV_PKG_AUTOTI_SECURE_DEV_PKG_K3ARAGO_SYSVINITSYSFW_FILE" EOM
}
Signature · 3 lines
Ryan Eatmon [email protected] ----------------------------------------- Texas Instruments, Inc. - LCPD - MGTS
PATCH 5/6 Build Poky in a directory named poky-tmp vs arago-tmp
In reply to Andrew DavisThis also allows us to keep version of both should we need.
--- sample-files/local-poky-v2.conf.sample | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sample-files/local-poky-v2.conf.sample +1 -1
@@ -48,7 +48,7 @@ SSTATE_DIR = "${OEBASE}/build/sstate-cache" # where BitBake should place its temporary files and output. Keep in mind that # this includes the extraction and compilation of many applications and the toolchain # which can use Gigabytes of hard disk space. -TMPDIR = "${OEBASE}/build/arago-tmp" +TMPDIR = "${OEBASE}/build/poky-tmp" # # Machine Selection
Signature · 1 line
2.17.1
Re: [meta-arago][oe-layersetup PATCH 5/6] Build Poky in a directory named poky-tmp vs arago-tmp
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
This also allows us to keep version of both should we need.
I'm fine with the change, although it's really a NOOP, as TMPDIR gets replaced by tisdk-build-scripts, Jenkins jobs and even a distro config... But for consistency, it's fine.
Quoted 20 lines
Signed-off-by Andrew Davis <[email protected]>--- sample-files/local-poky-v2.conf.sample | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)sample-files/local-poky-v2.conf.sample +1
-1@@ -48,7 +48,7 @@ SSTATE_DIR = "${OEBASE}/build/sstate-cache" # where BitBake should place its temporary files and output. Keep in mind that # this includes the extraction and compilation of many applications and the toolchain # which can use Gigabytes of hard disk space. -TMPDIR = "${OEBASE}/build/arago-tmp" +TMPDIR = "${OEBASE}/build/poky-tmp" # # Machine SelectionSignature · 1 line
2.17.1
Re: [meta-arago][oe-layersetup PATCH 5/6] Build Poky in a directory named poky-tmp vs arago-tmp
Quoted 7 lines · Denys Dmytriyenko
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
This also allows us to keep version of both should we need.
I'm fine with the change, although it's really a NOOP, as TMPDIR gets replaced by tisdk-build-scripts, Jenkins jobs and even a distro config... But for consistency, it's fine.
I'm not a build script nor a Jenkins job :) so this *does* change the behavior for me building on my local desktop. (Poky doesn't change this in distro config).
Andrew
Quoted 21 lines
Quoted 21 lines
Signed-off-by Andrew Davis <[email protected]>--- sample-files/local-poky-v2.conf.sample | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)sample-files/local-poky-v2.conf.sample +1
-1@@ -48,7 +48,7 @@ SSTATE_DIR = "${OEBASE}/build/sstate-cache" # where BitBake should place its temporary files and output. Keep in mind that # this includes the extraction and compilation of many applications and the toolchain # which can use Gigabytes of hard disk space. -TMPDIR = "${OEBASE}/build/arago-tmp" +TMPDIR = "${OEBASE}/build/poky-tmp" # # Machine SelectionSignature · 1 line
2.17.1
PATCH 6/6 Build Poky using meta-yocto instead of combined poky repo
In reply to Andrew DavisThe Poky repo contains meta-yocto plus extra bits needed for an all-in-one build, but since we already pull in tools with this script like bitbake and oe-core, lets use those and save some space/bandwidth.
--- configs/poky-master-config.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
configs/poky-master-config.txt +3 -1
@@ -1,8 +1,10 @@ # This file takes repo entries in the format # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] + bitbake,git://git.openembedded.org/bitbake,master,HEAD -poky,git://git.yoctoproject.org/poky,master,HEAD,layers=meta:meta-poky:meta-yocto-bsp +meta-yocto,git://git.yoctoproject.org/meta-yocto,master,HEAD,layers=meta-poky:meta-yocto-bsp meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain +oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sample OECORELOCALCONF=./sample-files/local-poky-v2.conf.sample
Signature · 1 line
2.17.1
Re: [meta-arago][oe-layersetup PATCH 6/6] Build Poky using meta-yocto instead of combined poky repo
Quoted 4 lines · Andrew F. Davis via lists.yoctoproject.org
The Poky repo contains meta-yocto plus extra bits needed for an all-in-one build, but since we already pull in tools with this script like bitbake and oe-core, lets use those and save some space/bandwidth.
There are other nuances of "flattened" Poky repo (commits are different, plus some other minor bits and pieces). The only overhead is to clone Bitbake twice (not OE-Core), which is neglectable and allows building the true Poky, instead of OE-Core + meta-yocto/meta-poky... :)
Quoted 23 lines
Signed-off-by Andrew Davis <[email protected]>--- configs/poky-master-config.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)configs/poky-master-config.txt +3
-1@@ -1,8 +1,10 @@ # This file takes repo entries in the format # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] + bitbake,git://git.openembedded.org/bitbake,master,HEAD -poky,git://git.yoctoproject.org/poky,master,HEAD,layers=meta:meta-poky:meta-yocto-bsp +meta-yocto,git://git.yoctoproject.org/meta-yocto,master,HEAD,layers=meta-poky:meta-yocto-bsp meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain +oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sample OECORELOCALCONF=./sample-files/local-poky-v2.conf.sampleSignature · 1 line
2.17.1
Re: [meta-arago][oe-layersetup PATCH 6/6] Build Poky using meta-yocto instead of combined poky repo
Quoted 11 lines · Denys Dmytriyenko
Quoted 4 lines · Andrew F. Davis via lists.yoctoproject.org
The Poky repo contains meta-yocto plus extra bits needed for an all-in-one build, but since we already pull in tools with this script like bitbake and oe-core, lets use those and save some space/bandwidth.
There are other nuances of "flattened" Poky repo (commits are different, plus some other minor bits and pieces). The only overhead is to clone Bitbake twice (not OE-Core), which is neglectable and allows building the true Poky, instead of OE-Core + meta-yocto/meta-poky... :)
Could you let me know what the other "minor bits and pieces" we are concerned about losing here? It seems the "flattened" Poky repo is an automatic merge of Bitbake + OE-Core + meta-yocto/meta-poky + some random scripts we don't care about since we do the same thing here in oe-layersetup.
If we want "true" Poky, then we just clone flattened Poky and don't need oe-layersetup at all here.
Andrew
Quoted 24 lines
Quoted 24 lines
Signed-off-by Andrew Davis <[email protected]>--- configs/poky-master-config.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)configs/poky-master-config.txt +3
-1@@ -1,8 +1,10 @@ # This file takes repo entries in the format # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] + bitbake,git://git.openembedded.org/bitbake,master,HEAD -poky,git://git.yoctoproject.org/poky,master,HEAD,layers=meta:meta-poky:meta-yocto-bsp +meta-yocto,git://git.yoctoproject.org/meta-yocto,master,HEAD,layers=meta-poky:meta-yocto-bsp meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain +oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sample OECORELOCALCONF=./sample-files/local-poky-v2.conf.sampleSignature · 1 line
2.17.1
Re: [meta-arago][oe-layersetup PATCH 6/6] Build Poky using meta-yocto instead of combined poky repo
Quoted 14 lines · Andrew Davis
Quoted 11 lines · Denys Dmytriyenko
Quoted 4 lines · Andrew F. Davis via lists.yoctoproject.org
The Poky repo contains meta-yocto plus extra bits needed for an all-in-one build, but since we already pull in tools with this script like bitbake and oe-core, lets use those and save some space/bandwidth.
There are other nuances of "flattened" Poky repo (commits are different, plus some other minor bits and pieces). The only overhead is to clone Bitbake twice (not OE-Core), which is neglectable and allows building the true Poky, instead of OE-Core + meta-yocto/meta-poky... :)
Quoted 7 lines
Could you let me know what the other "minor bits and pieces" we are concerned about losing here? It seems the "flattened" Poky repo is an automatic merge of Bitbake + OE-Core + meta-yocto/meta-poky + some random scripts we don't care about since we do the same thing here in oe-layersetup.
If we want "true" Poky, then we just clone flattened Poky and don't need oe-layersetup at all here.
Yeah, the biggest difference is all the different commit IDs between all those layers due to running combo-layer tool, which I don't believe runs automatically anyway. And, sure, combo-layer was one of the ways to do layer setup, vs. oe-layersetup tool. But since I wanted to do Poky builds with meta-ti on the same build farm with Arago, which uses tisdk-build-scripts and oe-layersetup, adding this config back then was the simplest approach. And if this is no longer used/needed, you can definitely change or remove it...
Quoted 23 lines
Quoted 23 lines
Quoted 23 lines
Signed-off-by Andrew Davis <[email protected]>--- configs/poky-master-config.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)configs/poky-master-config.txt +3
-1@@ -1,8 +1,10 @@ # This file takes repo entries in the format # repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] + bitbake,git://git.openembedded.org/bitbake,master,HEAD -poky,git://git.yoctoproject.org/poky,master,HEAD,layers=meta:meta-poky:meta-yocto-bsp +meta-yocto,git://git.yoctoproject.org/meta-yocto,master,HEAD,layers=meta-poky:meta-yocto-bsp meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=meta-ti-extras:meta-ti-bsp meta-arm,git://git.yoctoproject.org/meta-arm,master,HEAD,layers=meta-arm:meta-arm-toolchain +oe-core,git://git.openembedded.org/openembedded-core,master,HEAD,layers=meta OECORELAYERCONF=./sample-files/bblayers.conf.sample OECORELOCALCONF=./sample-files/local-poky-v2.conf.sampleSignature · 1 line
2.17.1
Quoted 1 line · Andrew F. Davis via lists.yoctoproject.org
Signed-off-by Andrew Davis <[email protected]>
Yeah, all zeus configs were removed, no need for this snippet either:
Quoted 25 lines
--- sample-files/bblayers-zeus-browser.conf.sample | 12 ------------ 1 file changed, 12 deletions(-) delete mode 100644 sample-files/bblayers-zeus-browser.conf.samplesample-files/bblayers-zeus-browser.conf.sample deleted +0
-12@@ -1,12 +0,0 @@ -# This template file was created by taking the oe-core/meta/conf/bblayers.conf -# file and removing the BBLAYERS section at the end. - -# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -LCONF_VERSION = "6" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -OVERRIDES = "forcevariable" -LAYERSERIES_COMPAT_browser-layer_forcevariable = "zeus"Signature · 1 line
2.17.1