All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gst1-plugins-imx: add package
Date: Sun, 02 Nov 2014 23:13:21 +0100	[thread overview]
Message-ID: <5456AC81.5090403@lucaceresoli.net> (raw)
In-Reply-To: <1414636344-8152-1-git-send-email-bisson.gary@gmail.com>

Dear Gary,

thanks for you resubmission.

Gary Bisson wrote:
> Open-source GStreamer 1.0 plugins for i.MX platforms.
> More info at https://github.com/Freescale/gstreamer-imx
>
> Signed-off-by: Gary Bisson <bisson.gary@gmail.com>
> ---
> Modifications v1->v2:
> - Use of github helper macro
> - Modify package comment with Peter S. original patch
> - Add comment for eglibc dependency (due to GPU libs)
> - Remove comments on package dependencies
>
> One thing I wasn't sure about, should all new package contain a .hash file? If
> so I can submit a v3 right away.

It is not mandatory. AFAIK the hash is recommended for security-related
packages only.

[...]
> diff --git a/package/gstreamer1/gst1-plugins-imx/Config.in b/package/gstreamer1/gst1-plugins-imx/Config.in
> new file mode 100644
> index 0000000..d499874
> --- /dev/null
> +++ b/package/gstreamer1/gst1-plugins-imx/Config.in
> @@ -0,0 +1,28 @@
> +comment "gst1-plugins-imx needs an imx-specific Linux kernel to be built"
> +	depends on BR2_arm && !BR2_LINUX_KERNEL
> +
> +# Required by gpu-viv-bin-mx6q
> +comment "gst1-plugins-imx needs an (e)glibc toolchain"
> +	depends on BR2_arm
> +	depends on !BR2_TOOLCHAIN_USES_GLIBC

These messages are much cleaner than in version 1 of your patch.
However, for an ARM configuration with a musl or uClibc toolchain and
without a kernel build activated, two lines are displayed. This is not
coherent with the general Buildroot behavior.

It should be:

comment "gst1-plugins-imx needs an (e)glibc toolchain and an 
imx-specific Linux kernel to be built"
	depends on BR2_arm && (!BR2_LINUX_KERNEL || !BR2_TOOLCHAIN_USES_GLIBC)

Although that's a bit lengthy...

With that fixed (which can be done by the committer):
Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net>

I'll try to test it during the coming week and give my Tested-by tag, or
report any issues.

-- 
Luca

  reply	other threads:[~2014-11-02 22:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30  2:32 [Buildroot] [PATCH v2] gst1-plugins-imx: add package Gary Bisson
2014-11-02 22:13 ` Luca Ceresoli [this message]
2014-11-03 21:33   ` Arnout Vandecappelle
2014-11-03 21:51 ` Arnout Vandecappelle
2014-11-03 22:47   ` Gary Bisson
2014-11-08 22:01     ` Peter Korsgaard

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=5456AC81.5090403@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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 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.