From: Luc Beaufils <luc.beaufils@savoirfairelinux.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: buildroot <buildroot@buildroot.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Thomas Perrot <thomas.perrot@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 2/2] package/imx-cst: add new package
Date: Fri, 7 Mar 2025 10:32:11 -0500 (EST) [thread overview]
Message-ID: <1410095564.929994.1741361531063.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <87ldtgylbw.fsf@tarshish>
----- Le 7 Mar 25, à 15:19, Baruch Siach baruch@tkos.co.il a écrit :
> Hi Luc,
>
> On Fri, Mar 07 2025, Luc Beaufils wrote:
>> ----- Le 7 Mar 25, à 12:49, Baruch Siach baruch@tkos.co.il a écrit :
>>> On Fri, Mar 07 2025, Luc BEAUFILS wrote:
>>>> diff --git a/package/imx-cst/imx-cst.mk b/package/imx-cst/imx-cst.mk
>>>> new file mode 100644
>>>> index 0000000000..a3f1cdf6a4
>>>> --- /dev/null
>>>> +++ b/package/imx-cst/imx-cst.mk
>>>> @@ -0,0 +1,50 @@
>>>> +################################################################################
>>>> +#
>>>> +# imx-cst
>>>> +#
>>>> +################################################################################
>>>> +
>>>> +# debian/3.4.0-dfsg
>>>> +IMX_CST_VERSION = 3.4.0+dfsg
>>>> +IMX_CST_SOURCE = imx-code-signing-tool_$(IMX_CST_VERSION).orig.tar.xz
>>>> +IMX_CST_SITE = https://deb.debian.org/debian/pool/main/i/imx-code-signing-tool
>>>
>>> Debian source packages are removed from main once the release they
>>> belong to are retired. Buildroot usually uses the Debian snapshot
>>> archive. See example in alsamixergui, cdrkit, cvs, and a few more
>>> packages.
>>
>> Thank you for your reply.
>>
>> Unfortunately, I haven't been able to find the sources of this package in the
>> Debian snapshot.
>
> See here:
>
> http://snapshot.debian.org/archive/debian/20250307T084701Z/pool/main/i/imx-code-signing-tool/imx-code-signing-tool_3.4.0%2Bdfsg.orig.tar.xz
My bad, I was searching at imx-cst package name.
>
>> As an alternative, I propose using the Apertis GitLab repository:
>>
>> -IMX_CST_VERSION = 3.4.0+dfsg
>> -IMX_CST_SOURCE = imx-code-signing-tool_$(IMX_CST_VERSION).orig.tar.xz
>> -IMX_CST_SITE = https://deb.debian.org/debian/pool/main/i/imx-code-signing-tool
>> +IMX_CST_VERSION = debian/3.4.0+dfsg-2
>> +IMX_CST_SITE = https://gitlab.apertis.org/pkg/imx-code-signing-tool
>> +IMX_CST_SITE_METHOD = git
>>
>> Does this solution work for you?
>
> Looks like an older CST version. I guess the Debian snapshot is
> preferred.
>
> baruch
Yes, I will send a v3 patch with the debian snapshot package,
thanks
Luc
>
>>>> +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
>>>> +
>>>> +HOST_CFLAGS += -Wno-error=unused-result
>>>> +
>>>> +# 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) \
>>>> + OPENSSL_PATH=$(HOST_DIR)/include/openssl \
>>>> + ENCRYPTION=yes \
>>>> + AR="$(HOSTAR)" \
>>>> + CC="$(HOSTCC)" \
>>>> + LD="$(HOSTCC)" \
>>>> + OBJCOPY="$(HOSTOBJCOPY)" \
>>>> + RANLIB="$(HOSTRANLIB)" \
>>>> + EXTRACFLAGS="$(HOST_CFLAGS) $(HOST_CPPFLAGS)" \
>>>> + EXTRALDFLAGS="$(HOST_LDFLAGS)" \
>>>> + -C $(@D)
>>>> + $(HOST_MAKE_ENV) $(MAKE) $(HOST_CONFIGURE_OPTS) \
>>>> + COPTS="$(HOST_CFLAGS) $(HOST_CPPFLAGS) $(HOST_LDFLAGS)" \
>>>> + -C $(@D)/add-ons/hab_csf_parser
>>>> +endef
>>>> +
>>>> +define HOST_IMX_CST_INSTALL_CMDS
>>>> + $(INSTALL) -D -m 755 $(@D)/code/obj.$(HOST_IMX_CST_OSTYPE)/cst
>>>> $(HOST_DIR)/bin/cst
>>>> + $(INSTALL) -D -m 755 $(@D)/code/obj.$(HOST_IMX_CST_OSTYPE)/srktool
>>>> $(HOST_DIR)/bin/srktool
>>>> + $(INSTALL) -D -m 755 $(@D)/add-ons/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 -
>
> --
> ~. .~ 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
prev parent reply other threads:[~2025-03-07 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 9:59 [Buildroot] [PATCH v2 0/2] Support for i.MX Code Signing Tools Luc BEAUFILS
2025-03-07 9:59 ` [Buildroot] [PATCH v2 1/2] package/byacc: add new package Luc BEAUFILS
2025-03-07 9:59 ` [Buildroot] [PATCH v2 2/2] package/imx-cst: " Luc BEAUFILS
2025-03-07 11:49 ` Baruch Siach via buildroot
2025-03-07 14:09 ` Luc Beaufils
2025-03-07 14:19 ` Baruch Siach via buildroot
2025-03-07 15:32 ` Luc Beaufils [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=1410095564.929994.1741361531063.JavaMail.zimbra@savoirfairelinux.com \
--to=luc.beaufils@savoirfairelinux.com \
--cc=baruch@tkos.co.il \
--cc=buildroot@buildroot.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox