Merge pull request #1186 from cmarcelo/fix-mac-build

Fixes for Mac build
[Extensions] Fix regression, extensions not being registered on Tizen and Android

RegisterInternalExtensionsInServer should have been renamed for Tizen and
Android and not only for desktop. The extensions were not being registered
because of that for these platforms.

Thanks to Jesus Sanchez-Palencia for pointing the directions.
Merge pull request #1189 from tmpsantos/server_fix

[Extensions] Fix regression, extensions not being registered on Tizen and Android
Roll chromium-crosswalk to 58e2e1f.

ffe0dfe [Temp] Backport Chromium r236822.
58e2e1f Merge pull request #89 from rakuco/cr-backport-r326822

BUG=https://crosswalk-project.org/jira/browse/XWALK-454
[Packaging] Change the way we pass BUILDDIR_NAME to gyp and make.

The M32 Chromium rebase ended up causing a regression in the incremental
Tizen builds: even with no changes, an incremental build would always
trigger a regeneration of most of the V8 bindings in Blink, which then
caused an almost full rebuild of Blink itself.

This was caused by changes in Blink's Source/bindings/derived_sources.gyp,
which were generating some file lists that were dependencies for some
targets in the source tree itself. Since the source tree is erased in every
build, the file lists are regenerated and trigger all those rebuilds.

Fix this by pulling some commits that had to be made in Chromium and gyp
itself to properly support passing an absolute directory to gyp's
--generator-output option and then using that to know where to store the
file lists generated by gyp:

  Chromium r236822: Pass the gold binary to the linker using only absolute
                    paths.
  gyp r1797:        make: Support the generator_filelist_paths input info.

Now, instead of passing "builddir_name" when calling make, we pass --depth
and --generator-output to gyp.

While we could backport this commit to the crosswalk-2 branch, there isn't
really a need for that, as the previous process was working fine with M31.

BUG=https://crosswalk-project.org/jira/browse/XWALK-454
Merge pull request #1190 from rakuco/incremental-tizen-builds-blink

[Packaging] Change the way we pass BUILDDIR_NAME to gyp and make.
[Tizen] Permit the inclusion of Tizen Web UI Framework

This patch creates a Tizen-specific XWalkContentRendererClient that
implements the WillSendRequest hook.  This hook, as the name implies, is
called before every request is made from a particular WebKit::WebFrame.  By
tapping into this hook, it is possible to rewrite requests so that they have
the full file path.

Some measures are taken so that relative paths outside where the Tizen Web
UI Framework can't be referenced; also, only known extensions are permitted.
Merge pull request #1188 from cmarcelo/move-indicator

[Tizen][UI] Move TizenSystemIndicator to tizen/mobile/ui/
Merge pull request #1172 from lpereira/request-url-rewriter

Permit the inclusion of Tizen Web UI Framework
[Application] Add a way to observe ApplicationService activity

Add an Observer interface for ApplicationService, so that other code can
be notified when applications were added or removed.

This will be useful when exposing D-Bus interface on Linux because we
keep an D-Bus object for each application installed.
[Application][Linux] Expose installed apps via D-Bus

This commit exposes the '/installed' object path, that allow D-Bus
clients to List, Install and Uninstall applications. The D-Bus
interfaces are described in the implementation files.

InstalledApplicationsRoot is the entry point, and hold a corresponding
D-Bus object. It also hold a vector of child objects, which themselves
have their own D-Bus objects.

The org.freedesktop.DBus.ObjectManager interface implementation is
partial but enough for our current functionality.