27 replies to this topic

[eagleLS]

Sorry but I wanted to put ipk already compiled... your system is not good for me.

"myplugin.bb" creating a folder /myplugin into /tmp/deploy/ipk with inside my ipk's. The problem that remains is how to get the ipk into my image.
I modified the file openpli-enigma2-image.bb without results...

Help me MiLo

Many Thanks

Edited by eagleLS, 10 February 2013 - 11:49.

[tension]

Did you compile your optional packages in pli environment?
How did you modify openpli-enigma2-image.bb?

[eagleLS]

Did you compile your optional packages in pli environment?
How did you modify openpli-enigma2-image.bb?

Hi tension!

myplugin.bb added /myplugin folder feed. Into work

Added "myplugin" in DEPENDS + and added the plugin's names in ENIGMA2_PLUGINS +

but don't work..

Edited by eagleLS, 10 February 2013 - 14:07.

[christophecvr]

As far as I know, You need to build your plugin with openpli. An already build ipk will not work that way. What You can do is just copy your ipk tou your box onto hd or cf or temp flash (if not to big)
And install the ipkg with opkg install ....

[christophecvr]

Or You can extract your ipk file. Then make a .bb file with uri to the location of the extracted plugin. and add the .bb file You made to you're personal image. For that You will need to study first how to make your bb file. Think about the naming of it as this will be important to be able to find it in applications download.

[MiLo]

Sorry but I wanted to put ipk already compiled... your system is not good for me.

"myplugin.bb" creating a folder /myplugin into /tmp/deploy/ipk with inside my ipk's. The problem that remains is how to get the ipk into my image.
I modified the file openpli-enigma2-image.bb without results...

Help me MiLo

Well, now you know why we don't like ready-built ipks. The source recipes are way more useful for everyone.

[tension]

Hi Eagle!

It seems you want to install a .ipk not compiled into PLI env, then treat it as a group of files after it has been extracted as cristophecvr suggested.
It's annoying, but if you don't have the source code.....
You must provide a new .bb recipe in its new folder, and put files to be installed in that folder, as other recipes.
A simple example, new folder "recipes-support" with the structure:

ls -R meta-local/recipes-local/recipes-support
meta-local/recipes-local/recipes-support:
tns-files  tns-files.bb
meta-local/recipes-local/recipes-support/tns-files:
dvbT_a867.sh  dvbT_on  enigma2_pre_start.sh  tns_setup.sh  tvsat.sh

The .bb recipe states what and where install the files with correct permissions. Here we install a bunch of scripts in /usr/bin and a conf file in /etc:

DESCRIPTION = "Image setup/check utility scripts"
MAINTAINER = "Malo"
LICENSE = "CLOSED"
PV = "1.0"
PR = "r3"
SRC_URI = "file://* \
   "
PACKAGES = "${PN}"
FILES_${PN} = "/"
S = "${WORKDIR}"
SCRIPT_FILES = "dvbT_a867.sh enigma2_pre_start.sh tns_setup.sh tvsat.sh"
do_install() {
install -d ${D}/usr/bin
for i in ${SCRIPT_FILES}; do
  install -m 0755 ${S}/${i} ${D}/usr/bin/${i}
done;
install -d ${D}/etc
install -m 0644 ${S}/dvbT_on ${D}/etc/dvbT_on
}
inherit allarch

And finally add the new recipe to the stuff installed onto image by openpli-enigma2-image.bb recipe. That's all.

[christophecvr]

I've improved the local recipes for oscam.

The best way is first to make a brandnew fresh build off image (with make image)

Then instead off building the feeds with bitbake openpli-enigma2-feed

First run the git patch included here to remove the crappy included oscam's build.
(I just modified the pli's softcams meta file in order to build all cams except the oscam's)

Copy the recipes local folder to your openpli-oe-core

and build the feeds with

bitbake cvr-image

These recipes will build the latest avbl oscam (the experimental one) configs are in /etc/tuxbox/config/oscam with smargo support webif and ssl (libusb static into binary) Binary called oscam and
the the same oscam but with pcsc cardreader support. With this one configs are in /etc/tuxbox/config/oscam-pcsc . Also libusb,libccid and pcsclite will be installed to your box. for that reason this binary does not have staticlibusb included but dynamic linked libusb1 support. (means that libusb must be installed on box in order to run binary) Binary called oscam-pcsc

Also I added smargo uitil as independend package again but now updated to latest svnrev. (If smargo-list was installed to your box previousely it must be uninstalled first. or just remove the smargo-list binary from /usr/lib)

There where some errors concerning pcsc into local local-recipes for oscam with this revision they are solved.

Attached Files

•  RemoveOscalmFromsoftcamGitPatch.tar.gz   550bytes   25 downloads
•  Openpli30RecipeslocalWithCorrectOscam-REV3.tar.gz   11.14KB   28 downloads

Edited by christophecvr, 16 February 2013 - 13:33.