From: "Naveen Saini" <naveen.kumar.saini@intel.com>
To: Ross Burton <ross.burton@arm.com>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [meta-zephyr][PATCH] zephyr: use TCLIBC=newlib directly
Date: Wed, 21 Oct 2020 05:35:49 +0000 [thread overview]
Message-ID: <aa6dbe8064824081b832cb11cfe98eb2@intel.com> (raw)
In-Reply-To: <20201020124254.471303-1-ross.burton@arm.com>
Few kernel testcases have dependencies on gperf-native, so we should keep it in DEPENDS.
Regards,
Naveen
-----Original Message-----
From: Ross Burton <ross.burton@arm.com>
Sent: Tuesday, October 20, 2020 8:43 PM
To: yocto@lists.yoctoproject.org
Cc: Saini, Naveen Kumar <naveen.kumar.saini@intel.com>
Subject: [meta-zephyr][PATCH] zephyr: use TCLIBC=newlib directly
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.
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}"
--
2.25.1
prev parent reply other threads:[~2020-10-21 5:35 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
2020-10-21 5:35 ` Naveen Saini [this message]
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=aa6dbe8064824081b832cb11cfe98eb2@intel.com \
--to=naveen.kumar.saini@intel.com \
--cc=ross.burton@arm.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