31 replies to this topic

[linus]

Hello, i do not know that i should have done that before.

So have done that and try again the compile line you give me.

 

it make suprising things; i don t know why but it print me python line at the end.
THe last line are for exemple the line of the fonction:
"python write_task_data()"

No information about a fail or something else.

Edited by linus, 16 November 2024 - 13:49.

[WanWizard]

You need to source your build environment to get all environment variables setup, and to get the build tools in your PATH.

 

A bitbake recipe consists of a lot of different tasks, which are either bash or python.

 

You can find "write_task_data" here: https://github.com/o...ats.bbclass#L88

[linus]

Yep, but the problem is that when i use the option "-e" i don t know why it start to make action then at the end he "print" me python fonction and does nothing.

In the wiki in openpli it's the -k option that it used.
So i test:

ENIGMA2_BRANCH=release-9.0 MACHINE=vusolose bitbake -k openpli-enigma2-image

But it seems that it does exactly the same then when i compile "normaly", it does not use my repo because no error and compilation is ok.

Is there not somewhere a "meta" or a head that limit to a "git version" ? So even if you done some modification because they are "after" they do not take care because it's limited to a tag that is before?

[WanWizard]

-e doesn't do anything, it just dumps the entire build environment, so you can check all variable values, etc.

 

It allows you to see what the contents of SRC_URI is, and if it points to your own local repo clone.

[linus]

Here is the result of the -e option that i redirect to a file

 

I test an other solution:
things that has been said there:
https://forums.openp...ndpost&p=638159

 

And the same thing happen even if i remove a ";" in a line so it should never compile, it change nothing, it compile and it works...

It's really like it's stucked to a tag and do not take care of the thing that are after.

Attached Files

•  log.txt   1.6MB   3 downloads

[WanWizard]

This says your repo override works fine:

# $SRC_URI [4 operations]
#   append /opt/openpli/openpli-oe-core/openembedded-core/meta/conf/bitbake.conf:671
#     [vardepsexclude] "    APACHE_MIRROR     CPAN_MIRROR     DEBIAN_MIRROR     GENTOO_MIRROR     GNOME_GIT     GNOME_MIRROR     GNU_MIRROR     GNUPG_MIRROR     GPE_MIRROR     KERNELORG_MIRROR     SAVANNAH_GNU_MIRROR     SAVANNAH_NONGNU_MIRROR     SOURCEFORGE_MIRROR     XLIBS_MIRROR     XORG_MIRROR "
#   set /opt/openpli/openpli-oe-core/openembedded-core/meta/conf/bitbake.conf:685
#     ""
#   set /opt/openpli/openpli-oe-core/openembedded-core/meta/conf/documentation.conf:391
#     [doc] "The list of source files - local or remote. This variable tells the OpenEmbedded build system what bits to pull in for the build and how to pull them in."
#   immediate /opt/openpli/openpli-oe-core/meta-openpli/recipes-openpli/enigma2/enigma2.bb:117
#     " ${SRC_ORIGIN};branch=${ENIGMA2_BRANCH}"
# pre-expansion value:
#   " git:///opt/openpli/enigma2;branch=develop"
SRC_URI=" git:///opt/openpli/enigma2;branch=develop"

 

[linus]

But it works only for "develop" so that confirm at it does not take car of it if you lock to a version 9.0

So the test i was going to make was to switch to develop branch, so that confirm that i should do it an have no over choice then that. :/

[WanWizard]

As you can see on that snippit of output, it gets its branch from ENIGMA2_BRANCH.

 

So if you want to build enigma for a 9.0-release image ( with the 9.0-release OE ), you need to prefix your bitbake command with

ENIGMA2_BRANCH=release-9.0

and use the -e option first to verify if it is indeed set correctly. If you don't, it defaults to "develop" in enigma2.bb.

 

You can also set this permanently, in the same location as you set your SRC_ORIGIN.

[linus]

I always prefix it with ENIGMA2_BRANCH=release-9.0 and since that time it never works.
So i have test with develop branch and now it works. It fail to compile with an error on subtitle.cpp so that's good.

Will try again with the release-9.0 in the conf file to see if works.

[WanWizard]

If you do that, and -e still reports "develop", you've got problems elsewhere.

 

Like with SRC_ORIGIN, we override ENIGMA2_BRANCH in the conf file too.

[linus]

So i confirm.
If i do:
ENIGMA2_BRANCH=release-9.0 MACHINE=vusolose bitbake -k enigma2, like you see on the log:

SRC_URI=" git:///opt/openpli/enigma2;branch=develop"

So it does not take care of ENIGMA2_BRANCH=release-9.0

I add ENIGMA2_BRANCH = "release-9.0" in the file where i add the src_origin (that's the build/conf/openpli.conf file).
and do: MACHINE=vusolose bitbake -k enigma2
And now i got

SRC_URI=" git:///opt/openpli/enigma2;branch=release-9.0"

I compile it with the error i got in the release-9.0 for enigma and... I have got the error too!!
So now it works!


Thank's a lot for the information.
I could make some test now.

 

Edited by linus, 16 November 2024 - 16:45.

[WanWizard]

No worries, we're getting there.

 

I make this mistake a lot, forgetting there is a difference between shell environment variables and OE variables...