All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Binner <stephan.binner@basyskom.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH] recipes: upgrade from 5.4.0 to 5.4.1
Date: Fri, 27 Feb 2015 16:14:19 +0100	[thread overview]
Message-ID: <1924700.0Y3Fg92bfb@fridolin> (raw)
In-Reply-To: <20150227144201.GN2309@jama>

On Friday 27 February 2015 15:42:01 Martin Jansa wrote:

> I've fixed these issues in separate commit in meta-qt5/master-next and

Thanks.

> - please confirm that you agree with SOB line.

Sure I do. :-)

Today I noticed that qtwebengine doesn't compile if qtbase is not built with
"accessibility" (which I usually have defined via some qtbase*.bbappend).

The situation was the same with 5.4.0 - not sure if it's worth the effort
to patch qtwebengine to be able to compile without accessibility though.

Regards,
Stephan



  reply	other threads:[~2015-02-27 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 12:30 [meta-qt5][PATCH] recipes: upgrade from 5.4.0 to 5.4.1 Stephan Binner
2015-02-26 23:59 ` Jonathan Liu
2015-02-27 14:42 ` Martin Jansa
2015-02-27 15:14   ` Stephan Binner [this message]
2015-02-27 15:58     ` Martin Jansa
2015-02-27 16:53       ` Otavio Salvador

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=1924700.0Y3Fg92bfb@fridolin \
    --to=stephan.binner@basyskom.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.