From: Gary Bisson <gary.bisson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/nxp: new package directory
Date: Thu, 16 Jul 2020 17:00:56 +0200 [thread overview]
Message-ID: <20200716150056.GA702345@p1g2> (raw)
In-Reply-To: <20200716135738.19050-2-fgervais@distech-controls.com>
Hi,
On Thu, Jul 16, 2020 at 09:57:37AM -0400, Francois Gervais wrote:
> From: Changming Huang <jerry.huang@nxp.com>
>
> The "nxp" directory is intended to contain all NXP
> QorIQ (including PowerPC and LayerScape serial) related packages,
> together with their download site and version info.
>
> Signed-off-by: Changming Huang <jerry.huang@nxp.com>
> Signed-off-by: Francois Gervais <fgervais@distech-controls.com>
> ---
> package/Config.in | 1 +
> package/nxp/Config.in | 4 ++++
> package/nxp/helper.mk | 32 ++++++++++++++++++++++++++++++++
> 3 files changed, 37 insertions(+)
> create mode 100644 package/nxp/Config.in
> create mode 100644 package/nxp/helper.mk
>
> diff --git a/package/Config.in b/package/Config.in
> index aafaa312a1..c93c7452ec 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -502,6 +502,7 @@ endmenu
> source "package/nvidia-driver/Config.in"
> source "package/nvidia-tegra23/Config.in"
> source "package/nvme/Config.in"
> + source "package/nxp/Config.in"
> source "package/ofono/Config.in"
> source "package/on2-8170-modules/Config.in"
> source "package/open2300/Config.in"
> diff --git a/package/nxp/Config.in b/package/nxp/Config.in
> new file mode 100644
> index 0000000000..575542c7ab
> --- /dev/null
> +++ b/package/nxp/Config.in
> @@ -0,0 +1,4 @@
> +menu "NXP QorIQ libraries"
> + depends on BR2_aarch64 || BR2_arm || BR2_powerpc64 || BR2_powerpc
> +
> +endmenu
> diff --git a/package/nxp/helper.mk b/package/nxp/helper.mk
> new file mode 100644
> index 0000000000..79e4236249
> --- /dev/null
> +++ b/package/nxp/helper.mk
> @@ -0,0 +1,32 @@
> +################################################################################
> +#
> +# helper
> +#
> +################################################################################
> +
> +# Helper for self-extracting binaries distributed by NXP.
> +#
> +# The --force option makes sure it doesn't fail if the source
> +# directory already exists. The --auto-accept skips the license check,
> +# as it is not needed in Buildroot because we have legal-info. Since
> +# there's a EULA in the binary file, we extract it in this macro, and
> +# it should therefore be added to the LICENSE_FILES variable of
> +# packages using this macro. Also, remember to set REDISTRIBUTE to
> +# "NO". Indeed, this is a legal minefield: the EULA specifies that the
> +# Board Support Package includes software and hardware (sic!) for
> +# which a separate license is needed...
> +#
> +# $(1): full path to the archive file
> +#
> +define NXP_EXTRACT_HELPER
> + awk 'BEGIN { start = 0; } \
> + /^EOEULA/ { start = 0; } \
> + { if (start) print; } \
> + /<<EOEULA/ { start = 1; }' \
> + $(1) > $(@D)/EULA
> + cd $(@D) && sh $(1) --force --auto-accept
> + find $(@D)/$(basename $(notdir $(1))) -mindepth 1 -maxdepth 1 -exec mv {} $(@D) \;
> + rmdir $(@D)/$(basename $(notdir $(1)))
> +endef
> +
> +include $(sort $(wildcard package/nxp/*/*.mk))
This looks like a copy/paste of package/freescale-imx/freescale-imx.mk,
maybe it is time to move the latter to a common "nxp" folder so that
new QorIQ/i.MX packages share the same macros.
Any thoughts?
Note that latest NXP release (LF) are for both i.MX and QorIQ.
Regards,
Gary
next prev parent reply other threads:[~2020-07-16 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 13:57 [Buildroot] [PATCH 0/2] Move package/rcw to package/nxp/qoriq-rcw Francois Gervais
2020-07-16 13:57 ` [Buildroot] [PATCH 1/2] package/nxp: new package directory Francois Gervais
2020-07-16 15:00 ` Gary Bisson [this message]
2020-07-16 13:57 ` [Buildroot] [PATCH 2/2] package/qoriq-rcw: move rcw into nxp and rename it Francois Gervais
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=20200716150056.GA702345@p1g2 \
--to=gary.bisson@boundarydevices.com \
--cc=buildroot@busybox.net \
/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