1177 replies to this topic

[blzr]

I'm right?

I suppose so, please build and check
 

And for don't create 3rd-party feed files?

not sure, but probably removing 3rd-party-feed-configs from openpli-image.bb should do the job...

---
however, after reading 3rd-party feed recipe:

# Use the PLi download server, regardless of where we are. Even for "private" feeds,
# the 3rd party plugins originate here.

you could use openpli's 3rd party feed eventually, in that case for now you'd need to just change one number in 3rdparty-feed confs

Edited by blzr, 24 November 2016 - 15:29.

[WanWizard]

Eh, I don't think that phrase means you can use the feed for non-OpenPLi builds. It means that you can use the feed "from an original image" no matter where the box that runs the image is.

[christophecvr]

Problem with swig solved.

 

Just add:

 

python-importlib \

 

to enigma2.bb

 

Now just wait for nis.inc

 

http://git.openembed...cbf1d7a79b30a06

 

It's now in master-next of meta-openembedded. But if it's in master..dm8000 building fine against bitbake/meta-openembedded/openembedd-core GIT master HEAD of today.

 

Still question and wait for answer...What about bbappends for buildtools-tarball.bb and uninative-tarball.bb ? For dreambox only.

 

Awaiting openpli-dev.

The unitative tarballs ? You're solution was perfect. But the reason why it breaks by dm8000 is simply cause we are using :

MACHINEOVERRIDES .= ":dreambox"

into dreambox.inc .

 

By setting :

TARGET_ARCH_dm8000 = "mipsel"
TARGET_OS_dm8000 = "linux"

TARGET_ARCH_dm800se = "mipsel"
TARGET_OS_dm800se = "linux"

TARGET_ARCH_dm7020hd = "mipsel"
TARGET_OS_dm7020hd = "linux"

Li!ke You said problem is solved and does not break build for any other box .

 

btw I set those bbappends from You into :

openpli50/openpli-oe-core/meta-local/recipes-local/meta

[dax]

I suppose so, please build and check

Well, also for 3rd party feed, is there a directory on my pc where i can see the image-dirctories-structure after a building process?
I mean a dir with the sub
/bin
/boot
..etc..
like of the root of my box?
It will be more faster than a decoder flashing:D

[blzr]

look there:
build/tmp/work/<your_machine>-oe-linux/distro-feed-configs/1.0-r6/distro-feed-configs-1.0/etc/opkg/

[Beeker]

 

 

 

 

The unitative tarballs ? You're solution was perfect. But the reason why it breaks by dm8000 is simply cause we are using :

MACHINEOVERRIDES .= ":dreambox"

into dreambox.inc .

 

 

Ah.That was the reason..And i assume that we can not remove it now?  Did you test that? 

[Beeker]

Tested myself..same result..

 

But still the question...Do openpli-dev's accept these bbappends?

 

If not:  so be it.

 

If yes: Can we send a pull request?

Edited by Beeker, 24 November 2016 - 16:37.

[christophecvr]

Tested myself..same result..

 

But still the question...Do openpli-dev's accept these bbappends?

 

If not:  so be it.

 

If yes: Can we send a pull request?

I even did not started to test it since with the current oe-core if You wan't to test such things the only solution is building from scratch. But that's the only parameter which is extra by dm machine meta . All the othet stb's then dreambox do not have that and do not have the unitative*blablabla problem.

 

 

But still the question...Do openpli-dev's accept these bbappends?

Guess you might  expect answer in year 3001   

[WanWizard]

We don't need bbappends, we maintain the meta-dmm ourselfs, so we can change whatever we want. And as always, we're open to pr's. (@blzr, could you follow this up, this discussion is above my head ).

[Beeker]

Yes indeed..

 

No problem, I have my own git repo

 

But for others....

[Beeker]

 

Tested myself..same result..

 

But still the question...Do openpli-dev's accept these bbappends?

 

If not:  so be it.

 

If yes: Can we send a pull request?

But still the question...Do openpli-dev's accept these bbappends?

Guess you might  expect answer in year 3001 

 

 

 

No problem for me . i have my own git repo.. but for other...

Edited by Beeker, 24 November 2016 - 17:05.

[WanWizard]

Yes indeed..

 

No problem, I have my own git repo

 

But for others....

 

Which others? Aren't we talking about OpenPLi here?

[Beeker]

 

Yes indeed..

 

No problem, I have my own git repo

 

But for others....

 

Which others? Aren't we talking about OpenPLi here?

 

 

Yes we do...

[dax]

Ok, i found the solution:
in order to have

src/gz openpli-mips32el http://192.168.64.191/mips32el

(also for all and vusolo2) edit .../meta-openpli/conf/distro/openpli.conf

#DISTRO_FEED_URI ?= "http://${DISTRO_HOST}/feeds/${FEED_NAME}"
DISTRO_FEED_URI ?= "http://192.168.64.191"

If you don't want 3rd-party-feed remove from .../meta-openpli/conf/distro/openpli-image.bb the row

3rd-party-feed-configs \

to check if everythings is ok look at .../build/tmp/deploy/ipk/vusolo2/distro-feed-configs_1.0-r6_vusolo2.ipk

look there:
build/tmp/work/<your_machine>-oe-linux/distro-feed-configs/1.0-r6/distro-feed-configs-1.0/etc/opkg/

Nothing present, but as above-mentioned...
Thanks a lot

[christophecvr]

 

 

Yes indeed..

 

No problem, I have my own git repo

 

But for others....

 

Which others? Aren't we talking about OpenPLi here?

 

 

Yes we do...

 

If we where not it would be useless to discuss anything here since yes I build self  and can solve if for me personally but then the rest off the users .... 

And if You work on development from for example the servicemp3.c it's extremely important the be in line everywhere.

[WanWizard]

Yes we do...

 

So what is the problem for "others" if these fixes are just incorporated into the meta-dmm in master-next?

[Beeker]

We don't need bbappends, we maintain the meta-dmm ourselfs, so we can change whatever we want. And as always, we're open to pr's. (@blzr, could you follow this up, this discussion is above my head ).

 

We still talking about OpenPli.

 

Just a question before we send a pull request. There are perhaps better solutions...

 

This is something we can not achieve without bbappends. It has something to do with the OE-core.

 

But let's wait on @blzr

[Erik Slagter]

Gentlemen,

If you have a neat patch for either DMM BSP or OE (without side-effects) to solve this issue, please supply it. Only with the actual patch I can consider whether it is suitable for inclusion.

 

And yes, blzr, please comment.

Edited by Erik Slagter, 24 November 2016 - 17:40.

[christophecvr]

Ok, i found the solution:
in order to have

src/gz openpli-mips32el http://192.168.64.191/mips32el

(also for all and vusolo2) edit .../meta-openpli/conf/distro/openpli.conf

#DISTRO_FEED_URI ?= "http://${DISTRO_HOST}/feeds/${FEED_NAME}"
DISTRO_FEED_URI ?= "http://192.168.64.191"

If you don't want 3rd-party-feed remove from .../meta-openpli/conf/distro/openpli-image.bb the row

3rd-party-feed-configs \

to check if everythings is ok look at .../build/tmp/deploy/ipk/vusolo2/distro-feed-configs_1.0-r6_vusolo2.ipk

look there:
build/tmp/work/<your_machine>-oe-linux/distro-feed-configs/1.0-r6/distro-feed-configs-1.0/etc/opkg/

Nothing present, but as above-mentioned...
Thanks a lot

 

Just adapt You're site.conf before You very first build with You're personal update link . like for me the site conf is changed before my first build into :

 

location of site.conf  ~/openpli50/openpli-oe-core

 

content

SCONF_VERSION = "1"
BB_NUMBER_THREADS = "10"
PARALLEL_MAKE = "-j 10"
BUILD_OPTIMIZATION = "-march=native -O2 -pipe"
DL_DIR ="/home/christophe/openpli50/sources"
#INHERIT += "rm_work"
DISTRO_FEED_URI = "http://<my-httpserverip>/pli50/feeds/${FEED_NAME}/${MACHINE}"

the my-htttpserverip  is the ip of pc on which my http server is installed.

 

again read document about linking feeds and so inti document like I told before

 

and if You are using gnix or something like that just replace the http//blablabla by /home/<yours>  and the rest eventualy make links in You're home dir first

[christophecvr]

Gentlemen,

If you have a neat patch for either DMM BSP or OE (without side-effects) to solve this issue, please supply it. Only with the actual patch I can consider whether it is suitable for inclusion.

 

And yes, blzr, please comment.

Here the patch for dm800se dm8000 and dm7020hd.

 

Beeker asked me to make a patch.

Attached Files

•  dm-master-next-arch-detection.patch   2.09KB   9 downloads