465 replies to this topic

[littlesat]

As far I understand wanwizzard add link in repo and the text in wiki... maintain on one place.

[MCelliotG]

@MCelliotG, Why are you creating multiple templates? The whole point is the button bar just works irrespective of the object type. This is not about hiding PNGs, That is just a bonus that works for StaticText.

Because my skin does not have only one button bar. Anyway I figured out a way to do it, however I see quite a few differences between stable and dev images, so I consider making two repos for my skin. Unless all button changes are pushed for stable OpenPLi as well. It's a one way if you need to maintain compatibility with older images.

BTW the Mut@nt images are all in the stable branch?

[WanWizard]

As far I understand wanwizzard add link in repo and the text in wiki... maintain on one place.

 

No, the other way around, as the idea here is that the code should be generic, not OpenPLi specific. Not sure what the diffence is between "in our wiki" vs "in our repo" in that respect, but if you clone, you get the docs too, you don't have to go and look for them.

 

Obviously I prefer to have all documentation in one place, but who am I to dicate that...  

[Huevos]

 

@MCelliotG, Why are you creating multiple templates? The whole point is the button bar just works irrespective of the object type. This is not about hiding PNGs, That is just a bonus that works for StaticText.

Because my skin does not have only one button bar. Anyway I figured out a way to do it, however I see quite a few differences between stable and dev images, so I consider making two repos for my skin. Unless all button changes are pushed for stable OpenPLi as well. It's a one way if you need to maintain compatibility with older images.

BTW the Mut@nt images are all in the stable branch?

 

You're missing my point. Each buttonbar has to be complete with 16 elements.

 

The code required only exists in the develop branch.

[Rob van der Does]

.... however I see quite a few differences between stable and dev images,......

Yes, well, that's the whole point of haveng 'stable releases' and a dev-branch.

 

....so I consider making two repos for my skin. Unless all button changes are pushed for stable OpenPLi as well. It's a one way if you need to maintain compatibility with older images.

Now why would you do that? Older images will never be updated, so no pint in maintaining skins for them at all. A 'stable release' is what it is, and new development will be in the next stable release. You always develop on/for the latest developments = for the dev-branch.

 

The fact that no images build from the dev-branch are available doesn't really help though.....

[MCelliotG]

It's a tough call, with these changes I have delayed my updates way too much though. The problem is that if I leave the old format, in dev images some buttons will not appear (there were more changes affecting some screens such as the Harddisk Setup) and vice versa. Anyway, I might release the old format for now and update to the new one when all changes are pushed to stable images as well.

[Abu Baniaz]

The PLI skins used across the different branch images are all built from the same skin repo. So some changes cannot be made to the skins because the older images do not have the skin.py changes. What is the possibility of backporting the skin.py changes?

https://github.com/O...develop/skin.py

[Rob van der Does]

PLi's release images are so-called 'stable-images', in which no changes will be made (apart from a few minor changes that do not have any impact, like updating settings plugins).

Any update goes only to the dev-branch, and will end up in the next release image.

 

BTW: the same applies to e.g. the skins; they won't be updated either, so there is even no need to backport changes in the skin engine.

 

And that's the whole idea of 'stable images'; otherwise they wouldn't be stable 

[IanSav]

Hi Persian Prince,

Here is a test image for "beyonwizt3": http://www.mediafire...onwizt3_usb.zip

I currently run a dev build of OpenViX because it is actively updated.  Can this OpenPLi image perform online updates to bring it up to date with the current develop branch?

 

I have some new code I want to submit to OpenPLi but I don't have enough hardware to run an OpenPLi image.  Is there anyone here who would like to work with me in testing new/updated code for inclusion into OpenPLi?

 

Regards,

Ian.

 

[Huevos]

Grab OMB plugin from your ViX feeds. Then build unofficial PLi and load it in multi-boot on the T3.

[IanSav]

Hi,

 

Okay, OMB installed and I am now running an old OpenPLi, how do I get it to update?

 

Regards,

Ian.

[IanSav]

Hi,

 

I am running OpenPLi but there are no updates available, no plugins available, no networking options enabled.  I can get to OpenWebif but I can't telnet in or set any SMB shares.  The startup screen also says something about the image being unofficial.  I must have done something wrong.  How can I make this image work properly?  Any advice or help welcomed.

 

Regards,

Ian.

[twol]

Hi,

I am running OpenPLi but there are no updates available, no plugins available, no networking options enabled. I can get to OpenWebif but I can't telnet in or set any SMB shares. The startup screen also says something about the image being unofficial. I must have done something wrong. How can I make this image work properly? Any advice or help welcomed.

Regards,
Ian.

Unofficial - Thats standard for develop branch, althoug they have recently changed the Startup screen, so new builds say something a little less harsh! ... so nothing wrong. For develop, you have to run a 2nd stage to get all the plugins (build OpenPli feeds)
I assume you keep all the branches local, so you can modify and run builds

Edited by twol, 27 March 2018 - 08:08.

[IanSav]

Hi Twol,

 

I don't run a build environment.  Most of my work is in the skins and Python code.  The version of OpenPLi that was built for me appears to be severely limited.  What can I do to make it useful?

 

Regards,

Ian.

[twol]

Hi Twol,
 
I don't run a build environment.  Most of my work is in the skins and Python code.  The version of OpenPLi that was built for me appears to be severely limited.  What can I do to make it useful?
 
Regards,
Ian.

So take a „release“ version (which has live feeds) and in most cases you can ftp over your changes to the receiver skins as xml to usr/share/enigma2 (or copy over a folder and files if new) and code changes in .py to existing modules to usr/lib/enigma2.
As long as you remember to init 4, before the copy and then reboot (init 6) using something like putty, it should pick up the changes.
The difficulty is when you introduce some new feature that requires a build, due to changes in for example setup

[twol]

Ian, sorry forgot that you have a „non“ standard receiver. ... does it use the Xtrend drivers??? Think in the OE-A it comes under that „brand“

[IanSav]

Hi Twol,

 

I think the Beyonwiz T3 is based on a now defunct Venton model.

 

Regards,

Ian.

[Abu Baniaz]

The Ventons were INI receivers. You can build an unoffcial PLI image for it.

 

https://forums.openp...orted-receiver/

[twol]

The Ventons were INI receivers. You can build an unoffcial PLI image for it.
 
https://forums.openp...orted-receiver/

Thanks Abu, didn‘t know about the other Meta‘s.... teaches me to read a thread from the start!!

[IanSav]

Hi,

 

I have built a build environment on my Windows 10 PC running the Ubuntu shell.  The build process is failing with the following:

root@windows:~/openpli-oe-core/build# MACHINE="beyonwiz t3" bitbake openpli-enigma2-image
ERROR: /home/IanSav/openpli-oe-core/meta-local/recipes-local/images/my-image.bb: Unable to determine endianness for architecture 'INVALID'
ERROR: /home/IanSav/openpli-oe-core/meta-local/recipes-local/images/my-image.bb: Please add your architecture to siteinfo.bbclass
ERROR: /home/IanSav/openpli-oe-core/pli-extras/meta-ini/recipes-linux/linux-ini-hdx_3.6.0.bb: cannot map 'INVALID' to a linux kernel architecture
ERROR: /home/IanSav/openpli-oe-core/pli-extras/meta-ini/recipes-linux/linux-ini-hdp_3.14.2.bb: cannot map 'INVALID' to a linux kernel architecture
ERROR: /home/IanSav/openpli-oe-core/pli-extras/meta-ini/recipes-linux/linux-ini-hde_3.12.1.bb: cannot map 'INVALID' to a linux kernel architecture
ERROR: /home/IanSav/openpli-oe-core/pli-extras/meta-ini/recipes-linux/linux-ini-hde2_3.14.2.bb: cannot map 'INVALID' to a linux kernel architecture
ERROR: /home/IanSav/openpli-oe-core/pli-extras/meta-ini/recipes-drivers/rt8723bt_4.1.6.bb: cannot map 'INVALID' to a linux kernel architecture
ERROR: /home/IanSav/openpli-oe-core/pli-extras/meta-ini/recipes-linux/linux-ini-hdx_3.6.0.bb: linux-ini-hdx: LIC_FILES_CHKSUM contains an invalid URL: t3-oe-linux/linux-ini-hdx/3.6.0-.1/linux-3.6.0/COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7
ERROR: Failed to parse recipe: /home/IanSav/openpli-oe-core/meta-local/recipes-local/images/my-image.bb
ERROR: /home/IanSav/openpli-oe-core/pli-extras/meta-ini/recipes-linux/linux-ini-hdp_3.14.2.bb: linux-ini-hdp: LIC_FILES_CHKSUM contains an invalid URL: t3-oe-linux/linux-ini-hdp/3.14.2-.1/linux-3.14.2/COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7
ERROR: /home/IanSav/openpli-oe-core/pli-extras/meta-ini/recipes-linux/linux-ini-hde_3.12.1.bb: linux-ini-hde: LIC_FILES_CHKSUM contains an invalid URL: t3-oe-linux/linux-ini-hde/3.12.1-.1/linux-3.12.1/COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7
ERROR: /home/IanSav/openpli-oe-core/pli-extras/meta-ini/recipes-linux/linux-ini-hde2_3.14.2.bb: linux-ini-hde2: LIC_FILES_CHKSUM contains an invalid URL: t3-oe-linux/linux-ini-hde2/3.14.2-.1/linux-3.14.2/COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7
 
Summary: There were 12 ERROR messages shown, returning a non-zero exit code.

This was the first sign of any issue with the build process.

 

Can anyone suggest a resolution?

 

Regards,

Ian.