Openvix - wwio bre2ze4k ! Coming ?

[Kittybuablueyoshibabygafi]

Hello, I'm new to you! build many images at home on the PC like tuxbox, neutrino, pli, etc. my question is whether you can also include the wwio bre2ze4k in the openvix image! just building it for testing! an hd51 image also runs on the bre2ze4k but the front display doesn't show the time! I would be happy if a wwio bre2ze4k was added to openvix! thanks

[abu baniaz]

OpenATV build the image. If that works, you can build the image for it for ViX. If there are not any enigma2 changes for it in ATV, it should just work. Otherwise, you will have to add the E2 changes.

[Kittybuablueyoshibabygafi]

Ok thank you I'm building the bre2ze4k image since today! everything is there with the git atv which I also see other images but the openvix is ​​the best for me! build ok but would it be possible so that it comes directly to the openvix image so with you in downloads? That would be great

[Kittybuablueyoshibabygafi]

Hello dear vix forum! Question please - when I build this rust-llvm-native 1.59.0-r0 always comes and after 1-2 hours it is only at 1%? does anyone know what this file is for or can i comment it out somehow if not necessary? I'm building a lot of images tuxbox, neutrino, tango ni, pli, and many more but I never had to wait that long! after a few hours this file is only at not even 10%! did not have this file with any construction until now! thanks ! build for wwio bre2ze4k box !

[Huevos]

No idea. Why dont you just build the image, not the feeds.

[Kittybuablueyoshibabygafi]

Thanks! I build the Image without the feeds ! Rust llvm is here :(

MACHINE=bre2ze4k DISTRO=openvix DISTRO_TYPE=release make enigma2-image

[Willo3092]

No idea. Why dont you just build the image, not the feeds.

How do you build without feeds? I may bring my SF4008 out of retirement.
Sorry for jumping on the thread, I'll post in the image building thread if you prefer.

[Kittybuablueyoshibabygafi]

https://github.com/OpenViX/enigma2

Without feeds :

MACHINE=xxxxxxxx DISTRO=openvix DISTRO_TYPE=release make enigma2-image

With feeds :

MACHINE=xxxxxxx DISTRO=openvix DISTRO_TYPE=release make image

Only feeds :

MACHINE=xxxxxxxx DISTRO=openvix DISTRO_TYPE=release make feeds

and this Work on oe Build specific packages :

MACHINE=xxxxxxxx DISTRO=openvix DISTRO_TYPE=release make init

cd builds/openvix/release/xxxxxxxxxx/

source env.source

bitbake nfs-utils rcpbind ...

;)

[Huevos]

Hello dear vix forum! Question please - when I build this rust-llvm-native 1.59.0-r0 always comes and after 1-2 hours it is only at 1%? does anyone know what this file is for or can i comment it out somehow if not necessary? I'm building a lot of images tuxbox, neutrino, tango ni, pli, and many more but I never had to wait that long! after a few hours this file is only at not even 10%! did not have this file with any construction until now! thanks ! build for wwio bre2ze4k box !No idea. What are you building on.

[Kittybuablueyoshibabygafi]

Ubuntu 20.04 Bodhi Linux 64bit hwe Version ! All my Images No Problem on PC Ubuntu ! All ready - tuxbox, tuxbox Ni,Tango,pli, neutrino, mohousch, and so on ! All OK but openvix build very very very Long wait

[Huevos]

Well our core is the same as OpenATV so that module must be in their build too.

[Kittybuablueyoshibabygafi]

ok will restart it again ! what bothers me so that you have to build with su atv openvix etc I don't have to do that with any build! this rust file has something to do with libsc++ or something! there is very little information about it! ok then try again! but it may also come with the image in the downloads for you! wwio bre2ze4k actually have a lot of people! thanks

[twol]

How do you build without feeds? I may bring my SF4008 out of retirement.
Sorry for jumping on the thread, I'll post in the image building thread if you prefer.

Build an image with feed (build time 5-12h)

MACHINE=zgemmah9combo DISTRO=openvix DISTRO_TYPE=release make image

Build an image without feed (build time 1-2h)

MACHINE=zgemmah9combo DISTRO=openvix DISTRO_TYPE=release make enigma2-image

Build the feeds

MACHINE=zgemmah9combo DISTRO=openvix DISTRO_TYPE=release make feeds

Build specific packages

MACHINE=zgemmah9combo DISTRO=openvix DISTRO_TYPE=release make init

cd builds/openvix/release/zgemmah9combo/

source env.source

bitbake nfs-utils rcpbind ...

[twol]

ok will restart it again ! what bothers me so that you have to build with su atv openvix etc I don't have to do that with any build! this rust file has something to do with libsc++ or something! there is very little information about it! ok then try again! but it may also come with the image in the downloads for you! wwio bre2ze4k actually have a lot of people! thanks

Yes, it can be frustrating when you don't need everything - see my post to Willo3092

[Kittybuablueyoshibabygafi]

Thanks ! yes, that's right ! I also removed a lot of the other images that nobody needs, e.g. tuxbox standard about 85mb and my image is about 50mb! I got rid of a lot of things! find j of the image with 50mb is more than enough the rest you can install if you want! with vix I can also remove some things but not much changes then! I hope it will be finished by Sunday, have good nerves and be patient ;) ! I hope it will also officially come to the images at vix! Kind regards

[abu baniaz]

When you clone the build environment, you are cloning the the build environment for all the OE-A images. All the OE-a images can be made from that directory. I'd ignore the instruction in the making openatv 7.2, vix 6.3 directories and use the branch name that you are forking. e.g "OE-A_5.2".

The adduser part has always given me grief with having to rights etc. Probably have to do something that is not written down and is meant to be common knowledge. Again, openvixbuilder, openatvbuilder or any other name can build any image in the OE-A team.

[Huevos]

When you clone the build environment, you are cloning the the build environment for all the OE-A images. All the OE-a images can be made from that directory. I'd ignore the instruction in the making openatv 7.2, vix 6.3 directories and use the branch name that you are forking. e.g "OE-A_5.2".

The adduser part has always given me grief with having to rights etc. Probably have to do something that is not written down and is meant to be common knowledge. Again, openvixbuilder, openatvbuilder or any other name can build any image in the OE-A team.No idea what that is about. On my personal server I just build under my own user. Done it like that for about 7 years. On ViX server it has separate users for Developer and Release. For me that is a nightmare because it is not possible to share the sources folder between them.

[abu baniaz]

No idea what that is about. On my personal server I just build under my own user. Done it like that for about 7 years. On ViX server it has separate users for Developer and Release. For me that is a nightmare because it is not possible to share the sources folder between them.

We are using different words to imply the same thing. Surely saying "ignore the create the additional user" means build under the username you are logged in.

https://github.com/OpenViX/enigma2/blob/Developer/README.md
Points 5,6,7

Points 8,9,10

Instead of creating openvix/openatv/openbh and then cloning the build environment into it

I am saying to create the name to indicate branch you are forking and then clone the build environment into it. Other people will say something else, as is their want. People reading are free to make up their own mind. I am currently building atv and vix from the same cloned environments instead of one for vix and one for atv and another for bh. This is to test a plugin.

[Kittybuablueyoshibabygafi]

Hey ! Yes clone is very good ! Thanks ! Or without root in the sanity.conf with #

I found more options in the Makefile ! Cool ;) Here :

.DEFAULT_GOAL := all
all: init
@echo
@echo "Openembedded for the oe-alliance environment has been initialized"
@echo "properly. Now you can start building your image, by doing either:"
@echo
@echo "MACHINE=xxxxxx DISTRO=openvix DISTRO_TYPE=release make image"
@echo " or"
@echo "cd $(BUILD_DIR) ; source env.source ; bitbake $(DISTRO)-image"
@echo
@echo "To download all sources for image build:"
@echo "MACHINE=xxxxx DISTRO=openvix DISTRO_TYPE=release make download"
@echo " or"
@echo "cd $(BUILD_DIR) ; source env.source ; bitbake $(DISTRO)-image --runall=fetch"
@echo
@echo "To build image without feed:"
@echo "MACHINE=xxxxxx DISTRO=openvix DISTRO_TYPE=release make enigma2-image"
@echo " or"
@echo "cd $(BUILD_DIR) ; source env.source ; bitbake $(DISTRO)-enigma2-image"
@echo
@echo "To build feeds:"
@echo "MACHINE=xxxxx DISTRO=openvix DISTRO_TYPE=release make feeds"
@echo " or"
@echo "cd $(BUILD_DIR) ; source env.source ; bitbake $(DISTRO)-feeds"
@echo

[Kittybuablueyoshibabygafi]

When you clone the build environment, you are cloning the the build environment for all the OE-A images. All the OE-a images can be made from that directory. I'd ignore the instruction in the making openatv 7.2, vix 6.3 directories and use the branch name that you are forking. e.g "OE-A_5.2".

The adduser part has always given me grief with having to rights etc. Probably have to do something that is not written down and is meant to be common knowledge. Again, openvixbuilder, openatvbuilder or any other name can build any image in the OE-A team.

hey ! can you please say how? Do you mean I download everything normally then I create a folder myself, for example OE then clone the git into the OE folder? but think in the sanity conf with the # is enough! I'll stop depending on the with cmod 777 * and then close again up to the build folder! thanks ! I also think it's funny as root other images like tuxbox neutrino and actually all the others can't be built with root for security reasons! thank you mfg

[Huevos]

The only point was build under your own user rather than create a new one just for the build.

The negative point is the build can now write to any file that belongs to the current user.

Really makes no difference if your build folder is named "build-enviroment" or "OE-A_5.2" unless you are going to be building from multiple build enviroment branches. But everyone knows what is best for them. If you are not sure follow the instructions in OpenViX/enigma2 repo.

[Kittybuablueyoshibabygafi]

OK thanks

Did it normally with git clone cloned 5.2 from git ! then I set the # in the sanity.conf and set it to sudo chmod 755 * directly in the build-env so it will build! if I want to change something, just change it in build-env sudo chmod 777 * and then change it and do it again later! should also fit like this! I will give feedback! load the sources and fetch before I build! Kind regards

[Huevos]

The idea is the user that cloned the build env is the same user that builds the image. That way you should see no permissions errors.

[Kittybuablueyoshibabygafi]

Great thank you ! I'm happy to change my pictures because there are always too many things that nobody needs, at least I don't! my tuxbox tuxbox ni is also only about 45 mb instead of about 90 mb! thank you we will do it! but as su sudo should build oe alliance away because it is not ok and very dangerous they say! thanks ! hope it will be official soon the wwio bre2ze4k image for other users! Kind regards

[Kittybuablueyoshibabygafi]

I found rust llvm

https://git.openembedded.org/openembedded-core/commit/?h=2022-04.5-kirkstone&id=05f4a09899aa8dbb22ef1adb494abac41d5b96b7

https://git.openembedded.org/openembedded-core/commit/?h=2022-04.5-kirkstone&id=a845029df7ea8c1bd987ffac3902d4521742debb

[Kittybuablueyoshibabygafi]

Ok runs without root now! I just created a folder like OE-5.2 then started with point 10 git

https://github.com/OpenViX/enigma2

clean the build-env then a make update and set the hash in the sanity.conf # then I ran a chmod 755 * on OE-5.2 and am building right now so it should fit! if I want to change something, do it now or before in OE-5.2 do a chmod 777 * then do it again with 755 and continue building! Kind regards

[Kittybuablueyoshibabygafi]

hey ! so oe alliance so it doesn't matter if vix atv etc the fetch errors are really not normal and many at qt si make it little fun to build! in between I've already built pli, tuxbox, moh but the oe 5.1 and 5.2 is not funny with urls fetch error! think leave it! Kind regards

[Huevos]

I don't understand what your problem is. I've just built 4 machines from scratch in the last 6 hours.