From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] webkitgtk: add dependency on the woff2 package
Date: Wed, 10 Oct 2018 00:17:14 +0200 [thread overview]
Message-ID: <20181010001714.GD10287@momiji> (raw)
In-Reply-To: <87tvmbw4qb.fsf@dell.be.48ers.dk>
Hello Peter (and all the mailing list members),
On Thu, 27 Sep 2018 13:37:48 +0200, Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "Adrian" == Adrian Perez de Castro <aperez@igalia.com> writes:
>
> Hi,
>
> >> However, since woff2 has very few dependencies, and
> >> woff2+brotli+host-pkgconf build in 19 seconds, it's nothing compared to
> >> webkitgtk, so I applied your patch.
>
> > I will make a follow-up patch to make WOFF2 optional. I think it should be
> > fine to enable it by default if BR2_PACKAGE_WOFF2 is enabled, and add a line
> > in the help description telling that it is recommended to enable it.
>
> Correct. Now that we have updated kconfig we could even consider using
> the imply keyword to enable woff2 by default if it is really an option
> that most people should enable:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=237e3ad0f195d8fd34f1299e45f04793832a16fc
There's a small doubt I have here... How exactly would we prefer to have this?
I can think of two options. One would be the following, and would allow to
disable WOFF2 support in WebKitGTK+ even if the woff2 package is built:
config BR2_PACKAGE_WEBKITGTK
# ...
imply BR2_PACKAGE_WEBKITGTK_WOFF2
config BR2_PACKAGE_WEBKITGTK_WOFF2
bool "woff2 support"
depends on BR2_PACKAGE_WOFF2
imply BR2_PACKAGE_WOFF2
The other, simpler option, always enables WOFF2 support in WebKitGTK+ if the
woff2 package can be built:
config BR2_PACKAGE_WEBKITGTK
# ...
imply BR2_PACKAGE_WOFF2
With this second option, the only way of disabling WOFF2 support in WebKitGTK+
is *also* disabling the woff2 package completely. While this is not a problem
in this case right now (I think WebKitGTK+ is the only user of the woff2
package, after all), I would like to apply a similar treatment to some of the
build options.
Any preference/suggestion/comments? Thanks in advance,
-Adri?n
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181010/15a0a0cf/attachment.asc>
next prev parent reply other threads:[~2018-10-09 22:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-22 23:53 [Buildroot] [PATCH 0/5] webkitgtk: update to the latest stable and add a number of fixes Adrian Perez de Castro
2018-09-22 23:53 ` [Buildroot] [PATCH 1/5] webkitgtk: bump to version 2.22.2 Adrian Perez de Castro
2018-09-25 20:47 ` Thomas Petazzoni
2018-10-05 17:34 ` Peter Korsgaard
2018-09-22 23:53 ` [Buildroot] [PATCH 2/5] webkitgtk: add dependency on the woff2 package Adrian Perez de Castro
2018-09-25 20:52 ` Thomas Petazzoni
2018-09-27 9:41 ` Adrian Perez de Castro
2018-09-27 11:37 ` Peter Korsgaard
2018-09-27 12:44 ` Adrian Perez de Castro
2018-10-09 22:17 ` Adrian Perez de Castro [this message]
2018-10-11 18:19 ` Peter Korsgaard
2018-10-19 18:29 ` Adrian Perez de Castro
2018-10-05 17:34 ` Peter Korsgaard
2018-09-22 23:53 ` [Buildroot] [PATCH 3/5] webkitgtk: enable package for aarch64 Adrian Perez de Castro
2018-09-25 20:56 ` Thomas Petazzoni
2018-09-27 9:44 ` Adrian Perez de Castro
2018-09-22 23:53 ` [Buildroot] [PATCH 4/5] webkitgtk: enable JIT support on 32-bit MIPS Adrian Perez de Castro
2018-09-22 23:53 ` [Buildroot] [PATCH 5/5] webkitgtk: explicitly set USE_GSTREAMER_GL build option Adrian Perez de Castro
2018-09-25 20:57 ` Thomas Petazzoni
2018-09-27 12:40 ` Adrian Perez de Castro
2018-10-02 21:28 ` Arnout Vandecappelle
2018-10-09 21:12 ` Adrian Perez de Castro
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=20181010001714.GD10287@momiji \
--to=aperez@igalia.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