From: vijaikumar.kanagarajan@gmail.com
To: isar-users@googlegroups.com, jan.kiszka@siemens.com
Cc: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
Subject: [PATCH v2 2/2] Replace FILESPATH with FILESEXTRAPATHS
Date: Wed, 16 Oct 2019 20:07:45 +0530 [thread overview]
Message-ID: <20191016143745.25765-3-Vijaikumar_Kangarajan@mentor.com> (raw)
In-Reply-To: <20191016143745.25765-1-Vijaikumar_Kangarajan@mentor.com>
From: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
The suggested approach to include files & patches from bbappend
files is FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
This is not possible if FILESPATH is modified directly. Use
FILESEXTRAPATHS instead.
Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
---
meta/recipes-bsp/u-boot/u-boot-custom.inc | 2 +-
meta/recipes-kernel/linux-module/module.inc | 2 +-
meta/recipes-kernel/linux/linux-custom.inc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-bsp/u-boot/u-boot-custom.inc b/meta/recipes-bsp/u-boot/u-boot-custom.inc
index 8843789..41124fc 100644
--- a/meta/recipes-bsp/u-boot/u-boot-custom.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-custom.inc
@@ -5,7 +5,7 @@
#
# SPDX-License-Identifier: MIT
-FILESPATH =. "${LAYERDIR_core}/recipes-bsp/u-boot/files:"
+FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/files:"
DESCRIPTION ?= "Custom U-Boot"
diff --git a/meta/recipes-kernel/linux-module/module.inc b/meta/recipes-kernel/linux-module/module.inc
index 6506e39..d30e799 100644
--- a/meta/recipes-kernel/linux-module/module.inc
+++ b/meta/recipes-kernel/linux-module/module.inc
@@ -5,7 +5,7 @@
#
# SPDX-License-Identifier: MIT
-FILESPATH =. "${LAYERDIR_core}/recipes-kernel/linux-module/files:"
+FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/files:"
DESCRIPTION ?= "Custom kernel module ${PN}"
diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
index 5a4f5bf..dc2af1a 100644
--- a/meta/recipes-kernel/linux/linux-custom.inc
+++ b/meta/recipes-kernel/linux/linux-custom.inc
@@ -5,7 +5,7 @@
#
# SPDX-License-Identifier: MIT
-FILESPATH =. "${LAYERDIR_core}/recipes-kernel/linux/files:"
+FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/files:"
DESCRIPTION ?= "Custom kernel"
--
2.17.1
next prev parent reply other threads:[~2019-10-16 14:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0191015094118.GA15374@lightning>
2019-10-16 14:37 ` [PATCH v2 0/2] FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-16 14:37 ` [PATCH v2 1/2] meta: Add support for FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-16 14:37 ` vijaikumar.kanagarajan [this message]
2019-10-16 17:05 ` [PATCH v2 0/2] FILESEXTRAPATHS Henning Schild
2019-10-17 9:17 ` Vijai Kumar K
2019-10-17 9:28 ` [PATCH v3 " vijaikumar.kanagarajan
2019-10-17 9:28 ` [PATCH v3 1/2] meta: Add support for FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-17 9:28 ` [PATCH v3 2/2] Replace FILESPATH with FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-25 12:49 ` [PATCH v3 0/2] FILESEXTRAPATHS Baurzhan Ismagulov
2019-10-25 13:22 ` Henning Schild
2019-10-25 14:12 ` Baurzhan Ismagulov
2019-10-25 17:17 ` Jan Kiszka
2019-11-04 19:41 ` Baurzhan Ismagulov
2019-11-04 19:45 ` Baurzhan Ismagulov
2019-11-05 16:08 ` Henning Schild
2019-11-05 16:18 ` vijai kumar
2019-11-05 17:07 ` Jan Kiszka
2019-11-05 17:36 ` vijai kumar
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=20191016143745.25765-3-Vijaikumar_Kangarajan@mentor.com \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=Vijaikumar_Kanagarajan@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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