All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] qt5tools: new package
Date: Thu, 4 Feb 2016 22:32:45 +0100	[thread overview]
Message-ID: <20160204223245.243b9c96@gmx.net> (raw)
In-Reply-To: <20160204221333.00873039@free-electrons.com>

Hello Thomas,

On Thu, 4 Feb 2016 22:13:33 +0100, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> Hello,
> 
> On Thu, 4 Feb 2016 22:07:05 +0100, Peter Seiderer wrote:
> 
> > > This does not really answer the question. The question is really
> > > whether pixeltools uses only the Qt5 PNG functions, or directly the
> > > libpng functions.
> > 
> > Sorry for not being precise here, pixeltools uses only Qt5 PNG functions
> > (via QPixmap.save(name, "PNG"))...
> 
> OK, then the dependency on libpng is indeed not needed.
> 
> 
> > > Having host binaries in $(STAGING_DIR) is really not good. So yes,
> > > maybe QT_INSTALL_BINS should point to $(HOST_DIR)/usr/bin/.
> > 
> > Will take a look and try to change QT_INSTALL_BINS, hope it breaks no
> > other usage...
> 
> That's also what I'm a bit afraid of, but the only way to know is to
> actually test.

Found a better way, simple use QT_HOST_BINS instead of QT_INSTALL_BINS
in my example...will send an updated patch soon...

Regards,
Peter

> 
> Best regards,
> 
> Thomas

      reply	other threads:[~2016-02-04 21:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 22:01 [Buildroot] [PATCH v2 1/2] qt5tools: new package Peter Seiderer
2016-02-03 22:44 ` Thomas Petazzoni
2016-02-04 20:20   ` Peter Seiderer
2016-02-04 20:38     ` Thomas Petazzoni
2016-02-04 21:07       ` Peter Seiderer
2016-02-04 21:13         ` Thomas Petazzoni
2016-02-04 21:32           ` Peter Seiderer [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=20160204223245.243b9c96@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.