Build my own Vix image

[birdman]

One odd 6.3.x to 6.4.x change is that some parts procps now uses libncursesw rather than libncurses.

Why anything would want to use wide-chars on a Linux system is a mystery and why it would change now is even more of one.

(Only noticed this as the editor I use links against libncurses and it stopped working - for a while).

[BrianG61UK]

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.

I think Huevos has just fixed it:

https://github.com/oe-alliance/oe-alliance-core/commit/9f6612efcfbacbef36d40b04448eaca3c1497c0b

[Huevos]

I think Huevos has just fixed it:

https://github.com/oe-alliance/oe-alliance-core/commit/9f6612efcfbacbef36d40b04448eaca3c1497c0b

There is an override in layer.conf, which breaks using ?= syntax for DEVELOPER_BUILD_VERSION in distro.conf.

[lincsat]

I've just built my first image for a ZGemma H9 Twin SE. The image is correctly named as openvix-6.4.001.004.developer-zgemmah9twinse but it builds into a folder called h9combose. I know it's not a problem and the combo and twin are the same base, just thought I'd mention it in case that shouldn't happen.

BTW, I think I'm missing something, how do I turn subtitles off by default? Can't remember how I did it on other boxes and can't see a switch anywhere.

[abu baniaz]

I've just built my first image for a ZGemma H9 Twin SE. The image is correctly named as openvix-6.4.001.004.developer-zgemmah9twinse but it builds into a folder called h9combose. I know it's not a problem and the combo and twin are the same base, just thought I'd mention it in case that shouldn't happen.

It should happen.

[birdman]

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

PR submitted:
https://github.com/oe-alliance/oe-al...-core/pull/825