10 replies to this topic

[athoik]

Hello,

 

 

I would like to guide/help me with the building of custom images using recipes-local.

 

When you want to put something extra into the image (my-image.bb) you simply appending this to IMAGE_INSTALL.

 

 

IMAGE_INSTALL += "enigma2-plugin-my-custom-plugin"

 

Above is clear and wors like a charm.

 

 

When you want to remove something from the image (eg ppanels) how can you do that?

 

 

IMAGE_INSTALL -= "enigma2-plugin-extensions-ppanel"

 

Above probably is not valid, so the simpler way is to copy openpli-enigma2-image.bb, make changes and save it as my-image.bb?

 

 

When you want to add a modified version of pliHD skin you need to use my-pliHD and use RPROVIDES,RREPLACES? Or just adding modified pliHD into local-recipes will use the modified version over the original one?

 

Sorry for making all those questions, but i don't want to reinvent the wheel and done things by the hard way.

 

Thanks,

Edited by athoik, 13 September 2013 - 21:01.

[Erik Slagter]

Sorry for making all those questions, but i don't want to reinvent the wheel and done things by the hard way.

Not at all, I am very interested in the answer as well  . I think you have very good points.

[MiLo]

You can create a .bbappend for any script you like, and then overwrite things.

An example of how to "delete" things is in ntfs-3g-ntfsprogs_2013.1.13.bbappend:

RDEPENDS_ntfs-3g := "${@bb.data.getVar('RDEPENDS_ntfs-3g',d,1).replace('util-linux-mount', '')}"

(The ":=" is important, it forces bitbake to evaluate it "now" instead of later, when used, like make does)

[athoik]

Million thanks MiLo,

This is what i did on my-image.bb

IMAGE_INSTALL := "${@bb.data.getVar('IMAGE_INSTALL',d,1).replace('openpli-bootlogo', '')}"
IMAGE_INSTALL := "${@bb.data.getVar('IMAGE_INSTALL',d,1).replace('enigma2-plugin-skins-pli-hd', '')}"
IMAGE_INSTALL := "${@bb.data.getVar('IMAGE_INSTALL',d,1).replace('enigma2-plugin-extensions-ppanel', ' ')}"

But when i was trying to build vusolo2 i was getting "vuplus-initrd-vusolo2vuplus-initrd-vusolo2vuplus-initrd-vusolo2" missing RDEPENDS.

So i change it like this and build workd on vusolo2 too.

IMAGE_INSTALL := "${@bb.data.getVar('IMAGE_INSTALL',d,1).replace('openpli-bootlogo', '').replace('enigma2-plugin-skins-pli-hd', '').replace('enigma2-plugin-extensions-ppanel','')}"

Now i am trying to change also the spinner but i think the code do_openpli_branding needs change in order to support changing spinner too.

if [ -n "${BRANDINGDIR}" -a -d "${BRANDINGDIR}/enigma2" ] ; then
- cp -p ${BRANDINGDIR}/enigma2/* ${S}/data/.
+ cp -rp ${BRANDINGDIR}/enigma2/* ${S}/data/ 
fi

Using "cp -p ${BRANDINGDIR}/enigma2/* ${S}/data/." you cannot copy subfolders.

cp: omitting directory `/.../enigma2/skin_default'

PS. In order to use BRANDINGDIR you must run bitbake like this MACHINE=XXX BRANDINGDIR=YYY bitbake my-image correct?

Edited by athoik, 15 September 2013 - 13:37.

[athoik]

Here is the exact message appears when trying to build vusolo2:

 

ERROR: Nothing RPROVIDES 'vuplus-initrd-vusolo2vuplus-initrd-vusolo2vuplus-initrd-vusolo2' (but /opt/openpli/openpli4/meta-local/recipes-local/images/my-image.bb RDEPENDS on or otherwise requires it)

 

Something is wrong on vuplus-initrd-vuduo2.bb (or vuplus-initrd.inc)?

Edited by athoik, 15 September 2013 - 16:17.

[Erik Slagter]

Interesting, I don't see this.

Since when is this?

[athoik]

When using my-image.bb where the following exists:

 

 

IMAGE_INSTALL := "${@bb.data.getVar('IMAGE_INSTALL',d,1).replace('openpli-bootlogo', '')}"
IMAGE_INSTALL := "${@bb.data.getVar('IMAGE_INSTALL',d,1).replace('enigma2-plugin-skins-pli-hd', '')}"
IMAGE_INSTALL := "${@bb.data.getVar('IMAGE_INSTALL',d,1).replace('enigma2-plugin-extensions-ppanel', ' ')}"

 

This happens only on solo2 (and i think on duo2).

Edited by athoik, 15 September 2013 - 16:53.

[MiLo]

Don't use ":="

[athoik]

I will try without ":="

 

What about the spinner?

 

Now i am trying to change also the spinner but i think the code do_openpli_branding needs change in order to support changing spinner too.

if [ -n "${BRANDINGDIR}" -a -d "${BRANDINGDIR}/enigma2" ] ; then
- cp -p ${BRANDINGDIR}/enigma2/* ${S}/data/.
+ cp -rp ${BRANDINGDIR}/enigma2/* ${S}/data/ 
fi

Using "cp -p ${BRANDINGDIR}/enigma2/* ${S}/data/." you cannot copy subfolders.

cp: omitting directory `/.../enigma2/skin_default'

PS. In order to use BRANDINGDIR you must run bitbake like this MACHINE=XXX BRANDINGDIR=YYY bitbake my-image correct?

 

Thanks again.

[athoik]

Recursive add contents of BRANDINGDIR to enigma2 data directory.

 

 0001-Recursive-add-contents-of-BRANDINGDIR-to-enigma2-dat.patch.txt   938bytes   38 downloads

 

Using this patch you can customize also files under subfolders, eg the spinner.

 

Patch is for upstream.

[athoik]

Hello,

 

Maybe a silly question, is it possible to add 3rd-party plugin on image when you are building it?

 

There is no bitbake to add in IMAGE_INSTALL, so what is the best way to do that, create custom bitbake in meta-local?

 

Thanks once again.