From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta-isar: Allow to include isar-image-base from external layers
Date: Thu, 6 Jul 2017 07:26:16 +0200 [thread overview]
Message-ID: <cfd39b6d-ff77-5753-2e55-62de0e5df5b3@siemens.com> (raw)
In-Reply-To: <c8cc2a8c-828f-bce5-96d7-49142129572c@siemens.com>
On 2017-07-06 07:08, [ext] Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> THISDIR is expanded immediately which makes the including file define
> the path rather than the file that contains this variable. Use
> FILE_DIRNAME instead which has the required late evaluation property.
>
> This allows to "require recipes-core/images/isar-image-base.bb" from
> out-of-tree layers in order to derive an image from the base version.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> meta-isar/recipes-core/images/isar-image-base.bb | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/meta-isar/recipes-core/images/isar-image-base.bb b/meta-isar/recipes-core/images/isar-image-base.bb
> index 66d3cb9..f36fdc4 100644
> --- a/meta-isar/recipes-core/images/isar-image-base.bb
> +++ b/meta-isar/recipes-core/images/isar-image-base.bb
> @@ -27,10 +27,10 @@ do_rootfs() {
> install -d -m 755 ${WORKDIR}/hooks_multistrap
>
> # Copy config file
> - install -m 644 ${THISDIR}/files/multistrap.conf.in ${WORKDIR}/multistrap.conf
> - install -m 755 ${THISDIR}/files/${DISTRO_CONFIG_SCRIPT} ${WORKDIR}/configscript.sh
> - install -m 755 ${THISDIR}/files/setup.sh ${WORKDIR}
> - install -m 755 ${THISDIR}/files/download_dev-random ${WORKDIR}/hooks_multistrap/
> + install -m 644 ${FILE_DIRNAME}/files/multistrap.conf.in ${WORKDIR}/multistrap.conf
> + install -m 755 ${FILE_DIRNAME}/files/${DISTRO_CONFIG_SCRIPT} ${WORKDIR}/configscript.sh
> + install -m 755 ${FILE_DIRNAME}/files/setup.sh ${WORKDIR}
> + install -m 755 ${FILE_DIRNAME}/files/download_dev-random ${WORKDIR}/hooks_multistrap/
>
> # Adjust multistrap config
> sed -i 's|##IMAGE_PREINSTALL##|${IMAGE_PREINSTALL}|' ${WORKDIR}/multistrap.conf
>
Forget this, I was testing the wrong version. We need to define COREBASE
and derive the path from that.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2017-07-06 5:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 5:08 Jan Kiszka
2017-07-06 5:26 ` Jan Kiszka [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=cfd39b6d-ff77-5753-2e55-62de0e5df5b3@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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