Thema: Build Enigma2.bb

Hello OPEN ATV team,

I created my build server using a Virtualbox VM with Ubuntu 20.04.2 and then I build the openatv image successfully.

Then, If I run:

Code:

cd ~/openatv/build-enviroment/builds/openatv/release/h9
source env.source
MACHINE=h9
MACHINEBUILD=zgemmah92s
DISTRO=openatv 
bitbake enigma2

It works fine too.

Now I want to change some files of openatv/enigma2 repo, so I cloned the repo in the openatvbuilder home folder:

Code:

cd ~
git clone git://github.com/openatv/enigma2.git -b 6.4

When try to build the local files for the first time (without any change), I run the following commands:

Code:

cd ~/openatv/build-enviroment/builds/openatv/release/h9
source env.source
MACHINE=h9
MACHINEBUILD=zgemmah92s
DISTRO=openatv
bitbake -f -c compile -b ~/enigma2/enigma2.bb

Unfortunately It doesn't work and I don't know why (see attached the log file)

Can someone check what's wrong? I was no able to find the solution in the older posts

Thanks a lot in advance,

Zitat von betacentauri

I do it the same way like you. There is only one difference I haven't compiled ATV e2 binary since a longer time.

Please try to add this:
enigma2/enigma2.bb at develop . OpenPLi/enigma2 . GitHub

If it don't work, create a patch file and add the patch to the normal e2 build.

Thanks betacentauri, I added that patch to my enigma2.bb but the problem is still there.

Looking at the error message, the problem seems to be with a file called "enigma_python.Tpo"

Code:

| arm-oe-linux-gnueabi-gcc-ranlib network/libenigma_network.a
| Unable to open file .deps/python/enigma_python.Tpo: No such file or directory
| make[4]: *** [Makefile:3306: python/enigma_python.cpp] Error 1
| make[4]: Leaving directory '/home/openatvbuilder/enigma2/lib'
| make[3]: *** [Makefile:2646: all-recursive] Error 1
| make[3]: Leaving directory '/home/openatvbuilder/enigma2/lib'
| make[2]: *** [Makefile:1161: all] Error 2
| make[2]: Leaving directory '/home/openatvbuilder/enigma2/lib'
| make[1]: *** [Makefile:599: all-recursive] Error 1
| make[1]: Leaving directory '/home/openatvbuilder/enigma2'
| make: *** [Makefile:442: all] Error 2
| WARNING: /home/openatvbuilder/enigma2/build/temp/run.do_compile.12544:1 exit 1 from 'exit 1'
| 
ERROR: Task (/home/openatvbuilder/enigma2/enigma2.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 6 tasks of which 5 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/openatvbuilder/enigma2/enigma2.bb:do_compile
Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Zitat von betacentauri

Yes, I already saw the error message, but I have no idea how to fix that.

Maybe first call again “bitbake -c cleansstate -f enigma2”

Hi betacentauri, after calling that command, the problem is still there.

Looking more in deep into the log, the problem seems to be in this line:

Code:

/home/openatvbuilder/enigma2/build/recipe-sysroot-native/usr/bin/swig -c++ -python -DSWIG_PYTHON_LEGACY_BOOL -MT python/enigma_python.cpp -MD -MF .deps/python/enigma_python.Tpo -I..  -O -nortti -nothreads -o python/enigma_python.cpp python/enigma_python.i

Looking for the files, enigma_python.Tpo and enigma_python.cpp don't exist in my enigma2 local repo.
enigma_python.cpp is in the gitignore file.

Are those files in your enigma2 local repo?

Maybe I'am missing something, but why do you not use the openembedded / yocto way of developing process?

I'am using the devshell and pydevshell to change the sources, commit changes and creating patches.

If you can bitbake the image and even enigma2 you would simply need to use a command like this:

Code:

cd ~/openatv/build-enviroment/builds/openatv/release/h9
source env.source
MACHINE=h9
MACHINEBUILD=zgemmah92s
DISTRO=openatv 
bitbake enigma2 -c devshell

From there you could also start your preferred IDE or Editor and have the environment already set up.

Please check out
3 Common Tasks — The Yocto Project (R) dev documentation and
3 Common Tasks — The Yocto Project (R) dev documentation

I hope this helps.

Zitat von 4l3x2k

Maybe I'am missing something, but why do you not use the openembedded / yocto way of developing process?

I'am using the devshell and pydevshell to change the sources, commit changes and creating patches.

If you can bitbake the image and even enigma2 you would simply need to use a command like this:

Code:

cd ~/openatv/build-enviroment/builds/openatv/release/h9
source env.source
MACHINE=h9
MACHINEBUILD=zgemmah92s
DISTRO=openatv 
bitbake enigma2 -c devshell

From there you could also start your preferred IDE or Editor and have the environment already set up.

Please check out
3 Common Tasks — The Yocto Project (R) dev documentation and
3 Common Tasks — The Yocto Project (R) dev documentation

I hope this helps.

Hi 4l3x2k, thanks a lot for your help! I didn't use the openembedded / yocto way because I didn't know what it is I just followed the instructions I found in the forum for building the enigma2 binary.

So I run that command and at the end of the process it opens a dev shell, then I edited a cpp file using nano and now I'd like to build the enigma2 binary file, so what should be the command now and where the enigma2 binary file will be stored? If I try to call bitbake from the dev shell it tries to connect to a build server but the connection fails.

Zitat von betacentauri

Swig generates the .cpp file from the .i file. And the .TPo is also generated by the build process. So cpp and Tpo are not in the repo.
What files are in the build/build/lib/python/.deps directory?

Maybe it’s a problem with Ubuntu 20. I use older Ubuntu.

And as said. Instead of searching hours the problem, there are other ways to compile e2 like I or 4l3x2k wrote.
I think it’s also possible to redirect original enigma2.bb to a local git clone. But I never did that before. I only saw it somewhere.

build/build/lib/python/.deps doesn't exist, maybe you are referring to <git>/lib/python/.deps? if yes, the folder is empty.

yes, I agree. The goal is to have a way to build my changes and then test them in my box. It doesn't matter the method.

Zitat von lordportux

Hi 4l3x2k, thanks a lot for your help! I didn't use the openembedded / yocto way because I didn't know what it is I just followed the instructions I found in the forum for building the enigma2 binary.

So I run that command and at the end of the process it opens a dev shell, then I edited a cpp file using nano and now I'd like to build the enigma2 binary file, so what should be the command now and where the enigma2 binary file will be stored? If I try to call bitbake from the dev shell it tries to connect to a build server but the connection fails.

You would not use bitbake in the devshell. Please read the section from the first link carefully.

If you are in the devshell and already edited some files you would do

Code:

../temp/run.do_configure
../temp/run.do_compile

The final binary is placed ... I do not know. Maybe it is in current working directory of the devshell. So

Code:

ls ./enigma2

You could also call the package script with

Code:

../temp/run.do_package

The package should be placed in the package directory ... something like build/tmp/deploy/ipk/<machine>. I do not know the path exactly.

I'am used to create a patch after do_compile with

Code:

git commit -A -m "MY CHANGE"
git format-patch -1

and adding the patch to the bitbake recipe's (.bb) source files or creating my own .bbappend.