Skip to contentSkip to conversation

Coordination for updating the XBMC recipe

DISCUSSION Paul Menzel 2 participants 4 messages Aug 15, 2011 – Aug 16, 2011

lore
Share & tools
lore
#0 lore raw

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.)

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.

Then building XBMC should be a piece of cake for interested persons.

Thanks,

Paul

#1 lore raw

Dear OE folks and especially Koen,

Am Montag, den 15.08.2011, 21:35 +0200 schrieb Paul Menzel:

Quoted 26 lines

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.)

Quoted 7 lines

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.

Then building XBMC should be a piece of cake for interested persons.

some more questions.

3. oe.dev: When I rename xbmc_svn.bb, which uses Git already, to xbmc_git.bb what is the policy regarding PR? Just set it back to r0?

Koen, your comments are much appreciated!

Thanks,

Paul

#2 lore raw
In reply to Paul Menzel

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

Op 15-08-11 21:35, Paul Menzel schreef:

Quoted 13 lines

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.

Quoted 7 lines

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

Quoted 3 lines

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-----

#3 lore raw

Am Dienstag, den 16.08.2011, 10:07 +0200 schrieb Koen Kooi:

Quoted 22 lines

Op 15-08-11 21:35, Paul Menzel schreef:

Quoted 13 lines

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.

Quoted 7 lines

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.)

Quoted 7 lines

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

Quoted 3 lines

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.

Looking more into it, it looks like virtual/egl is not yet available in meta-oe or oe-core. So that would be quite an effort. Additionally I only have a working oe.dev build setup right now.

Regarding the PandaBoard it looks like there is only libgles-omap3 and nothing for OMAP4. Is that correct?

Do you have some patches you could post somewhere?

Thanks,

Paul