A dev build worked for me for an et80000. Just checked out out the 5.5.1 branch of OE-A and then ran a build. (No patches required).
Although looking at what my front-end script would have set for DISTRO_TYPE - it would have left it blank (things must have changed in the last few years).
From what i can see of the meta-oe-alliance/meta-oe/conf/distro/openvix.conf file it checks for DISTRO_TYPE being release - anything else is taken as developer.
Last edited by birdman; 06-01-25 at 02:57.
Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
OK, I've now had a vuultimo4k build succeed on the 5.5.1 branch. I currently have a ZGemma build going but have discovered that I had managed to use Developer (upper case D) rather than developer (lower case d) that I had been using, so it's building into a different folder. I'll correct that here and should be cooking again.
Sorry, so it is. I didn't read that far down.
Doesn't alter the fact that openvix.conf only checks for it being "release" and treats anything else as developer, e.g.
Code:IMAGE_BUILD = "${@bb.utils.contains("DISTRO_TYPE`", "release", "${BUILD_VERSION}" , "${BUILD_VERSION}.${DEVELOPER_BUILD_VERSION}", d)}"
Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
At last I've figured out my problem with building on Ubuntu 24.04 LTS - the upgrade from 22.04 had broken NordVPN, as soon as I removed and reinstalled that, the builds started working properly again.