You are viewing davidrusling

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:

chromium-21.0.1180.89-1.fc17.src.rpm          

chromium-ffmpegsumo-21.0.1180.81-1.fc17.src.rpm

jsoncpp-0.6.0-0.1.20120626svn249.fc17.src.rpm  

nacl-binutils-2.20.1-4.gitf412ed5.fc17.src.rpm 

nacl-gcc-4.4.3-5.git3937565.fc17.src.rpm 

nacl-newlib-1.20.0-2.git67e3510.fc17.src.rpm  

v8-3.11.10.20-1.fc17.src.rpm     

webrtc-0.1-0.6.20120613svn2401.fc17.src.rpm 

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.

hong kong

October 2014

S M T W T F S
   1234
567891011
12131415161718
19202122232425
262728293031 

Syndicate

RSS Atom
Powered by LiveJournal.com