<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">To answer my own question:<div><br></div><div>What ended up doing it was the following modifications: <a href="http://cl.ly/code/1q0V071Y1G2L">http://cl.ly/code/1q0V071Y1G2L</a></div><div><br></div><div>Some inspection of the g-ir-scanner source revealed that it respects the CFLAGS environment variable. So, adding that, with the value obtained by concatenating EGLGLES_CFLAGS with EGLGLES_LIBS to the invocation from the Makefile made that command succeed without the linker errors, and the build completed.</div><div><br></div><div>Alas, no luck getting 1080p playback working any better - it’s still the same old jerky/laggy mess as before. But that’s a whole different matter.</div><div><div apple-content-edited="true"><br class="Apple-interchange-newline"><br class="Apple-interchange-newline"> </div> <br><div><div>On 25 Feb 2014, at 12:05 pm, Michael Tyson <<a href="mailto:michael@tyson.id.au">michael@tyson.id.au</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi guys,<div><br></div><div>I hate to ask about something as pedestrian as building from source, but I’ve run out of ideas trying to build gst-plugins-bad1.0 from deb src (from the experimental/sid branches).</div><div><br></div><div>I’m building from source as I want to see if more recent builds than those available from <a href="http://vontaene.de/">vontaene.de</a> provide better support for HD video playback, which I’ve heard might be the case. I also want to build python support.</div><div><br></div><div>In order to enable the RPI EGL window system (rather than the default X11 option which, I might add, builds just fine but doesn’t work on the RasPi without X11 running), I’ve had to make a couple of modifications to the debian control files: </div><div><br></div><div><a href="http://f.cl.ly/items/1M141d0W3L1N1h071R36/diff%20ur%20debianorigrules%20debian.txt">http://f.cl.ly/items/1M141d0W3L1N1h071R36/diff%20ur%20debianorigrules%20debian.txt</a></div><div><br></div><div>This adds the --with-egl-window-system=rpi configure param, and adds some include/lib paths to build against the libraspberrypi stuff in /opt/vc/include (otherwise the configure checks for bcm_host fail).</div><div><br></div><div>Now, I have two building environments: One emulated, running under qemu, and one physical RasPi, both with the same set of packages installed.</div><div><br></div><div>On the emulated setup, the process builds all the way through until the last packaging stages, where I see an error, during a call to gst-codec-info-1.0:</div><div><br></div><div>* failed to open vchiq instance</div><div><br></div><div>This would appear to be because the system is emulated without /dev/vchiq support. So, with the same setup, I attempted a build on the RasPi.</div><div><br></div><div>This proceeds successfully through the configure stage, but throws a large number of syntax errors, then a bunch of undefined references from /opt/vc/lib/libEGL.so while building gstegl - specifically, while running g-ir-scanner to generate GstEGL-1.0.gir.</div><div><br></div><div>Output here: <a href="http://f.cl.ly/items/2P3q1E1a2D3r2E14093d/Making%20all%20in%20eglmake5%20Enterin.txt">http://f.cl.ly/items/2P3q1E1a2D3r2E14093d/Making%20all%20in%20eglmake5%20Enterin.txt</a></div><div><br></div><div>This is as far as I’ve gotten. As I understand it from this thread: <a href="http://www.raspberrypi.org/phpBB3/viewtopic.php?t=7090">http://www.raspberrypi.org/phpBB3/viewtopic.php?t=7090</a>, those undefined symbol issues can be resolved by linking against a few extra libraries - this is what the extra EGLGLES_LIBS environment variable I added is meant to achieve. However, it looks like the g-ir-scanner utility isn’t using those extra libs when it invokes gcc. That also doesn’t explain the syntax errors. Why those errors occur on the physical RasPi and not the emulated setup is beyond me - they’re all the same files, as far as I can see.</div><div><br></div><div>Can anyone shed light on what the next steps might be?</div><div><br></div><div>Many thanks,</div><div>Michael</div></div></blockquote></div><br></div></body></html>