Hi,
Another package that was requested to be able to cross-compiled was chromium. Now this is possible also, following the instructions at:
https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/ChromiumCrossCompi...
The starting point was chromium not building on arm at all, fortunately it was quite easy to fix. While easy, it was time consuming as I had to build chrome a few times natively. With builds taking around 20h on panda. Meanwhile, on dual-core (hypertheaded, so kinda 4-core) Intel i5 M 520, cross-compile took around 1.5h. When the native builds were failing at the final linking stage, the value of cross-compiling was surely becoming clear ;)
Cheers, Riku
Hi,
On Wed, Dec 7, 2011 at 1:04 PM, Riku Voipio riku.voipio@linaro.org wrote:
Hi,
Another package that was requested to be able to cross-compiled was chromium. Now this is possible also, following the instructions at:
https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/ChromiumCrossCompi...
The starting point was chromium not building on arm at all, fortunately it was quite easy to fix. While easy, it was time consuming as I had to build chrome a few times natively. With builds taking around 20h on panda. Meanwhile, on dual-core (hypertheaded, so kinda 4-core) Intel i5 M 520, cross-compile took around 1.5h. When the native builds were failing at the final linking stage, the value of cross-compiling was surely becoming clear ;)
That's nice, thanks for making it to work :-)
I just had one issue while installing all the dependencies, that is with the package libglib2.0-0:armel:
Setting up libglib2.0-0:armel (2.30.0-0ubuntu4linaro6) ... /var/lib/dpkg/info/libglib2.0-0:armel.postinst: 37: /usr/lib/arm-linux-gnueabi/glib-2.0/glib-compile-schemas: not found /var/lib/dpkg/info/libglib2.0-0:armel.postinst: 40: /usr/lib/arm-linux-gnueabi/glib-2.0/gio-querymodules: not found /var/lib/dpkg/info/libglib2.0-0:armel.postinst: 40: true: not found dpkg: error processing libglib2.0-0:armel (--configure): subprocess installed post-installation script returned error exit status 127
For some reason it seems that the || true statement didn't work as expected at the postinst script.
Cheers,