On Jun 25, 2016 8:30 AM, "akuster808" [off-list ref] wrote:

On 06/22/2016 10:21 AM, Khem Raj wrote:

quoted

quoted

On Jun 22, 2016, at 10:05 AM, akuster808 [off-list ref] wrote:



On 06/22/2016 09:52 AM, Khem Raj wrote:

quoted

quoted

On Jun 22, 2016, at 8:29 AM, Armin Kuster [off-list ref]

wrote:

quoted

quoted

quoted

quoted

Since there are two gcc versions supported and any number of tcglibc,
it would be nice to know which ones are being used.
Add those to the build summary.

Build summary
TCLIBC            = “glibc"

libc is evident from TARGET_SYS

TARGET_SYS="x86_64-oe-linux", this is not the my intent.


The intent is to track which libc is being used. I changed TCLIBC =
"musl" local.conf and now build summary show.

TCLIBC            = "musl"
GCC_VERSION       = "6.1"

Is there a clearer / better way to display this?

if you set TCLIBC = “musl” then TARGET_SYS should have changed to

x86_64-oe-linux-musl

quoted

and TARGET_SYS is displayed with build configuration.

Ah, ok. now I get it.

Would TCMODE be more useful?

Probably if external toolchain vendor versions are similar to internal
toolchain

is the GCC summary part OK?

Yes

- armin

quoted

quoted

- armin

quoted

quoted

GCC_VERSION       = "6.1"

Not sure if the gcc version bit is best practice.

Armin Kuster (2):
build summary: add gcc version being used.
build summary: add TCLIBC being used

meta/classes/base.bbclass | 2 ++
meta/conf/bitbake.conf    | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)

--
2.3.5

--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core