Skip to contentSkip to conversation

arago.conf: switch to internal toolchain for now

PATCH In review Denys Dmytriyenko 2 participants 3 messages May 13, 2022

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 arago.conf: switch to internal toolchain for now

From: Denys Dmytriyenko <[email protected]>

Set default to build and use internal toolchain for now, instead of a pre-built external one, as external gcc-11.2 toolchain still requires some work and syncup with latest meta-arm codebase.

---
 meta-arago-distro/conf/distro/arago.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-arago-distro/conf/distro/arago.conf +1 -1
index b2246537..e24cace9 100644
@@ -170,7 +170,7 @@ IMAGE_FSTYPES:remove = "${@['','ubi ubifs'][d.getVar('ARAGO_SYSTEST_ENABLE') ==
 # Toolchain should be selected by setting TOOLCHAIN_BRAND in local.conf
 # Set some sane defaults, in case someone forgets to set them in local.conf
 TC_SANE_DEFAULT ?= "arm"
-TOOLCHAIN_TYPE ?= "external"
+TOOLCHAIN_TYPE ?= "internal"
 TOOLCHAIN_TYPE:omapl1 = "internal"
 TOOLCHAIN_BRAND ?= "${@[d.getVar('TC_SANE_DEFAULT'),'gcc'][d.getVar('TOOLCHAIN_TYPE') == 'internal']}"
 
Signature · 1 line
2.25.1
#1 lore raw
Quoted 5 lines · Denys Dmytriyenko

From: Denys Dmytriyenko <[email protected]>

Set default to build and use internal toolchain for now, instead of a pre-built external one, as external gcc-11.2 toolchain still requires some work and syncup with latest meta-arm codebase.

I wonder if we should just settle for internal toolchain and dump the entire external toolchain argumentation?

Is'nt that more inline with what the rest of the ecosystem is doing?

Quoted 17 lines
---
 meta-arago-distro/conf/distro/arago.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-arago-distro/conf/distro/arago.conf +1 -1
index b2246537..e24cace9 100644
@@ -170,7 +170,7 @@ IMAGE_FSTYPES:remove = "${@['','ubi ubifs'][d.getVar('ARAGO_SYSTEST_ENABLE') ==
 # Toolchain should be selected by setting TOOLCHAIN_BRAND in local.conf
 # Set some sane defaults, in case someone forgets to set them in local.conf
 TC_SANE_DEFAULT ?= "arm"
-TOOLCHAIN_TYPE ?= "external"
+TOOLCHAIN_TYPE ?= "internal"
 TOOLCHAIN_TYPE:omapl1 = "internal"
 TOOLCHAIN_BRAND ?= "${@[d.getVar('TC_SANE_DEFAULT'),'gcc'][d.getVar('TOOLCHAIN_TYPE') == 'internal']}"
Signature · 3 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
#2 lore raw
Quoted 9 lines · Nishanth Menon
Quoted 5 lines · Denys Dmytriyenko

From: Denys Dmytriyenko <[email protected]>

Set default to build and use internal toolchain for now, instead of a pre-built external one, as external gcc-11.2 toolchain still requires some work and syncup with latest meta-arm codebase.

I wonder if we should just settle for internal toolchain and dump the entire external toolchain argumentation?

Sure, in due time. There were some concerns about using OE toolchain with the SDK, compared to the external toolchain - need to look closer at those.

Quoted 19 lines

Is'nt that more inline with what the rest of the ecosystem is doing?

Quoted 17 lines
---
 meta-arago-distro/conf/distro/arago.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-arago-distro/conf/distro/arago.conf +1 -1
index b2246537..e24cace9 100644
@@ -170,7 +170,7 @@ IMAGE_FSTYPES:remove = "${@['','ubi ubifs'][d.getVar('ARAGO_SYSTEST_ENABLE') ==
 # Toolchain should be selected by setting TOOLCHAIN_BRAND in local.conf
 # Set some sane defaults, in case someone forgets to set them in local.conf
 TC_SANE_DEFAULT ?= "arm"
-TOOLCHAIN_TYPE ?= "external"
+TOOLCHAIN_TYPE ?= "internal"
 TOOLCHAIN_TYPE:omapl1 = "internal"
 TOOLCHAIN_BRAND ?= "${@[d.getVar('TC_SANE_DEFAULT'),'gcc'][d.getVar('TOOLCHAIN_TYPE') == 'internal']}"