Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] package/ffmpeg: Add support for GnuTLS
Date: Mon, 19 Oct 2015 21:23:48 +0200	[thread overview]
Message-ID: <4jsffcxklv.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20151018154530.06efcfb9@free-electrons.com

Hi Thomas,

Am Sun, 18 Oct 2015 15:45:30 +0200 schrieb Thomas Petazzoni:

> # OpenSSL license is not compatible with the LGPL license of ffmpeg.
> else ifeq ($(BR2_PACKAGE_OPENSSL):$(BR2_PACKAGE_FFMPEG_GPL)
$(BR2_PACKAGE_FFMPEG_NONFREE),y::y)
> FFMPEG_CONF_OPTS += --enable-openssl
> FFMPEG_DEPENDENCIES += openssl
> else
> FFMPEG_CONF_OPTS += --disable-gnutls --disable-openssl
> endif
> 
> I think it is functionally equivalent, but much nicer to read. If you
> agree (and the above works), can you send a patch doing this?

your code does not duplicate the logic of ffmpeg configure. In your 
proposal the following settings are required for OpenSSL support:

	BR2_PACKAGE_FFMPEG_GPL		disabled
	BR2_PACKAGE_FFMPEG_NONFREE	enabled

This is one of three valid combinations, ffmpeg configure also
accepts these combinations for OpenSSL support:

	BR2_PACKAGE_FFMPEG_GPL		disabled
	BR2_PACKAGE_FFMPEG_NONFREE	disabled
and
	BR2_PACKAGE_FFMPEG_GPL		enabled
	BR2_PACKAGE_FFMPEG_NONFREE	enabled

because in

http://git.videolan.org/?
p=ffmpeg.git;a=blob;f=configure;h=7f9fed31a491ed0991aee2d354dba82e54e3291e;hb=refs/
heads/release/2.8#l4664

the following code line

enabled gpl && die_license_disabled_gpl nonfree openssl

checks whether --enable-gpl was issued and breaks only if --enable-
nonfree is not used at the same time like in the third example.

If --enable-gpl is not used, like in the first and second example, there 
will be no OpenSSL-related license checks during ffmpeg configure.

In other words: You can enable gpl-only code in ffmpeg along with OpenSSL 
support if you do not re-distribute the resulting binaries. If you do not 
enable gpl-only code you can do what you want regarding OpenSSL ;)

I am a bit lost atm trying to mirror this logic in an optimized form in 
package/ffmpeg/ffmpeg.mk as requested, sorry.

Regards, Bernd

      reply	other threads:[~2015-10-19 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-17 19:38 [Buildroot] [PATCH v4 1/1] package/ffmpeg: Add support for GnuTLS Bernd Kuhls
2015-10-17 19:55 ` Yann E. MORIN
2015-10-18 13:45 ` Thomas Petazzoni
2015-10-19 19:23   ` Bernd Kuhls [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=4jsffcxklv.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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