MMajoor

The problem not only occurs in nlhardwareinfo but also in cnet.podcast (and most likely many others).

In all cases it seems to be the Setinfo() which triggers the error:

  File "/usr/lib/enigma2/python/Plugins/Extensions/KodiLite/plugins/plugin.video.cnet.podcasts/default.py", line 265, in add_dir
    list_item.setInfo("mediatype", "video")
  File "/usr/lib/enigma2/python/Plugins/Extensions/KodiLite/scripts/script.module.main/lib/xbmcgui.py", line 239, in setInfo
    self.data.update(infoLabels)
ValueError: dictionary update sequence element #0 has length 1; 2 is required

Seems to be an invalid type of the second parameter or something ..

Since my knowledge of Python is basically non-existing, I can only give a solution here by modifying the plugin code. The 'real' solution should be in de KodiLite code obviously.

Solution (by modifying the plugin source):

#            list_item.setInfo("mediatype", "video")   -> replaced by next line
            list_item.setInfo("video", {"mediatype": "video"})

Or, you could use a Docker image with all the necessary building tools inside it:

https://forums.openp...ndpost&p=631723

Use:

  ./openembedded.sh openpli vuduo master-next

when using the supplied compile script.

If I recollect correctly, it is the same issue I had some time ago.

Had to do with the host system itself.

To make a long story short: I switched to using a Docker image for the compilation (see topic https://forums.openp...post&p=631723).

With such a Docker image, no matter if your host system changes, you will always be using the same compilation environment (think of it as a virtual machine).

No problem here finding bitbake when sourcing env.source

sudo docker run --rm --user openembedded -v $(pwd):/opt/openembedded -t -i --workdir /opt/openembedded openembedded/ubuntu:14.04
openembedded@d5a75ed186d1:/opt/openembedded$ cd openpli_hd2400_master_20161230/
openembedded@d5a75ed186d1:/opt/openembedded/openpli_hd2400_master_20161230$ cd build/
openembedded@d5a75ed186d1:/opt/openembedded/openpli_hd2400_master_20161230/build$ cd build/
openembedded@d5a75ed186d1:/opt/openembedded/openpli_hd2400_master_20161230/build/build$ source env.source
openembedded@d5a75ed186d1:/opt/openembedded/openpli_hd2400_master_20161230/build/build$ echo $PATH
/opt/openembedded/openpli_hd2400_master_20161230/build/openembedded-core/scripts:/opt/openembedded/openpli_hd2400_master_20161230/build/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
openembedded@d5a75ed186d1:/opt/openembedded/openpli_hd2400_master_20161230/build/build$ bitbake
Nothing to do.  Use 'bitbake world' to build everything, or run 'bitbake --help' for usage information.
openembedded@d5a75ed186d1:/opt/openembedded/openpli_hd2400_master_20161230/build/build$ cd ..
openembedded@d5a75ed186d1:/opt/openembedded/openpli_hd2400_master_20161230/build$ ls
bitbake               CC-BY-NC-ND-4.0  meta-dream     meta-gi     meta-miraclebox    meta-spycat  meta-xp       meta-xtrend        recreate_feed
branding.conf.sample  LICENSE          meta-edision   meta-hd     meta-openembedded  meta-vuplus  meta-xpeedc   meta-zgemma        scripts
build                 Makefile         meta-formuler  meta-local  meta-openpli       meta-wetek   meta-xsarius  openembedded-core  site.conf
openembedded@d5a75ed186d1:/opt/openembedded/openpli_hd2400_master_20161230/build$ bitbake
The BBPATH variable is not set and bitbake did not find a conf/bblayers.conf file in the expected location.
Maybe you accidentally invoked bitbake from the wrong directory?
DEBUG: Removed the following variables from the environment: LANG, LESSCLOSE, LANGUAGE, SHLVL, OLDPWD, HOSTNAME, LESSOPEN, LC_ALL, LS_COLORS, _

@pepinoogorino

Could you write, how to compile ...

That wat is run inside a container is -exactly- the same as you would do on a 'normal' system, so all the information about compiling specific recipes applies to a container as well.

I never did some individual compilation of recipes and such, so I can't help you with the correct parameters and calls for that (other than what the makefile help suggests).

I suggest you start the container in terminal mode and 'play' around with it.

By 'play' I mean just entering the commands you normally enter to do a checkout and/or compilation.

For example, start the container in terminal mode:

> sudo docker run --rm --user openembedded -v $(pwd):/opt/openembedded -t -i --workdir /opt/openembedded openembedded/ubuntu:14.04

# mkdir mycheckout

# cd mycheckout

# git clone https://github.com/o...openpli-oe-core builddirectory

# cd builddirectory

# make

# MACHINE=vusolo4k bitbake enigma2-plugin-extensions-serviceapp

Once you succeed in getting the all the commands and parameters correcly you can put the commands you entered directly in a script (just to automate things). Or make multiple simple scripts rather than one large script that should 'do it all'.

Scripts I can think of:

1. do a checkout of the repositiory

2. do an update

3. do a compilation

1. checkout.sh:

#!/bin/bash
mkdir mycheckout
cd mycheckout
git clone https://github.com/openpli/openpli-oe-core builddirectory

2. update.sh:

#!/bin/bash
cd mycheckout
cd builddirectory
make update

3. compile.sh:

#!/bin/bash
cd mycheckout
cd builddirectory
MACHINE=vusolo4k bitbake enigma2-plugin-extensions-serviceapp

And then use them like so:

> sudo docker run --rm --user openembedded -v $(pwd):/opt/openembedded --workdir /opt/openembedded openembedded/ubuntu:14.04 checkout.sh

> sudo docker run --rm --user openembedded -v $(pwd):/opt/openembedded --workdir /opt/openembedded openembedded/ubuntu:14.04 update.sh

> sudo docker run --rm --user openembedded -v $(pwd):/opt/openembedded --workdir /opt/openembedded openembedded/ubuntu:14.04 compile.sh