SDK for 17.5 available

[peteru]

I am making available an SDK that can be used to build binaries for the T series running 17.5 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.

beyonwizt4-x86_64-mips32el-toolchain-17.5.20170623.sh

A newer version that matches the release candidate of 17.5 is also available:
beyonwizt4-x86_64-mips32el-toolchain-17.5.20170802.sh

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

Code: Select all

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

to set up your shell environment for the SDK.

The README file in the enigma2 source code tree has been updated to show how to build using the 17.5 SDK. Unlike the previous versions, there should be no need to copy any header files between the sysroots.

[prl]

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

Thanks. I don't have an immediate use for it, though it will, of course, be handy.

... Unlike the previous versions, there should be no need to copy any header files between the sysroots.

[prl]

I installed it and ran a test build. All ran smoothly and the toolchain was even built with the right compile options for my ancient MacBook

[peteru]

Good to hear. I invested a significant amount of time on improving the SDK and also updating the git repo build instructions and testing it all out. There are probably still areas that could use improvement, but it seems to get the main job done as is.

One of the things I'd like to improve in the future is the integration of the SDK with the Eclipse C/C++ IDE so that it's possible to cross-compile and deploy straight from the IDE. But, that's a long term, back-burner goal.

There is likely to be an update to this SDK as we approach the release of 17.5, but for the 17.5 series, I tried to take SDK upgrades into account. We'll see how it pans out.

[peteru]

An update to the 17.5 SDK is being uploaded right now and it should take about 1 hour to complete.

beyonwizt4-x86_64-mips32el-toolchain-17.5.20170706.sh

Please let me know if there are any issues with the new SDK and your experience with updating it.

[prl]

The SDK install and a configure/make from an empty directory ran cleanly, with the usual bunch of compile warnings.

All the runs of the mipsel "ar" gave a warning, though:

Code: Select all

mipsel-oe-linux-ar: `u' modifier ignored since `D' is the default (see `U')

It was the same with the 17.5.20170623 SDK. I Don't recall seeing it in builds using earlier SDKs.

[peteru]

Another update to the 17.5 SDK is available. This release is intended to match the 20170711 firmware release. I don't expect it to behave any differently to the previous SDK release.

beyonwizt4-x86_64-mips32el-toolchain-17.5.2017071.sh

[prl]

I'm currently working on a fix that needs compilation, so I'll give it a go in the next couple of days.

[prl]

I did a build from clean directory using the 17.5.20170711 toolchain without any problems.

Still getting the warnings from the mipsel "ar".

[peteru]

All good then, no changes from previous release.

[MrQuade]

Still works under Windows 10 too

[peteru]

Still works under Windows 10 too

Great, I expect some pull requests from you in the next 10 days

[peteru]

A newer version that matches the release candidate of 17.5 will also available in about an hour:
beyonwizt4-x86_64-mips32el-toolchain-17.5.20170802.sh

[prl]

OK, thanks. I'm currently working on some C++ changes, so I'll give it a go over the next couple of days.

[peteru]

The U4 SDK has been available for a while now, but I'm not sure how widely I circulated the link. Here it is:
beyonwizu4-x86_64-cortexa15hf-neon-vfpv4-toolchain-17.5.20170914.sh

[prl]

It had previously only been posted in the non-public U4 beta forum.

Good that it's available now, adoxa was asking after it recently.

[IanSav]

Hi PeterU,

The U4 SDK has been available for a while now, but I'm not sure how widely I circulated the link. Here it is:
beyonwizu4-x86_64-cortexa15hf-neon-vfpv4-toolchain-17.5.20170914.sh

Does this SDK also build the T2, T3 and T4 images or do I need to use an earlier version from further up the page?

Regards,
Ian.

[prl]

...

The U4 SDK has been available for a while now, but I'm not sure how widely I circulated the link. Here it is:
beyonwizu4-x86_64-cortexa15hf-neon-vfpv4-toolchain-17.5.20170914.sh

Does this SDK also build the T2, T3 and T4 images or do I need to use an earlier version from further up the page?
...

You need this SDK for the U4 and the ...x86_64-mips32el... SDK for the T series. The toolchain contains compiled libraries, and the T series has a different CPU architecture (MIPS) from the U4 (ARM).

The variable bits of the configure command arguments to commence the build are:
T2: --with-boxtype=inihde2 --with-nolcd
T3: --with-boxtype=inihdx --with-textlcd
T4: --with-boxtype=inihdp --with-bwlcd255
U4: --with-boxtype=et1300 --with-textlcd

I've never used the T3 config settings. I've successfully built using the other three settings arguments.

I just have a small shell script for each model that I build for that has the appropriate configure arguments.

[Edited 6 May 18 to apply adoxa's suggested corrections below]

[IanSav]

Hi Prl,

It looks like I need a build environment for OpenPLi so I thought I may as well get the Beyonwiz environment running as well.

Yes MrQuade, I am building on Ubuntu on Windows 10.

Regards,
Ian.

[IanSav]

Hi,

I tried my first build which wasn't very successful. I have attached a log of the run.

Can anyone give me pointers as to the problem. By the way "c++"is installed.

Regards,
Ian.

[adoxa]

Although there's no front panel display, the T2 still uses --with-textlcd - everything is there for it apart from the VFD display.

Why not just use --with-nolcd? That's what I've been using.

Can anyone give me pointers as to the problem. By the way "c++"is installed.

You need to install SWIG.

[prl]

...

Can anyone give me pointers as to the problem. By the way "c++"is installed.

You need to install SWIG.

That, too perhaps, but that won't stop you finding the C++ compiler for the target architecture. The error is caused when trying to compile (lib/)base/eenv.cpp for the target. The build hasn't got nearly as far as using SWIG at the point that it dies.

Ian, what's in the script called T3?

[adoxa]

Code: Select all

make[4]: Entering directory '/home/IanSav/Beyonwiz/build/lib'
  CXX      base/eenv.o
  AR       base/libenigma_base.a
mipsel-oe-linux-ar: `u' modifier ignored since `D' is the default (see `U')
  GEN      python/enigma_python.cpp
/bin/bash: -c++: command not found
Makefile:2873: recipe for target 'python/enigma_python.cpp' failed

It successfully compiles lib/base/eenv.cpp and creates the library. The problem is not lack of C++, but lack of SWIG: -c++ should be /usr/bin/swig -c++.

[prl]

yes, you're quite right.

[IanSav]

Hi Prl,

Ian, what's in the script called T3?

T3 is the script based on PeterU's instructions in the repository:

Code: Select all

#!/bin/bash
source ~/Beyonwiz/environment-setup-mips32el-oe-linux
autoreconf -i
mkdir build
cd build
../configure $CONFIGURE_FLAGS \
  BUILD_SYS=x86_64-linux \
  HOST_SYS=mipsel-oe-linux \
  STAGING_INCDIR=${SDKTARGETSYSROOT}/usr/include \
  STAGING_LIBDIR=${SDKTARGETSYSROOT}/usr/lib \
  PYTHON_VERSION=2.7 \
  PYTHON_CPPFLAGS=-I${SDKTARGETSYSROOT}/usr/include/python2.7 \
  PYTHON_LDFLAGS="-L${SDKTARGETSYSROOT}/usr/lib -lpython2.7" \
  PYTHON_SITE_PKG=${SDKTARGETSYSROOT}/usr/lib/python2.7/site-packages \
  --prefix=/usr \
  --libexecdir=/usr/lib/enigma2 \
  --sysconfdir=/etc \
  --localstatedir=/var \
  --enable-silent-rules \
  --enable-dependency-tracking \
  --with-gstversion=1.0 \
  --with-boxtype=inihdx \
  --with-textlcd
make

Installing SWIG got the run further but with all the warnings and errors I have no idea if this is normal or a problem. I am also not sure if a firmware was built or where it may have been placed.

Regards,
Ian.

[prl]

A normal build has loads of warnings. I hate it when code gets like that, because it can make it hard to spot when a useful warning is being given.

Some of the warnings may be hard to avoid, though. A lot of them come from code that SWIG has generated

Did the build run to completion and produce a main/enigma2?

[IanSav]

Hi Prl,

That level of warnings and issues is quite alarming.

Yes, there is a enigma2 in the main directory. It is about 12 MB, huge compared to the 4MB existing enigma2 on the Beyonwiz.

Doesn't the build throw out a firmware image, like in the zip file we get from PeterU?

Regards,
Ian.

[prl]

No, it just builds the enigma2 binary and lib/python/enigma.py. The latter is the glue that sticks the C++ and the Python together. You need to put both on the target system, in /usr/bin/enigma2 and /usr/lib/enigma2/python/enigma.py.

The SDK build of enigma2 still has its (quite large) symbol table. The production one has had the symbol table stripped.

[IanSav]

Hi Prl,

Is there a option or recipe to build the zip file that PeterU generates?

Regards,
Ian.

[prl]

Within the SDK, no, not as far as I know.

Why? I've never felt the need to have it.

[IanSav]

Hi Prl,

Within the SDK, no, not as far as I know.

Why? I've never felt the need to have it.

I want to build images for use with OMB (OpenMultiBoot).

Regards,
Ian.

[Paul_oz53]

Ian,

A year ago adoxa posted this as a suggestion. It seems to be the symbol table size reduction you're looking to achieve.

But, as for how to build the actual firmware, I have no idea but it would be good if you guys can figure that out, I am nervous that we have too many eggs in one basket!

Paul

[IanSav]

Hi Paul,

Thanks for the link.

Regards,
Ian.