From: "Khem Raj" <raj.khem@gmail.com>
To: Ross Burton <ross@burtonini.com>, yocto@lists.yoctoproject.org
Cc: naveen.kumar.saini@intel.com
Subject: Re: [yocto] [meta-zephyr][PATCH] zephyr: use TCLIBC=newlib directly
Date: Tue, 20 Oct 2020 10:06:16 -0700 [thread overview]
Message-ID: <ab6e6467-6026-e373-e926-a05f7824d671@gmail.com> (raw)
In-Reply-To: <20201020124254.471303-1-ross.burton@arm.com>
On 10/20/20 5:42 AM, Ross Burton wrote:
> Instead of setting TCLIBC=baremetal and then adding newlib in various places,
> just set TCLIBC=newlib directly.
>
> This also means we can use the standard DEPENDS instead of reinventing them.
>
I think this will also link the app with newlib now which previously was
using baremetal.
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
> conf/distro/zephyr.conf | 7 +------
> recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 3 ---
> 2 files changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/conf/distro/zephyr.conf b/conf/distro/zephyr.conf
> index 44448af..a98da32 100644
> --- a/conf/distro/zephyr.conf
> +++ b/conf/distro/zephyr.conf
> @@ -5,16 +5,11 @@ DISTRO_VERSION = "1.0"
>
> TARGET_VENDOR = "-yocto"
>
> -TCLIBC = "baremetal"
> -TCLIBCAPPEND = ""
> +TCLIBC = "newlib"
>
> TEST_TARGET = "QemuTargetZephyr"
> TEST_SUITES = "zephyr"
>
> -PREFERRED_PROVIDER_virtual/libc = "newlib"
> -PREFERRED_PROVIDER_virtual/libiconv = "newlib"
> -
> -TOOLCHAIN_TARGET_TASK += " newlib"
> INHERIT += "siteinfo-zephyr"
>
> INHERIT += "uninative"
> diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
> index 7fa4b25..b947472 100644
> --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
> +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
> @@ -19,9 +19,6 @@ EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis"
> export ZEPHYR_BASE="${S}"
>
>
> -# We always need a toolchain to cross-compile.
> -INHIBIT_DEFAULT_DEPS = "1"
> -DEPENDS += "gcc-cross-${TARGET_ARCH} libgcc ${TOOLCHAIN_TARGET_TASK} gperf-native"
> DEPENDS += " python3-pyelftools-native python3-pyyaml-native python3-pykwalify-native"
> CROSS_COMPILE = "${STAGING_BINDIR_TOOLCHAIN}/${TARGET_PREFIX}"
>
>
>
>
>
>
next prev parent reply other threads:[~2020-10-20 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 12:42 [meta-zephyr][PATCH] zephyr: use TCLIBC=newlib directly Ross Burton
2020-10-20 12:44 ` [yocto] " Ross Burton
2020-10-20 17:06 ` Khem Raj [this message]
2020-10-21 5:35 ` Naveen Saini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ab6e6467-6026-e373-e926-a05f7824d671@gmail.com \
--to=raj.khem@gmail.com \
--cc=naveen.kumar.saini@intel.com \
--cc=ross@burtonini.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox