SDK 16.1.20170311 available

[peteru]

I am making available an SDK that can be used to build binaries for the T series running 16.1 firmware. The SDK is created from the T4 build tree, but it should generate binaries that will work on T2, T3 and T4.

It requires a modern 64-bit Linux distribution and is provided as an install script. The installer will perform the correct relocation of the SDK to your installation directory. Please be aware that you can not simply move the installed SDK to a new place. You also can not use soft links to alias the SDK. Doing either will break things in subtle and unsubtle ways.

http://peteru.net/beyonwizt4-x86_64-mip ... 0170311.sh

If you install the SDK in the default location, you will need to:

Code: Select all

source /opt/beyonwiz/beyonwizt4/16.1.20170311/environment-setup-mips32el-oe-linux

to set up your shell environment for the SDK.

I have not had a chance to test with this version of the SDK. You might find that the x86_64 sysroot is missing some Python includes. One workaround is to copy the missing files from the mips32el sysroot.

[adoxa]

Is any particular distro recommended? I'm looking at getting a VirtualBox image from VirtualBoxes or OSBoxes.

[prl]

I'm running Ubuntu 16.04 LTS inside VirtualBox on a Mac.

[adoxa]

Okay, getting Ubuntu 16.04.2 ISO (may as well get the whole thing, after all).

[peteru]

It's built on a Gentoo ~amd64 system. Ubuntu is probably OK.

[adoxa]

Got it working (with thanks to prl for the configure command, from the 4.4 SDK topic).
The supplied perl gave me locale errors (the installed perl is fine), but otherwise worked okay.
Did the sysroots Python copy (assuming I needed to, which it seemed I did).
Had to install swig, but had no issues with it (presumably because I had no previous version).
So many warnings! I addressed a few and meant to add -Wno-sign-compare to CFLAGS to remove a couple more, but I guess there's not much to be done about swig & po warnings.
For reference, here's how I configured (for a T2):

Code: Select all

../easy-ui-4/configure -C --enable-silent-rules $CONFIGURE_FLAGS --prefix=/usr --libexecdir=/usr/lib/enigma2 --sysconfidr=/etc --sharedstatedir=/com --localstatedir=/var --with-gstversion=1.0 --with-boxtype=inihide2 --with-nolocd

[/size]

[prl]

The configure incantation comes from peteru, not me. I may have just been repeating it where you saw it.

I've stashed mine in a script file so it is easier to find/use.

[peteru]

New(ish) build environments require the build locale to be "C" or "US.utf-8" to avoid issues due to localisation interfering. It's changed a couple of times over the last few months. There were also some issues with the build environment not working properly on the very latest glibc. I think Ubuntu is still on 2.23, which works, but 2.24 had issues.

Your configure command looks a little sparse, but if it gives usable binaries, then it's all good.

[adoxa]

Your configure command looks a little sparse, but if it gives usable binaries, then it's all good.

There's no need for most of the directory settings, since they take their default from --prefix; the CONFIGURE_FLAGS variable contains all the build/host/target stuff; the STAGING stuff is used by bitbake, not configure; and I believe dependency tracking is default (not that I care if it's not).

Not entirely related, but not entirely unrelated either, is mcut (the binary that does "Execute cuts"). I had lost a couple of recordings because mcut stopped prematurely, but still indicated success. I was able to build it on Windows, where it worked fine. Building it with the SDK and putting it back on the box also worked fine, so I guess the supplied plugin is using an older version. Since it's included with the release, shouldn't its source be part of easy-ui-4, too?

[peteru]

I've split the topic so that the unrelated conversation about mcut.cc can be continued elsewhere.

[MrQuade]

I am guessing that with today's new beta firmware, a new toolchain will be coming?

Just question regarding prl's helpful post with the additional steps required to use the toolchain.

One of his steps includes copying some files (example using the 4.4 toolchain):

Code: Select all

sudo cp /opt/beyonwiz/beyonwizt4/4.4.20150709/sysroots/mips32el-oe-linux/usr/include/python2.7/* /opt/beyonwiz/beyonwizt4/4.4.20150709/sysroots/x86_64-beyonwizt4sdk-linux/usr/include/python2.7/

Why is this step necessary, and can it instead be baked into the toolchain installation script?

Also, is it possible/appropriate for the toolchain installation script to also unzip a pre-made configure script for easy-ui-4 for a t2, t3, and t4, into the current directory?

[prl]

...

Code: Select all

sudo cp /opt/beyonwiz/beyonwizt4/4.4.20150709/sysroots/mips32el-oe-linux/usr/include/python2.7/* /opt/beyonwiz/beyonwizt4/4.4.20150709/sysroots/x86_64-beyonwizt4sdk-linux/usr/include/python2.7/

Why is this step necessary, and can it instead be baked into the toolchain installation script?

It's necessary because header files that are supposed to be in the host side of the toolchain are missing. I don't know why they're missing, but I think that simply having them in the toolchain script would be better than copying them, since they need not necessarily be the same.

Also, is it possible/appropriate for the toolchain installation script to also unzip a pre-made configure script for easy-ui-4 for a t2, t3, and t4, into the current directory?

I think that would be very helpful.

[prl]

I am guessing that with today's new beta firmware, a new toolchain will be coming?
...

It may be, but I don't think it's necessary to build the enigma2 binary, or even changes the outcome when you do. The build of the enigma2 binary doesn't build the Python .pyo files. It's the build of the .pyo files that peteru's changes to the toolchanin affect.

But if there is one coming, please remember my ancient CPU!

[MrQuade]

It may be, but I don't think it's necessary to build the enigma2 binary, or even changes the outcome when you do. The build of the enigma2 binary doesn't build the Python .pyo files. It's the build of the .pyo files that peteru's changes to the toolchanin affect.

Ahh ok, I wasn't sure what PeterU had meant by this comment in the beta thread.