All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 3/3] qt5base: make harfbuzz support selectable
Date: Sun, 9 Apr 2017 21:32:56 +0200	[thread overview]
Message-ID: <20170409213256.3a854474@gmx.net> (raw)
In-Reply-To: <20170408160959.1e0ef627@free-electrons.com>

Hello Thomas,

On Sat, 8 Apr 2017 16:09:59 +0200, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> Hello,
> 
> On Sat, 18 Feb 2017 12:32:02 +0100, Peter Seiderer wrote:
> > If selected use:
> > 
> >  - system/buildroot harfbuzz in case __sync for 4 bytes is supported
> >  - qt harfbuzz otherwise (using QAtomic instead)
> > 
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> 
> We still have this patch pending. Could you summarize if it's still
> needed. From a quick read of our past discussion, it seems like it is
> still needed, but I prefer to ask before applying. Thanks!
> 

...considering your quote 'We generally don't like
to use the builtin libraries.' ([1]) I would say yes ;-)

Otherwise at least the harfbuzz license part is needed...

Regards,
Peter

[1] http://lists.busybox.net/pipermail/buildroot/2017-February/183615.html

> Thomas

  reply	other threads:[~2017-04-09 19:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18 11:32 [Buildroot] [PATCH v3 1/3] qt5base: move linuxfb configure option comment Peter Seiderer
2017-02-18 11:32 ` [Buildroot] [PATCH v3 2/3] qt5base: use system/buildroot provided freetype Peter Seiderer
2017-02-20 21:04   ` Thomas Petazzoni
2017-02-18 11:32 ` [Buildroot] [PATCH v3 3/3] qt5base: make harfbuzz support selectable Peter Seiderer
2017-02-20 21:04   ` Thomas Petazzoni
2017-02-20 21:14     ` Peter Seiderer
2017-02-20 21:22       ` Thomas Petazzoni
2017-04-08 14:09   ` Thomas Petazzoni
2017-04-09 19:32     ` Peter Seiderer [this message]
2017-10-21 19:38   ` Arnout Vandecappelle
2017-02-20 21:04 ` [Buildroot] [PATCH v3 1/3] qt5base: move linuxfb configure option comment Thomas Petazzoni

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=20170409213256.3a854474@gmx.net \
    --to=ps.report@gmx.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.