Build my own Vix image

[Willo3092]

I just did a 'make update' and it built 6.4.001.001

[abu baniaz]

OpenViX 6.3 is built using OE Alliance branch 5.2
OpenViX 6.4 will be built using OE Alliance branch 5.3

The branch you fork is defined at end of this line

git clone https://github.com/oe-alliance/build-enviroment.git -b 5.2

I use LraiZer's instructions

Instead of

mkdir -p ~/openvix
cd openvix

I use

mkdir -p ~/oe-a-5.2
cd oe-a-5.2

Increase the branch number as you go along. You can build ATV, OBH, ViX from that same environment, it is what you forked. All the images will have their own folder. The enigma2 branches will be defined in the conf files.

The ATV instructions previously used to say to create "openatv" directory. I convinced them to use the version number.

oe-a 5.3 commits

https://github.com/oe-alliance/oe-alliance-core/commits/5.3/meta-oe

oe-a 5.2 commits

https://github.com/oe-alliance/oe-alliance-core/commits/5.2/meta-oe

[Willo3092]

That will be why I managed to build 6.4 then. I had used the ATV latest build instructions because the ViX instructions wouldn't work for me.

[lincsat]

Done it now - I had to re-hash out the STATIC_FEED = "1" in openvix.conf

[BrianG61UK]

***Deleted***
@abu baniaz beat me to it and gave a much better, more detailed answer too.

[Huevos]

You need to create a new build env cloning the oe-alliance-core 5.3 branch. This builds ok on my old 20.04 Ubuntu and 21.04. Recommendation is 22.04.

[birdman]

You need to create a new build env cloning the oe-alliance-core 5.3 branch. This builds ok on my old 20.04 Ubuntu and 21.04. Recommendation is 22.04.

It builds on 23.04 with a few provisos.

1. /bin/sh need to be a symlink to bash. (This can no longer be done using dpkg-reconfigure.)
2. /usr/bin/python needs to exist (a symlink to python3). So python-is-python3 needs to be installed.

1. is a bug. Both should, ideally, be fixed. (1. is actually a problem in the main Makefile!)

Also, if you build rclone you'll find that go is installed under HOME and much of it is set to be read-only. This is a definite bug (no build should affect my HOME), but Captain's comment when I reported it as an issue was that this was the standard build so was not an issue. In that case, whey are there so many patch files in the build?

[BrianG61UK]

Also, if you build rclone you'll find that go is installed under HOME and much of it is set to be read-only. This is a definite bug (no build should affect my HOME), but Captain's comment when I reported it as an issue was that this was the standard build so was not an issue. In that case, whey are there so many patch files in the build?

I wondered why that go directory kept appearing.

[BrianG61UK]

Since about 6.3.008.001 my developer builds started behaving differently.

It used to be that when I did a developer build, the version number of the build would always match the last version number in the changelog of github OpenViX/enigma2/Developer.

But now, for instance with my last build just completed minutes ago (and untested) the version in the changelog was "developer 6.4.001.002" but the resulting images were:
openvix-6.4.001.001.developer-zgemmah7_multi.zip and openvix-6.4.001.001.developer-zgemmah7_recovery_emmc.zip
when I expected 6.4.001.002.

What's causing that?
Is the same happing to everyone who builds developer builds?
Maybe I just need to rename the files and the contents is correct?

[abu baniaz]

@briang61uk, which OE-A branch environment are you building from?

[Joe_90]

@Orlandox has reported that the official builds (recently completed) are numbered 6.4.001.001 also. May be a numbering increment didn't happen somewhere in the build files?

[BrianG61UK]

@briang61uk, which OE-A branch environment are you building from?

It happened with oe-a-be 5.2 building 6.3.008.00x that all came out as 6.3.008.001, and I just built a new oe-a-be 5.3 on lubuntu 22.04 LTS which I just used to build 6.4.001.00x on.

[birdman]

@Orlandox has reported that the official builds (recently completed) are numbered 6.4.001.001 also. May be a numbering increment didn't happen somewhere in the build files?

Something similar happened at the end of the 6.3 series, which meant that an attempt to update to the last one actually took you backwards and you had to reflash to the last-but-one.
This was reported by a few people at the time, bu there has been no comment as to what was happening.

I hope it isn't still happening.

[birdman]

I wondered why that go directory kept appearing.

I'm trying to make it go away.
You can easily make it appear in the build tree by setting (and exporting):

HOME=<<your-build-location>>/oe-alliance/builds/openvix/developer/${machine2}

before starting the build.

[birdman]

I'm trying to make it go away.

I now have a simple rclone.bbappend file which:

• Puts the mod install into the build tree (where it should be).
• Makes all of the files and dirs writeable by the user (so you can delete them when you delete the build directory).

# This uses go, which will download modules and, by default, place them 
# in the HOME of build user! 
# It will even make some of them read-only!!! 
# So put them within the build tree, and undo the read-only setting. 
# 

GOPATH = "${TMPDIR}/go/" 
export GOPATH 

do_compile:append() { 
    chmod -R +w "$GOPATH" 
}

Now to see whether I can get this into the meta-oe-alliance git....