From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Possible gtk+-native de-breakage
Date: Sun, 7 Mar 2010 13:40:47 +0100 [thread overview]
Message-ID: <20100307124047.GH31945@jama> (raw)
In-Reply-To: <20100306193907.GA5881@xora-build.xora.org.uk>
On Sat, Mar 06, 2010 at 07:39:07PM +0000, Graeme Gregory wrote:
> Hi, I knocked this up while doing some enterprise java installs this after
> noon and Im too brain fried to deal with it and wont have time in next few
> days.
>
> So can people checkout the attached patch/improve it.
I can confirm, that this patch solves
http://bugs.openembedded.org/show_bug.cgi?id=5405
as well as gtk+ demos build.
As RP said, maybe we should keep gdk-pixbuf-csource-native for those who
don't need whole gtk+, but for those like me who builds whole
gtk+-native because other apps it's better with
gdk-pixbuf-csource-native provider set to gtk+-native (to build it just
once).
Regards,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next prev parent reply other threads:[~2010-03-07 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 19:39 Possible gtk+-native de-breakage Graeme Gregory
2010-03-07 12:40 ` Martin Jansa [this message]
2010-03-09 20:49 ` Phil Blundell
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=20100307124047.GH31945@jama \
--to=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox