Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...
Build my own Vix image
- Thread starter Willo3092
- Start date
Willo3092
ViX Beta Tester
I have been uncommenting the static feed line in openvix conf which seems to save a lot of build time.
But every time I perform a 'make update', I get this error message.
Is it possible that the static feed can be uncommented as default or will that cause issues?
But every time I perform a 'make update', I get this error message.
Code:
willo@willo-OptiPlex-7010:/media/willo/USB-SSD/build-enviroment$ make update
Updating Git repositories...
remote: Enumerating objects: 119, done.
remote: Counting objects: 100% (119/119), done.
remote: Compressing objects: 100% (72/72), done.
remote: Total 119 (delta 57), reused 85 (delta 47), pack-reused 0
Receiving objects: 100% (119/119), 13.67 KiB | 4.56 MiB/s, done.
Resolving deltas: 100% (57/57), completed with 2 local objects.
From https://github.com/oe-alliance/build-enviroment
e450e648..2871255d 5.3 -> origin/5.3
cbaac844..762a0100 5.2 -> origin/5.2
Fetching submodule meta-oe-alliance
From https://github.com/oe-alliance/oe-alliance-core
80f7ea222c..dfecd4c729 5.2 -> origin/5.2
0b0edb2004..b7ae5d0490 5.3 -> origin/5.3
Updating e450e648..2871255d
Fast-forward
meta-oe-alliance | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Synchronising submodule url for 'bitbake'
Synchronising submodule url for 'meta-clang'
Synchronising submodule url for 'meta-oe-alliance'
Synchronising submodule url for 'meta-openembedded'
Synchronising submodule url for 'meta-python2'
Synchronising submodule url for 'meta-qt5.15'
Synchronising submodule url for 'openembedded-core'
error: Your local changes to the following files would be overwritten by checkout:
meta-oe/conf/distro/openvix.conf
Please commit your changes or stash them before you switch branches.
Aborting
fatal: Unable to checkout 'b7ae5d049075f31b6c21e11b6f0fd9cb0dc2d4ae' in submodule path 'meta-oe-alliance'
The oe-alliance is now up-to-date.Is it possible that the static feed can be uncommented as default or will that cause issues?
birdman
Moderator
Is it possible to set the variable in your own site.conf file?
Willo3092
ViX Beta Tester
I don't know. How would I do that?
Willo3092
ViX Beta Tester
No, sorry. I haven't got a webcam. Email & SMS are enough for me.
Don,t need a webcam!
Never thought of that. I've just tried it and it seems to build a ZGemma H7 image OK. I'm away for a few Days and can't test build for other boxes until I return.
birdman
Moderator
Put a site·conf file into the oe-alliance directory.
Mine looks like this:
Although I actually keep this elsewhere and do this in oe-alliance:
Code:
rm -f site.conf builds/openvix/developer/${machine2}/conf/site.confBut that's because I might do the build on any of a few systems, and they have different numbers of processors, so I want to clear out that setting (which the build will put in the machine2 version once it starts).
So where is your static feed?
birdman
Moderator
No idea.
All I do is set STATIC_FEED = "1" in my site.conf, rather than in an openvix.conf within a git reporitory.
So you are setting static feed and you don't have a static feed?
birdman
Moderator
Possibly.
The only comments I've seen (and remember) about this variable is to just uncomment it - no mention of having to put something else in place.
There's no mention in the openvix.conf file about setting something else up.
But the request was for a way to set this without changing the openvix.conf file. Which setting it in site.conf does.
I it called STATIC FEED. The reason the time is saved is because you are skipping a load of stuff in the build. The static feed you build additionally to the main build so those resource hungry items are not built on every rebuild.
birdman
Moderator
This strikes me as weird.
If I don't need to build these things then why does the standard config build them at all?
And if I do need them, then surely it should rebuild them whenever they change.
I'd assumed that setting STATIC_FEED just turned off some builds. Not that it did them once, and then ignored them forever.
So what should I be doing?
I'm not sure if you're on a wind up.
This is just the same as the picon feed, I don't rebuild it on every run, I build it when server resources are available.
Just because someone named the feed STATIC doesn't mean it is static. It is just an additional feed that is not built in sync with the main build.
So if you want complete feeds you either build the whole thing without modifying that conf file, or you do 2 processes.
Example: Nodejs
Typical compile time for this one package is 2 hours.
OpenViX builds 60 boxes.
Standard build would be around 120 hours of server time wasted.
STATIC feed. Just build for mips32el, cortexa7hf-vfp, and cortexa15hf-neon-vfpv4. Build time 6 hours total. Now put that on the static feed and it feeds all 60 boxes.
Build time saved 114 hours.
And that is a simple example of just one package.
If they're not built they won't be on the feeds. I have no clue whether YOU need them or not, but if we didn't build them there would be a lot of complaining.
That is not what I said. I said, "The static feed you build additionally to the main build so those resource hungry items are not built on every rebuild."
This is just the same as the picon feed, I don't rebuild it on every run, I build it when server resources are available.
Just because someone named the feed STATIC doesn't mean it is static. It is just an additional feed that is not built in sync with the main build.
So if you want complete feeds you either build the whole thing without modifying that conf file, or you do 2 processes.
Example: Nodejs
Typical compile time for this one package is 2 hours.
OpenViX builds 60 boxes.
Standard build would be around 120 hours of server time wasted.
STATIC feed. Just build for mips32el, cortexa7hf-vfp, and cortexa15hf-neon-vfpv4. Build time 6 hours total. Now put that on the static feed and it feeds all 60 boxes.
Build time saved 114 hours.
And that is a simple example of just one package.
birdman
Moderator
Definitely not.
OK. So If I set STATIC_FEED to 1 then some things do not get built at all. Ever?
OK. So there is a static feed and a dynamic (== non static feed).
So if I'm not interested in things like Nodejs (I only really build things so I can test changes to the compiled enigma2) I just do a static feed?
(If so, it's still odd, as it appears to me that setting STATIC_FEED builds the dynamic parts - so I think I may still be misunderstanding).
They will never be built by the main build.
There is a main feed from the build process and an additional feed built by a separate process.
Yes, STATIC_FEED to 1 as explained above by LraiZer.
But... maybe you should read the readme. Setting STATIC_FEED to 1 skips just a few resource hungry things (like nodejs, kodi, etc), but still builds everything else.
What you wanted to do was "only really build things so I can test changes to the compiled enigma2". To achieve that, instead of doing "make image" do "make enigma2-image".
This skips building/rebuilding a lot of stuff and cuts the task list in half. If you run "make enigma2-image" on an interim build it will just freshen up the modules you want to update. It will not run oe-alliance-feeds.bb.
As above, STATIC_FEED=1 just circumvents a few resource hungry recipes.
If you actually want the "static" feed you need to add the lines that produce the opkg files, pointing to your or the official OpenViX static feed.
Code:
STATIC_FEED = "1"
STATIC_ARCH = "static-${MACHINE} static-${TUNE_PKGARCH}"
STATIC_DISTRO_FEED_URI = "http://www.openvix.co.uk/feeds/${DISTRO_NAME}-static/${DISTRO_VERSION}"birdman
Moderator
And that highlights my problem with understanding.
To skip building the (probably unused) build resource hogs I set STATIC_FEED = "1".
But to build them I also set STATIC _FEED = "1".
STATIC_FEED=1 means I have a static feed so don't want to build those extras. STATIC_FEED=0 is the default, i.e I don.'t have a static feed so build the extras. Or in your case you don't have a static feed and don't care about the extras so just set to 1.
Obviously you can only do that because you are the sole user of your build.
