I just did a 'make update' and it built 6.4.001.001
I just did a 'make update' and it built 6.4.001.001
Willo
#######################
AX HD61 4K UHD Twin (test box)
Vu+ Uno 4K SE
Edision OS Mio 4K
Zgemma H9 Twin
Vu+ Zero 4K
Vu+ Uno 4K
GT-Sat GT-S3DCSS24 Unicable II LNB
GT-Sat GT-dLNB1-DY Unicable II LNB
#######################
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
I use LraiZer's instructionsCode:git clone https://github.com/oe-alliance/build-enviroment.git -b 5.2
Instead of
I useCode:mkdir -p ~/openvix cd openvix
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.Code:mkdir -p ~/oe-a-5.2 cd oe-a-5.2
The ATV instructions previously used to say to create "openatv" directory. I convinced them to use the version number.
oe-a 5.3 commits
oe-a 5.2 commitsCode:https://github.com/oe-alliance/oe-alliance-core/commits/5.3/meta-oe
Code:https://github.com/oe-alliance/oe-alliance-core/commits/5.2/meta-oe
Last edited by abu baniaz; 15-05-23 at 16:15.
BrianG61UK (15-05-23),Willo3092 (15-05-23)
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.
Willo
#######################
AX HD61 4K UHD Twin (test box)
Vu+ Uno 4K SE
Edision OS Mio 4K
Zgemma H9 Twin
Vu+ Zero 4K
Vu+ Uno 4K
GT-Sat GT-S3DCSS24 Unicable II LNB
GT-Sat GT-dLNB1-DY Unicable II LNB
#######################
Done it now - I had to re-hash out the STATIC_FEED = "1" in openvix.conf
***Deleted***
@abu baniaz beat me to it and gave a much better, more detailed answer too.
Last edited by BrianG61UK; 15-05-23 at 16:35.
Zgemma H7S, Fixed 28.2°E dish, Freeview (Hannington). ABM Providers: [Sky UK; Thames Valley SD Custom; HD swap], [Freeview (UK); Berks and North Hants]
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.
BrianG61UK (16-05-23)
It builds on 23.04 with a few provisos.
- /bin/sh need to be a symlink to bash. (This can no longer be done using dpkg-reconfigure.)
- /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?
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
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?
Last edited by BrianG61UK; 17-05-23 at 15:03.
Zgemma H7S, Fixed 28.2°E dish, Freeview (Hannington). ABM Providers: [Sky UK; Thames Valley SD Custom; HD swap], [Freeview (UK); Berks and North Hants]
@briang61uk, which OE-A branch environment are you building from?
BrianG61UK (17-05-23)
@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?
GB Quad Plus, Mut@nt HD51, AX HD61, 80cm dish and Supreme Dark motor. Sony STR-DN 1060, Sony UHP-H1 Bluray, Odroid N2+ (CoreElec), Monitor Audio Bronze 5.1 speakers
BrianG61UK (17-05-23)
Zgemma H7S, Fixed 28.2°E dish, Freeview (Hannington). ABM Providers: [Sky UK; Thames Valley SD Custom; HD swap], [Freeview (UK); Berks and North Hants]
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.
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
BrianG61UK (17-05-23)
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
BrianG61UK (17-05-23)
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).
Now to see whether I can get this into the meta-oe-alliance git....Code:# 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" }
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
BrianG61UK (17-05-23)