Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Alessandro Sappia <a.sappia@biotechware.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH 0/1] dbus-glib-native and dbus-glib corrected
Date: Wed,  6 Jul 2011 13:12:09 +0200	[thread overview]
Message-ID: <cover.1309949770.git.a.sappia@biotechware.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

Hi all,
dbus-glib-native and dbus-glib were not compiling. 
Reason were in how the dbus-glib.inc and dbus-glib_0.86.bb were wrote.
The patch clears what the recipe has to do for each target compilation.

More info from http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg10184.html
[cut]
> I suspect that code could well have come from Poky. In this case the
> native recipe generates a file which is then used by the target builds.
> It can't be generated in the target recipe as that would mean running
> target binaries.
[cut]

Patch compiles and dbus-glib works on target device (tested with mini2440).

Regards,

Alessandro

Alessandro Sappia (1):
  dbus-glib-native and dbus-glib were not compiling. This patch
    corrects dbus-glib-native to install required files in order to let
    dbus-glib to compile on target.

 recipes/dbus/dbus-glib.inc     |    4 ++--
 recipes/dbus/dbus-glib_0.86.bb |    4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

-- 
1.7.4.1



             reply	other threads:[~2011-07-06 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 11:12 Alessandro Sappia [this message]
     [not found] ` <d0771ab59e5a19cd41045ecaf5f390926a78e229.1309949770.git.a.sappia@biotechware.com>
2011-07-06 11:32   ` [PATCH 1/1] dbus-glib-native and dbus-glib were not compiling. This patch corrects dbus-glib-native to install required files in order to let dbus-glib to compile on target Paul Menzel
2011-07-06 11:56     ` [PATCH v2] dbus-glib: install required files for target on native build Alessandro Sappia
2011-07-06 12:11       ` Henning Heinold
2011-07-06 12:36         ` Alessandro Sappia

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=cover.1309949770.git.a.sappia@biotechware.com \
    --to=a.sappia@biotechware.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