public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v5 6/9] optee-os-stm32mp15x: Do not use shell environment
Date: Sun, 13 Feb 2022 08:41:08 +0100	[thread overview]
Message-ID: <20220213074111.23232-7-ubely@ilbers.de> (raw)
In-Reply-To: <20220213074111.23232-1-ubely@ilbers.de>

Move export of TEE_IMPL_VERSION variable directly to debian/rules.

This makes building process more Debian-like.

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb b/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb
index 0fa2005d..9c0efaf1 100644
--- a/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb
+++ b/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb
@@ -21,5 +21,8 @@ OPTEE_BINARIES = "tee-header_v2.stm32 tee-pageable_v2.stm32 tee-pager_v2.stm32"
 # Set version manually to PV, the tarball does not contain any hint.
 # Alternative: pull from git and add git as build dependency.
 dpkg_runbuild_prepend() {
-    export TEE_IMPL_VERSION=${PV}
+    cat << EOF >> ${S}/debian/rules
+
+export TEE_IMPL_VERSION=${PV}
+EOF
 }
-- 
2.20.1


  parent reply	other threads:[~2022-02-13  7:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13  7:41 [PATCH v5 0/9] Avoid using shell environment during the build Uladzimir Bely
2022-02-13  7:41 ` [PATCH v5 1/9] template: Copy template attributes on transform Uladzimir Bely
2022-02-13  7:41 ` [PATCH v5 2/9] linux-module: Do not use shell environment Uladzimir Bely
2022-02-13  7:41 ` [PATCH v5 3/9] u-boot: " Uladzimir Bely
2022-02-13  7:41 ` [PATCH v5 4/9] trusted-firmware: " Uladzimir Bely
2022-02-13  7:41 ` [PATCH v5 5/9] optee-os: " Uladzimir Bely
2022-02-13  7:41 ` Uladzimir Bely [this message]
2022-02-22  6:49   ` [PATCH v5 6/9] optee-os-stm32mp15x: " Jan Kiszka
2022-02-22 12:29     ` Uladzimir Bely
2022-02-23 14:01       ` Jan Kiszka
2022-02-13  7:41 ` [PATCH v5 7/9] kselftest: " Uladzimir Bely
2022-02-13  7:41 ` [PATCH v5 8/9] linux-mainline: Move cfg fragment test to debian/rules Uladzimir Bely
2022-02-22  6:50   ` Jan Kiszka
2022-02-13  7:41 ` [PATCH v5 9/9] linux-custom: Move cfg fragments applying " Uladzimir Bely
2022-02-23 13:53   ` Henning Schild
2022-02-24  9:09     ` Uladzimir Bely
2022-02-24 12:36       ` Henning Schild
2022-02-24 14:49         ` Uladzimir Bely
2022-02-24 19:53           ` Henning Schild
2022-02-22  6:39 ` [PATCH v5 0/9] Avoid using shell environment during the build Anton Mikanovich

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=20220213074111.23232-7-ubely@ilbers.de \
    --to=ubely@ilbers.de \
    --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