All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Coordination for updating the XBMC recipe
Date: Tue, 16 Aug 2011 10:07:17 +0200	[thread overview]
Message-ID: <j2d8fl$5qf$3@dough.gmane.org> (raw)
In-Reply-To: <1313436905.4058.47.camel@mattotaupa>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 15-08-11 21:35, Paul Menzel schreef:
> Dear OE folks and especially Koen,
> 
> 
> Scott Davilla from the XBMC project asked me for build instructions for XBMC for the PandaBoard.
> 
> Currently the XBMC recipe does not build for the PandaBoard
> 
> COMPATIBLE_MACHINE = "omap3|ti816x"
> 
> and 'virtual/egl' is not available for `MACHINE = "omap4430-panda"` in oe.dev. Additionally the recipe is quite outdated.
> 
> This is a good occasion to update and clean up the current XBMC recipes.
> 
> I have some patches locally and I build test the latest commits for `MACHINE = "beagleboard"` unfortunately still for oe.dev. On LinuxTag you told me that you also had some patches but they conflicted with my pushed commits.
> 
> So what is the best way to go forward? Did you already do some work on this so that no wheel is reinvented? Please publish your patches somewhere. That would be awesome.
> 
> Without knowing your answer I propose the following.
> 
> 1. I try to clean up my patches and push them right to oe.dev? (I could also publish a tree on Gitorious where I am already registered.)

OE .dev is a dead end, no use working there

> Unfortunately I am only able to build test XBMC as I do not have a setup BeagleBoard or PandaBoard currently and no time to set them up.
> 
> 2. Not having used meta-oe/oe-core it would be great if you could port those to meta-oe.

Importing the current recipe into meta-oe and working on it there would be a better idea.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFOSiU1MkyGM64RGpERAtQBAJ48KoKoh7nft3HvUoSs8V7XIQA3zQCfWwPR
GMDIt8xZIIeH1HSDnxeY8Rs=
=UlFH
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2011-08-16  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15 19:35 Coordination for updating the XBMC recipe Paul Menzel
2011-08-15 21:58 ` Paul Menzel
2011-08-16  8:07 ` Koen Kooi [this message]
2011-08-16  8:22   ` Paul Menzel

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='j2d8fl$5qf$3@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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.