Log in

Dec. 6th, 2012

hong kong

webrtc built

I fixed a couple of other problems with webrtc and it now builds.   Tom invited me to post patches to him so that these fixes can get into the main release.   I look forward to doing that, it's been a while since I donated patches anywhere.  Unfortunately, my 8Gb SD card has filled up and, despite deleting various things, I need to create another one.   Luckily Jon Masters has posted a clean 'how to' install Fedora (complete with lurid warnings) @ https://fedoraproject.org/wiki/Architectures/ARM/Samsung_Chromebook_2012.   
Tags: ,

Dec. 5th, 2012

hong kong

Playing with Fedora: Chrome web browser

I've been doing a little bit of playing trying to get the Chrome web browser built on F17.   The x86 source rpms can be found at http://fedoraproject.org/wiki/Chromium.   The list of packages is:









I downloaded these and started to try and build them.  

  • jsoncpp builds as is.
  • v8 is missing a load of devel RPMs, and built after they were added.    
  • Webrtc caused all sorts of problems, all associated with the use of SSE2.  I exchanged some email with Tom Callaway and his proposal was to fix the problems in the source RPMs rather than try to substitute them.   

Webrtc is causing all sorts of problems, mostly around the use of SSE2.   I tracked down something called webrtc-audio-processing (see http://freedesktop.org/software/pulseaudio/webrtc-audio-processing/) and this builds just fine on ARM.  Investigating, it uses WEBRTC_USE_SSE2, defined in typedefs.h, to use / comment out the SSE2 code on non-X86 platforms.   Looking at the webrtc source RPM, it used a similar define (WEBRTC_ARCH_X86_FAMILY) to do the same thing.    modules/audio-processing/aec was breaking, I fixed this in aec_core.c, aec_core_sse2.c and aec_rdft_sse2.c.

Dec. 4th, 2012

hong kong

Restarting this blog

Samsung Chromebook 
Here's the reason why, I now have a decent ARM based system on which to play.  I've installed Fedora and I'm playing. 
Tags: ,