From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Peter Seiderer <ps.report@gmx.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/gst1-devtools: drop python2 build dependencies
Date: Thu, 10 Feb 2022 07:42:19 +0200 [thread overview]
Message-ID: <87wni3b7iq.fsf@tarshish> (raw)
In-Reply-To: <20220209223551.772606-1-james.hilliard1@gmail.com>
Hi James,
On Wed, Feb 09 2022, James Hilliard wrote:
> Looks like this was missed in c4bbd6da50488944debba29e195557e5b345f2b1
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> package/gstreamer1/gst1-devtools/gst1-devtools.mk | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/package/gstreamer1/gst1-devtools/gst1-devtools.mk b/package/gstreamer1/gst1-devtools/gst1-devtools.mk
> index 66b509ae2c..390b20de16 100644
> --- a/package/gstreamer1/gst1-devtools/gst1-devtools.mk
> +++ b/package/gstreamer1/gst1-devtools/gst1-devtools.mk
> @@ -17,11 +17,7 @@ GST1_DEVTOOLS_DEPENDENCIES = \
> json-glib \
> $(if $(BR2_PACKAGE_CAIRO),cairo)
>
> -ifeq ($(BR2_PACKAGE_PYTHON3),y)
> GST1_DEVTOOLS_DEPENDENCIES += host-python3 python3
Maybe better add this to the list of unconditional dependencies above?
baruch
> -else
> -GST1_DEVTOOLS_DEPENDENCIES += host-python python
> -endif
>
> ifeq ($(BR2_PACKAGE_GST1_RTSP_SERVER),y)
> GST1_DEVTOOLS_DEPENDENCIES += gst1-rtsp-server
--
~. .~ 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:[~2022-02-10 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 22:35 [Buildroot] [PATCH 1/1] package/gst1-devtools: drop python2 build dependencies James Hilliard
2022-02-10 5:42 ` Baruch Siach via buildroot [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=87wni3b7iq.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=james.hilliard1@gmail.com \
--cc=ps.report@gmx.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