openvix dev build instructions

[LraiZer]

Is there any reason to build nodejs?

OpenWebif update moment.js from 2.14.1 to 2.29.1

https://github.com/E2OpenPlugins/e2openplugin-OpenWebif/commit/d276fd64a4ed0600c4e812f047888f8ded24476c

 

[LraiZer]

I don't think nodejs is really needed, but OpenWebif is the only reference i can find and does install it during build.

https://github.com/E2OpenPlugins/e2openplugin-OpenWebif/blob/master/.github/workflows/build.yml#L58

 

[Huevos]

I removed it from our build some time ago and nothing complains as far as I know. And nothing seems to link to the .bb file except oe-alliance-feeds.

 

[Huevos]

Just update the domain. Then afterwards you make a feeds folder in your web server root and symlink to the ipk folders. I'll post my link creation command later.

Ok, on mine I do this (/var/www is the webserver root):

mkdir -p /var/www/feeds/openvix/developer/6.2/vuultimo4k
ln -s /home/openvix/6.2/builds/openvix/developer/vuultimo4k/tmp/deploy/ipk/* /var/www/feeds/openvix/developer/6.2/vuultimo4k

 

[LraiZer]

I removed it from our build some time ago and nothing complains as far as I know. And nothing seems to link to the .bb file except oe-alliance-feeds.

Well it was add by atvcaptain 5 years ago, maybe ask if captain remembers reason to add this beast?

https://github.com/oe-alliance/oe-alliance-core/commit/bdc3d24fed3f20fde905abcbc6a52b3b948ecf18

 

[Huevos]

I think media portal requires it but OpenViX don't have that as it is not open source.

 

[Ev0]

I think media portal requires it but OpenViX don't have that as it is not open source.

Correct it was for mediaportal, but that A) as you say is not open source and B) doesn't work with Py3 anyway (well not officially).

 

[birdman]

You should still use at least 8GB swap along with the 16GB ram.

I have 16GB of swap and 16GB of RAM.
I've never actually seen the swap be used whilst running a build (and that includes building nodejs).
If the swap were ever used then you'd be adding a lot of time to a build.

 

[Huevos]

nodejs and QT both peak over 24GB in my build.

 

[twol]

nodejs and QT both peak over 24GB in my build.

that's also my (bad) experience

 

[birdman]

nodejs and QT both peak over 24GB in my build.

I've just run a build from scratch (kept sources) of 6.2.002.004.
On a system with 8 CPUs and 16GB of memory the maximum memory usage, according to sar, was 80% and there is no sign of paging.

I just let it run with the standard CPU count setting, as since both bitbake and several (many?) of the individual builds all try to use all of the CPUs they are always well overcommitted (my run-q size hovers around 40 and reached >70 at a maximum).

I believe you increase yours - which may be the cause of paging, as all it will do is leave more processes running but waiting (and hence consuming memory).

 

[twol]

Luck! If you get only nodejs and qt building at the same time ( that is just 2 streams) you can hit 34 gb (no swapping - I have excess memory on my PC ) and all 16 cpus running

 

[ronand]

Even with 24GB RAM I've needed to use a swap file on my old i7 920 (8 threads). Currently using an equally old 4th gen i5 machine (4 threads) with 8GB RAM and 16GB swap and its building OK.

 

[birdman]

Luck! If you get only nodejs and qt building at the same time ( that is just 2 streams) you can hit 34 gb (no swapping - I have excess memory on my PC ) and all 16 cpus running

You could add one to the DEPENDS of the other, which will stop them being built at the same time.
Probably requires that you are building both, as I can't find a way to make that conditional on the other being set to build anyway.

 

[littlejim]

There are two parameters in your site.conf that influence how many threads you have running at a time.

I build on a system with only 4 logical CPUs, and they seemed to deafult to:

BB_NUMBER_THREADS = "4"
PARALLEL_MAKE = "-j 4"

for me. (both equal to the number of logical CPUs). A strategy that should be a good choice for building as fast as possible.

The first one controls how many bitbakes run at a time.
The second controls how many threads some of the various bit of software that bitbake uses can use.

So, for example, the above values mean up to 4 bitbakes can be running and they can each be using up to 4 threads.
This means that potentially there can be a lot more threads running than is needed to use all 4 logical CPUs, all using up RAM.

You can actually reduce the numbers and still be utilizing the full power of all your logical CPUs almost all of the time while greatly reducing the amount of RAM you'll need to ensure your build never crashes due to running out of RAM. It works best on systems with good fast I/O (an SSD).

If you have a large number of logical CPUs and are having trouble due to running out of RAM try experimenting with the values.
You're likely to find your builds really don't take much longer if you reduce the values a bit.
I think reducing the second parameter is likely to be the most useful, but you can try various combinations.

 

[birdman]

Luck! If you get only nodejs and qt building at the same time ( that is just 2 streams) you can hit 34 gb (no swapping - I have excess memory on my PC ) and all 16 cpus running

Perhaps not so lucky, really.

Just realized that my systems don't build qt (they do build nodejs).

 

[Huevos]

Can you give one good reason you are building nodejs?

 

[birdman]

Can you give one good reason you are building nodejs?

Because if I don't need it the standard Vix build shouldn't be building it for me - it should disable it.

 

[Huevos]

It is not in the "standard" ViX build, Release or Dev.

 

[bbbuk]

Hi,

I've decided to give building new openvix ago using this guide.

However, I'm getting stuck on step 1 (yes step 1 haha).

It is failing to find gcc-8 package. The error I get is:-

Package gcc-8 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'gcc-8' has no installation candidate

Removing gcc-8 from the list of packages to install, I can then install the rest of the packages without an issue.

I've stopped after this point as don't want to proceed further until I get gcc-8 installed.

I'm using Ubuntu 22.04.1

Anyone any ideas?