Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] meson-tools: new Package
Date: Sun, 30 Aug 2020 00:12:38 +0200	[thread overview]
Message-ID: <20200830001238.1ca793de@windsurf.home> (raw)
In-Reply-To: <20200717164643.4702-1-daggs@gmx.com>

Hello,

On Fri, 17 Jul 2020 19:46:40 +0300
Dagg Stompler <daggs@gmx.com> wrote:

> add meson-tools for handling of amlogic boards boot firmware signatures
> 
> Signed-off-by: Dagg Stompler <daggs@gmx.com>

Thanks, I have applied your patch to our next branch, with a few
changes.

First, the commit title was changed to:

	package/meson-tools: new package

> diff --git a/package/meson-tools/meson-tools.hash b/package/meson-tools/meson-tools.hash
> new file mode 100644
> index 0000000000..f10f5d8590
> --- /dev/null
> +++ b/package/meson-tools/meson-tools.hash
> @@ -0,0 +1,2 @@
> +# Locally calculated
> +sha256	10d707b2f741df03ff5000f2a82c6f577036ce1cd34d9278b22b92cb616b6fce	meson-tools-0a02e2d34413f4bf9b15946352bc8c8ee13a5843.tar.gz

I've added the hash of the license file here, and use 2 spaces as a
separator, which is our convention.

> diff --git a/package/meson-tools/meson-tools.mk b/package/meson-tools/meson-tools.mk
> new file mode 100644
> index 0000000000..7fe115c6dd
> --- /dev/null
> +++ b/package/meson-tools/meson-tools.mk
> @@ -0,0 +1,24 @@
> +################################################################################
> +#
> +# meson-tools
> +#
> +################################################################################
> +
> +HOST_MESON_TOOLS_VERSION = 0a02e2d34413f4bf9b15946352bc8c8ee13a5843
> +HOST_MESON_TOOLS_SITE = $(call github,afaerber,meson-tools,$(HOST_MESON_TOOLS_VERSION))
> +HOST_MESON_TOOLS_LICENSE = GPL-2.0+
> +HOST_MESON_TOOLS_LICENSE_FILES = COPYING README.md

I've dropped README.md here, it doesn't contain any license details.

> +HOST_MESON_TOOLS_DEPENDENCIES = host-openssl
> +
> +HOST_MESON_TOOLS_PROGS = amlbootsig unamlbootsig amlinfo
> +
> +define HOST_MESON_TOOLS_BUILD_CMDS
> +	$(MAKE) -C $(@D) CC="$(HOSTCC)" CFLAGS="$(HOST_CFLAGS)" LDFLAGS="$(HOST_LDFLAGS) -lssl -lcrypto"

I've used $(HOST_CONFIGURE_OPTS) here instead of passing CC/CFLAGS
manually.

As said: applied with those changes. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2020-08-29 22:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 16:46 [Buildroot] [PATCH 1/4] meson-tools: new Package Dagg Stompler
2020-07-17 16:46 ` [Buildroot] [PATCH 2/4] odroidc2_atf: " Dagg Stompler
2020-09-03 18:50   ` Thomas Petazzoni
2020-07-17 16:46 ` [Buildroot] [PATCH 3/4] board/odroidc2: add board Dagg Stompler
2020-09-03 18:53   ` Thomas Petazzoni
2020-07-17 16:46 ` [Buildroot] [PATCH 4/4] configs/odroidc2: add defconfig Dagg Stompler
2020-08-29 22:12 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-10 14:58 [Buildroot] [PATCH 1/4] meson-tools: new Package Dagg Stompler
2018-03-10 15:24 ` daggs

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=20200830001238.1ca793de@windsurf.home \
    --to=thomas.petazzoni@bootlin.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