From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Thomas Perrot <thomas.perrot@bootlin.com>
Cc: thomas.petazzoni@bootlin.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/imx-cst: new package
Date: Wed, 20 Apr 2022 20:28:06 +0300 [thread overview]
Message-ID: <87pmlbr70w.fsf@tarshish> (raw)
In-Reply-To: <20220420083923.3875405-2-thomas.perrot@bootlin.com>
Hi Thomas,
On Wed, Apr 20 2022, Thomas Perrot via buildroot wrote:
> This package provides i.MX Code Signing Tools uses to sign i.MX bootloader
> to enable secure boot (HABv4 and AHAB).
>
> Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com>
> ---
[...]
> diff --git a/package/imx-cst/imx-cst.mk b/package/imx-cst/imx-cst.mk
> new file mode 100644
> index 000000000000..c91dfb602cbf
> --- /dev/null
> +++ b/package/imx-cst/imx-cst.mk
> @@ -0,0 +1,49 @@
> +################################################################################
> +#
> +# imx-cst
> +#
> +################################################################################
> +
> +# debian/3.3.1+dfsg-2
> +IMX_CST_SITE = https://gitlab.apertis.org/pkg/imx-code-signing-tool.git
> +IMX_CST_SITE_METHOD = git
> +IMX_CST_VERSION = e2c687a856e6670e753147aacef42d0a3c07891a
> +IMX_CST_LICENSE = BSD-3-Clause
> +IMX_CST_LICENSE_FILES = LICENSE.bsd3
> +
> +HOST_IMX_CST_DEPENDENCIES = host-byacc host-flex host-openssl
> +
> +ifneq ($(filter %64,$(HOSTARCH)),)
> +HOST_IMX_CST_OSTYPE = linux64
> +else
> +HOST_IMX_CST_OSTYPE = linux32
> +endif
It looks like the only difference between 64 and 32 is in openssl build
rule, and for x86 (host) targets only. We don't use this openssl rule
since we build host-openssl with our own rules. So maybe we can just
arbitrarily choose hard coded 'linux64'. It seems that debian/Makefile
does that.
baruch
> +
> +# We don't use HOST_CONFIGURE_OPTS when building cst, because we need
> +# to preserve the CFLAGS/LDFLAGS used by their Makefile.
> +define HOST_IMX_CST_BUILD_CMDS
> + $(HOST_MAKE_ENV) $(MAKE) \
> + OSTYPE=$(HOST_IMX_CST_OSTYPE) \
> + ENCRYPTION=yes \
> + AR="$(HOSTAR)" \
> + CC="$(HOSTCC)" \
> + LD="$(HOSTCC)" \
> + OBJCOPY="$(HOSTOBJCOPY)" \
> + RANLIB="$(HOSTRANLIB)" \
> + EXTRACFLAGS="$(HOST_CFLAGS) $(HOST_CPPFLAGS)" \
> + EXTRALDFLAGS="$(HOST_LDFLAGS)" \
> + PWD=$(@D)/code/cst \
> + -C $(@D)/code/cst \
> + build
> + $(HOST_MAKE_ENV) $(MAKE) $(HOST_CONFIGURE_OPTS) \
> + COPTS="$(HOST_CFLAGS) $(HOST_CPPFLAGS) $(HOST_LDFLAGS)" \
> + -C $(@D)/code/hab_csf_parser
> +endef
> +
> +define HOST_IMX_CST_INSTALL_CMDS
> + $(INSTALL) -D -m 755 $(@D)/code/cst/code/obj.linux64/cst $(HOST_DIR)/bin/cst
> + $(INSTALL) -D -m 755 $(@D)/code/cst/code/obj.linux64/srktool $(HOST_DIR)/bin/srktool
> + $(INSTALL) -D -m 755 $(@D)/code/hab_csf_parser/csf_parser $(HOST_DIR)/bin/csf_parser
> +endef
> +
> +$(eval $(host-generic-package))
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-04-20 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 8:39 [Buildroot] [PATCH v2 1/2] package/byacc: new package Thomas Perrot via buildroot
2022-04-20 8:39 ` [Buildroot] [PATCH 2/2] package/imx-cst: " Thomas Perrot via buildroot
2022-04-20 17:28 ` Baruch Siach via buildroot [this message]
2022-04-22 10:09 ` Thomas Perrot via buildroot
2022-04-22 10:16 ` Thomas Petazzoni via buildroot
2022-04-24 11:19 ` Baruch Siach via buildroot
2022-08-22 19:56 ` [Buildroot] [PATCH v2 1/2] package/byacc: " Yann E. MORIN
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=87pmlbr70w.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=thomas.perrot@bootlin.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.