Build my own Vix image

**birdman** · 10-06-23, 19:28

Originally Posted by Huevos

So where is your static feed?

No idea.
All I do is set STATIC_FEED = "1" in my site.conf, rather than in an openvix.conf within a git reporitory.

**Huevos** · 10-06-23, 21:06

Originally Posted by birdman

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** · 11-06-23, 00:49

Originally Posted by Huevos

So you are setting static feed and you don't have a static feed?

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.

**Huevos** · 12-06-23, 20:50

Originally Posted by birdman

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** · 13-06-23, 01:13

Originally Posted by Huevos

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.

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?

**Huevos** · 13-06-23, 13:08

I'm not sure if you're on a wind up.

Originally Posted by birdman

This strikes me as weird.
If I don't need to build these things then why does the standard config build them at all?

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.

Originally Posted by birdman

And if I do need them, then surely it should rebuild them whenever they change. Not that it did them once, and then ignored them forever.

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** · 14-06-23, 01:34

Originally Posted by Huevos

I'm not sure if you're on a wind up.

Definitely not.

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."

OK. So If I set STATIC_FEED to 1 then some things do not get built at all. Ever?

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.

OK. So there is a static feed and a dynamic (== non static feed).

So if you want complete feeds you either build the whole thing without modifying that conf file, or you do 2 processes.

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).

**Huevos** · 14-06-23, 09:20

Originally Posted by birdman

If I set STATIC_FEED to 1 then some things do not get built at all. Ever?

They will never be built by the main build.

Originally Posted by birdman

OK. So there is a static feed and a dynamic (== non static feed).

There is a main feed from the build process and an additional feed built by a separate process.

Originally Posted by birdman

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?

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.

Originally Posted by birdman

(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).

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** · 14-06-23, 11:17

Originally Posted by Huevos

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}"

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".

**Huevos** · 15-06-23, 15:57

Originally Posted by birdman

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.

**judge** · 14-07-23, 01:00

Built a 6.4 release image for the original VU+ Ultimo today on a laptop in under 4 hours.
Installed image works a lot faster/snappier than the last available VIX release for this box.
Have the feeds built on the laptop in /oe-a-5.3/build-enviroment/builds/openvix/release/vuultimo/tmp/deploy/ipk & want to move them to the Ultimo hdd, no need for a build server as it's a rare box I'd need to update.
Anyone know what's the correct format I should use in the /etc/opkg conf files to point to media/hdd/feeds/ rather than the URLs?

**birdman** · 14-07-23, 02:33

Originally Posted by judge

Anyone know what's the correct format I should use in the /etc/opkg conf files to point to media/hdd/feeds/ rather than the URLs?

From the man page (there is one in the source).

Code:

       The third part consists of the repository location.  This must point to 
       the top directory containing the Packages index file.   The  repository 
       location  may  refer to a local directory on the system with the prefix 
       file://, or to a webserver with http://https://, or to  an  FTP  server 
       with ftp://.

**Huevos** · 14-07-23, 10:13

And you could set this URL in site.conf so it is already correct on the box and you don't need to edit anything.

**judge** · 14-07-23, 20:57

Originally Posted by birdman

From the man page (there is one in the source).

Code:

       The third part consists of the repository location.  This must point to 
       the top directory containing the Packages index file.   The  repository 
       location  may  refer to a local directory on the system with the prefix 
       file://, or to a webserver with http://https://, or to  an  FTP  server 
       with ftp://.

Couldn't get file:// to work.

Sent from my CPH2399 using Tapatalk

**judge** · 14-07-23, 20:59

Originally Posted by Huevos

And you could set this URL in site.conf so it is already correct on the box and you don't need to edit anything.

Away for the next week but will try that when I get back.
Any idea what the format should be to use /HDD/feeds on the box the image is installed on?

Sent from my CPH2399 using Tapatalk

Thread: Build my own Vix image

Thread Tools

Display

The Following User Says Thank You to Huevos For This Useful Post:

The Following 2 Users Say Thank You to Huevos For This Useful Post:

The Following User Says Thank You to Huevos For This Useful Post:

The Following User Says Thank You to judge For This Useful Post:

The Following 2 Users Say Thank You to birdman For This Useful Post:

The Following User Says Thank You to Huevos For This Useful Post:

Posting Permissions

Options

About

Site Links

Social Media