From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2 1/2] add support for debian build profiles
Date: Tue, 4 Jan 2022 17:43:24 +0530 [thread overview]
Message-ID: <CALLGG_Khbw8UEVvT0pwGnSt6YsvHLDJU1GRO5nnpJbNt0ZXYpw@mail.gmail.com> (raw)
In-Reply-To: <20220104100235.719079-2-felix.moessbauer@siemens.com>
On Tue, Jan 4, 2022 at 3:33 PM Felix Moessbauer
<felix.moessbauer@siemens.com> wrote:
>
> This patch adds the bitbake variables DEB_BUILD_PROFILES and
> DEB_BUILD_PROFILES_CROSS.
> The values of these variables are used to define the DEB_BUILD_PROFILES
> environment variable.
>
> When cross-compiling, the DEB_BUILD_PROFILES_CROSS variable is defaulted
> to "cross", to be consistent with upstream debian.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> RECIPE-API-CHANGELOG.md | 9 +++++++++
> meta/classes/dpkg-base.bbclass | 13 +++++++++++++
> meta/classes/dpkg.bbclass | 4 +++-
> 3 files changed, 25 insertions(+), 1 deletion(-)
>
> diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
> index 3bbb42a9..1f3a19b4 100644
> --- a/RECIPE-API-CHANGELOG.md
> +++ b/RECIPE-API-CHANGELOG.md
> @@ -314,3 +314,12 @@ The "NAME" used to be rather static and the TAG was always "latest", now the val
> ### Renamed variable CONTAINER_FORMATS to CONTAINER_IMAGE_FORMATS
>
> The meaning remains the same, just the name changed.
> +### Introduce debian build profiles
> +
> +All recipes that inherit from dpkg and dpkg-base can utilize the variables DEB_BUILD_PROFILES and DEB_BUILD_PROFILES_CROSS.
> +These variables define the DEB_BUILD_PROFILES environment variable which is available in do_install_builddeps and do_dpkg_build.
> +When cross compiling, the values in DEB_BUILD_PROFILES_CROSS (default: "cross") are used to define the environment variable.
> +
> +For a list of well-known Debian build profiles and common practices, we refer to Debian's BuildProfileSpec.
> +
> +
> diff --git a/meta/classes/dpkg-base.bbclass b/meta/classes/dpkg-base.bbclass
> index cb5ce4a9..05c1cbd3 100644
> --- a/meta/classes/dpkg-base.bbclass
> +++ b/meta/classes/dpkg-base.bbclass
> @@ -13,6 +13,8 @@ inherit deb-dl-dir
> DEPENDS ?= ""
>
> DEPENDS_append_riscv64 = "${@' crossbuild-essential-riscv64' if d.getVar('ISAR_CROSS_COMPILE', True) == '1' and d.getVar('PN') != 'crossbuild-essential-riscv64' else ''}"
> +DEB_BUILD_PROFILES ?= ""
> +DEB_BUILD_PROFILES_CROSS ?= "cross"
>
> python do_adjust_git() {
> import subprocess
> @@ -201,7 +203,17 @@ dpkg_runbuild() {
> die "This should never be called, overwrite it in your derived class"
> }
>
> +def isar_export_build_profiles(d):
> + import os
> + deb_build_profiles = os.environ['DEB_BUILD_PROFILES'] if 'DEB_BUILD_PROFILES' in os.environ else ''
> + if d.getVar("ISAR_CROSS_COMPILE") == "1":
> + deb_build_profiles += ' ' + d.getVar('DEB_BUILD_PROFILES_CROSS', True)
Still trying to understand the need for the extra variable. Maybe an
example will help me understand better.
It could just be DEB_BUILD_PROFILES += "cross"
> + else:
> + deb_build_profiles += ' ' + d.getVar('DEB_BUILD_PROFILES', True)
> + os.environ['DEB_BUILD_PROFILES'] = deb_build_profiles.strip()
> +
> python do_dpkg_build() {
> + isar_export_build_profiles(d)
> lock = bb.utils.lockfile(d.getVar("REPO_ISAR_DIR") + "/isar.lock",
> shared=True)
> bb.build.exec_func("dpkg_do_mounts", d)
> @@ -279,6 +291,7 @@ python do_devshell() {
>
> isar_export_proxies(d)
> isar_export_ccache(d)
> + isar_export_build_profiles(d)
>
> buildchroot = d.getVar('BUILDCHROOT_DIR')
> pp_pps = os.path.join(d.getVar('PP'), d.getVar('PPS'))
> diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
> index 27fe84f4..68f63f93 100644
> --- a/meta/classes/dpkg.bbclass
> +++ b/meta/classes/dpkg.bbclass
> @@ -9,10 +9,12 @@ PACKAGE_ARCH ?= "${DISTRO_ARCH}"
> do_install_builddeps() {
> dpkg_do_mounts
> E="${@ isar_export_proxies(d)}"
> + E="${@ isar_export_build_profiles(d)}"
> distro="${DISTRO}"
> if [ ${ISAR_CROSS_COMPILE} -eq 1 ]; then
> - distro="${HOST_DISTRO}"
> + distro="${HOST_DISTRO}"
Probably an unwanted indent change.
Thanks,
Vijai Kumar K
> fi
> +
> deb_dl_dir_import "${BUILDCHROOT_DIR}" "${distro}"
> sudo -E chroot ${BUILDCHROOT_DIR} /isar/deps.sh \
> ${PP}/${PPS} ${PACKAGE_ARCH} --download-only
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-01-04 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 10:02 [PATCH v2 0/2] " Felix Moessbauer
2022-01-04 10:02 ` [PATCH v2 1/2] " Felix Moessbauer
2022-01-04 11:24 ` Jan Kiszka
2022-01-04 12:13 ` vijai kumar [this message]
2022-01-04 10:02 ` [PATCH v2 2/2] refactor linux-custom.inc to use ISAR's DEB_BUILD_PROFILES support Felix Moessbauer
2022-01-04 11:25 ` Jan Kiszka
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=CALLGG_Khbw8UEVvT0pwGnSt6YsvHLDJU1GRO5nnpJbNt0ZXYpw@mail.gmail.com \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=felix.moessbauer@siemens.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