249 replies to this topic

[littlesat]

????

The gstreamer branch is far behind...

[christophecvr]

And with my changes , it does build but still with gst 0.1 and not 1.xxx

[christophecvr]

Well it even does not build (which is logic due to enigma2.bb and gst-subsink and dvbmedia-sink). Somehow something extra is still missing

Edited by christophecvr, 25 January 2014 - 15:27.

[athoik]

Hi guys,

 

I think the best option is to put gstreamer 1.0.7 (because that version works for sure) into master branch and also apply patches for dvbmediank (OpenPLi one).

 

PS. I tried to compile 1.2.2 (exists in OE) but it doesn't compile.

[Erik Slagter]

????

The gstreamer branch is far behind...

Yes, we already established that some time ago...

 

But "merging" a "master" branch into a "derived" branch???

[athoik]

Hi,

 

Here is gstreamer 1.0.7 for master branch! (just extract files on meta-local)

 

41.tar.gz contains patched dvbmediasink, dvbmediasink from meta-local uses that.

 

I compiled sucessfully gstreamer, gstreamer-libav, gst-plugins-base/good/bad/ugly and gst-plugin-dvbmediasink!

 

PS. In order to use local dvbmediasink rename the existing one into txt and change vu/dreambox to use OpenPLi dvbmediasink...

Attached Files

•  41.tar.gz   140.78KB   19 downloads
•  gstreamer_1.0.7.tar.gz   7.87KB   21 downloads

[christophecvr]

ok that work around of athoik work's. It might be ussefull for very limited persons and only very limited applications. Reading more about the gstreamer, if migrating to 1.0 the latest version should be used. Whitout that there always will be very few applications avbl and especially the codecs will be a problem.

 

Gstreamer 1.2.2 itself does build very well. But the problem are the plugins-base from openembedded are not building . Then it's pretty usseless.

[theparasol]

True, and for xp1000 it doesnt work "out-of-the-box" but I can use his  change suggestions to adopt to latest gstreamer.

Indeed big impact on plugins. I wasnt realizing it till now. Before I thought they just call some function in enigma and start to play a certain object.

So more rework is needed. Perhaps the reason a more recent gstreamer hasnt show up already

[christophecvr]

I have here the faillog of build gstreamer1.0-plugins-base_1.2.2.bb  (gstreamer1.0_1.2.2 is build ok)

 

Seems somewhere a small typo or so or wrong link, but which ?? that's the problem

 

 

Attached Files

•  gstreamer10pluginsbasefaillog.zip   25.08KB   5 downloads

[theparasol]

--sysroot=/home/christophe/openpli40gst/openpli-oe-core/build/tmp/sysroots/vuduo2  -c  -Os -pipe -g -feliminate-unused-debug-types  conftest.c >&5
conftest.c:87:29: error: expected ';', ',' or ')' before 'text'
 test_restrict (ccp restrict text)
                             ^
conftest.c: In function 'main':
conftest.c:141:18: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'newvar'
   char *restrict newvar = "Another string";
                  ^
conftest.c:141:18: error: 'newvar' undeclared (first use in this function)
conftest.c:141:18: note: each undeclared identifier is reported only once for each function it appears in
conftest.c:151:3: error: 'for' loop initial declarations are only allowed in C99 mode
   for (int i = 0; i < ia->datasize; ++i)
   ^
conftest.c:151:3: note: use option -std=c99 or -std=gnu99 to compile your code
configure:17635: $? = 1
configure: failed program was:
| /* confdefs.h */

[WanWizard]

restrict is fairly new, and requires c99 ?

[betacentauri]

If you have access to the source code you can rewrite it to:
int i;
for (i = 0; i < ia->datasize; ++i)

[Erik Slagter]

Not good coding practise to use c99 in such a generic piece of code, imho. OTOH maybe cán change the compilerflags to allow c99, but it thought that was the job of configure?

[betacentauri]

Otherwise try to add
-std=c99
as extra compile option in bitbake file (how exactly I don't know...)

[Erik Slagter]

 

????

The gstreamer branch is far behind...

Yes, we already established that some time ago...

 

But "merging" a "master" branch into a "derived" branch???

Ah you mean REBASE.

[christophecvr]

Not good coding practise to use c99 in such a generic piece of code, imho. OTOH maybe cán change the compilerflags to allow c99, but it thought that was the job of configure?

Yes that is a job off configure. By the gstreamer1.0_1.2.2.2 self in work can be seen that configure add's the -std=gnuc99. (and it does configure and compile)

But with the gstreamer1.0-plugins-base_1.2.2.2 in work can be seen that the configure file does not have this extra add .

 

How to solve that I don't know

[betacentauri]

Try to add or adapt
EXTRA_OECONF += "-std=gnuc99"
to bb file.
Like here:
http://sourceforge.n...se_0.10.36.1.bb

[christophecvr]

Try to add or adapt
EXTRA_OECONF += "-std=gnuc99"
to bb file.
Like here:
http://sourceforge.n...se_0.10.36.1.bb

Thank's I already tested by temporarely changing the config and added the std=gnu99  (c99 was typo) But then other error's show up.

 

However I go no try out by first remove the package with cleanall and then adapt the .bb file and retry.

[christophecvr]

I tried That way but it's not correct.

 

I think well it's possible trough EXTRA_OECONF + = "  xxx"

 

But I t's a cflag which must be added there is a way just can't find it anymore

[athoik]

Maybe like this:

 

CFLAGS += "-std=gnu99"