chromium: Upgrade to version 35.0.1916.114

This fixes several CSS transition problems, and improves performance on
some pages

Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
chromium: Add PACKAGECONFIG for disabling API keys info bar

Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
chromium: Add recipe for version 37.0.2062.0

This version includes Wayland support by adding ozone-wayland

Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
firefox: workaround for freetype-config breakage

All binconfig scripts in OE-core have been disabled, leading to -I/usr/include/freetype2 disappearing from C(PP)FLAGS. Add it in manually as a workaround, mozilla autotools are a maze and not easily fixed.

Signed-off-by: Koen Kooi <koen.kooi@linaro.org>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
firefox-{l10n,addon}: Drop runtime dependency on TUNE_PKGARCH firefox and keep allarch

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
firefox: properly fix build without freetype-config

* fails with:
  ../../gfx/thebes/gfxFT2Utils.o: In function `gfxFT2LockedFace::GetMetrics(gfxFont::Metrics*, unsigned int*)':
  /OE/build/oe-core/tmp-eglibc/work/i586-oe-linux/firefox/10.0.11esr-r0/mozilla-esr10/gfx/thebes/gfxFT2Utils.cpp:139: undefined reference to `FT_Get_Sfnt_Table'
  /OE/build/oe-core/tmp-eglibc/work/i586-oe-linux/firefox/10.0.11esr-r0/mozilla-esr10/gfx/thebes/gfxFT2Utils.cpp:234: undefined reference to `FT_Get_Sfnt_Table'
  ../../gfx/thebes/gfxFT2Utils.o: In function `gfxFT2LockedFace::GetFontTable(unsigned int, FallibleTArray<unsigned char>&)':
  /OE/build/oe-core/tmp-eglibc/work/i586-oe-linux/firefox/10.0.11esr-r0/mozilla-esr10/gfx/thebes/gfxFT2Utils.cpp:364: undefined reference to `FT_Load_Sfnt_Table'
  /OE/build/oe-core/tmp-eglibc/work/i586-oe-linux/firefox/10.0.11esr-r0/mozilla-esr10/gfx/thebes/gfxFT2Utils.cpp:372: undefined reference to `FT_Load_Sfnt_Table'
  collect2: error: ld returned 1 exit status
  ../../config/rules.mk:1089: recipe for target 'libxul.so' failed

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
firefox: fix build on qemux86-64

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
chromium-35*: use BFD when building for x86-64

* this doesn't fix it completely, but allows it a bit further and then
  it fails in the same spot as when building for qemux86 (or 37* version
  with gold)

  sysroots/x86_64-linux/usr/bin/x86_64-oe-linux/x86_64-oe-linux-ld.gold:
    warning: hidden symbol 'sqlite3_temp_directory' in obj/third_party/sqlite/libsqlite3.a(obj/third_party/sqlite/amalgamation/sqlite.sqlite3.o)
    is referenced by DSO
    sysroots/qemux86-64/usr/lib/../lib/libsoftokn3.so
  sysroots/x86_64-linux/usr/bin/x86_64-oe-linux/x86_64-oe-linux-ld.gold:
    error: treating warnings as errors
  collect2: error: ld returned 1 exit status

  and few more symbols like this, libsoftokn3.so is provided by system
  nss, using system sqlite3 has some issues too:
  https://code.google.com/p/chromium/issues/detail?id=22208

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
chromium: Disable fatal linker warnings related to SQLite

With the gold linker, problems with hidden sqlite3 symbols occur. Example:

  warning: hidden symbol 'sqlite3_temp_directory' in obj/third_party/sqlite/libsqlite3.a
  (obj/third_party/sqlite/amalgamation/sqlite.sqlite3.o) is referenced by DSO
  /mnt/ramdisk/yocto/qemu-test-build/tmp//sysroots/qemux86/usr/lib/../lib/libsoftokn3.so

The problem is known, and a solution would be to set the build scripts
to not build sqlite3 and use the system's sqlite3 library instead.
However, currently, this is not possible:

  https://code.google.com/p/chromium/issues/detail?id=22208

The Crosswalk project fixed this by setting the warnings to non-fatal:

  https://github.com/crosswalk-project/crosswalk/commit/83d22586852a3d64300fd024e24ade9a4ac325be

The disable_fatal_linker_warnings GYP flag used in that commit is already
part of Chromium 37. It just needs to be enabled. This commit does
precisely that.

Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
chromium: Upgrade to version 37.0.2062.94

This is the current stable release of the 37 series. Since it is no longer
a beta, the DEFAULT_PREFERENCE = "-1" bit is removed. Furthermore, this
version adds the angle_use_commit_id flag, which makes the related patch
obsolete.

Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
chromium: Remove Chromium 35 recipe and obsolete patches

These patches are no longer used or needed anywhere. Chromium 35 is now
obsolete, since Chromium 37.0.2062.94 is the new stable version.

Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
nspr: Remove bbappend as it is not necessary

The OE-Core version supports what we need, so we can get rid of the
append file and avoid the hassle of the maintenance of it.

Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
chromium: Add missing impl side painting patch

Disable rasterization whitelist, unlocking impl side painting. It is
still in an experimental stage, but promises better performance so it
needs to be enabled by PACKAGECONFIG.

Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
chromium: conditionally compile routines for use with GLIB

The routine QuoteArgForDesktopFileExec is only called when GLIB is
used, and compilation will fail with the following error message
if it is compiled without GLIB support (e.g. under Wayland):
	"defined but not used [-Werror=unused-function]"

Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
chromium: Upgrade to version 38.0.2125.101

* Starting with this version, several cross compilation specific parts in
the GYP files need to be disabled with both additional flags and an extra
patch. Chromium 38 now includes clang specifics, which are enabled by
default. Additional flags (-Dhost_clang=0 -Dclang=0) disable these.
Furthermore, the GYP files now include default values for CC and CXX
(https://codereview.chromium.org/414343003/patch/40001/50001), which
could not be overridden with environment variables. A patch removes this.

* ozone-wayland's Milestone-Harvest branch is the one to use for
Chromium 38. It includes a patch that collides with another one that is
already present in the chromium/ directly. Consequently, this other patch
is now only used for X11 builds.

* Only 00*.patch patch files from ozone-wayland are used, since
the 10*.patch files cannot be applied cleanly and easily (and are not
actually required for builds with this recipe, since another patch already
takes care of the X11 linker flags removal).

Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>