All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: gtk+ native recipe question
Date: Wed, 31 Oct 2012 14:07:51 +0000	[thread overview]
Message-ID: <1720082.VE0UplCuMC@helios> (raw)
In-Reply-To: <20121030115615.77684awm7w5p1fqc@webmail.recipes4linux.com>

Hi there,

On Tuesday 30 October 2012 11:56:15 T.Michael Turney wrote:
> My first post, chose -core over -devel somewhat arbitrarily as I don't
> understand distinction of OE-classic yet.

Basically, OE-Classic is largely unmaintained (aside from critical updates to 
the 2011.3-maintenance branch) and should not be used for new work - use OE-
Core for that instead. So you're on the right path already :)

> In order to get an existing OE system (builds on Fedora) to build correctly
> on 64-bit Ubuntu 12.04 I had to modify a number of recipe files.

That's definitely not expected...

> In order to get native gtk+ to build I had to add no-demos.patch
> to SRC_URI_append.  The patch file already existed in recipes tree
> but wasn't being referenced in the .bb file.
> 
> Second change was adding glib-2.0-native to DEPEND_virtclass-native in
> same file.

So, the version in master and the danny branch (most recent stable, just 
branched the other day) already includes this. Are you using a different 
branch/release?

> Problem was manifested with unresolved reference to g_bytes_unref when
> building gtk+ native.  Ubuntu 12.04 has more recent glib install than in
> OE project I'm building and g_bytes_unref is visible in host glib but not
> OE version.
> 
> With this change and a few other similar minor changes in .bb files, the
> system builds.  However, the bitbake build line has to be invoked twice.
> 
> For example, let's say I'm building foo-image and foo1-image, and I run:
> 
> bitbake foo-image foo1-image
> 
> This command fails building gtk+ native.  

Fails how? Can you mention the actual error you're receiving?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-10-31 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 18:56 gtk+ native recipe question T.Michael Turney
2012-10-31 14:07 ` Paul Eggleton [this message]
2012-10-31 19:57   ` T.Michael Turney
2012-10-31 22:31     ` Paul Eggleton
2012-10-31 22:51       ` Paul Eggleton

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=1720082.VE0UplCuMC@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@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.