To update this thread, Steve has removed the Android.mk files from the tree
but left PLATFORM(ANDROID) in the tree. This sounds like a reasonable
compromise to me because the maintenance burden of Android.mk appears to be
about 4x that of PLATFORM(ANDROID) and removing PLATFORM(ANDROID) would make
On 04/27/2011 11:53 AM, Steve Block wrote:
>> Is there any plan to fully merge the code, have updated LayoutTests and
>> build-webkit integration?
> The Android browser still uses the Android port, but as you point out,
> it's not fully upstreamed. We're continuing to work on this.
>> Since then,
> Is there any plan to fully merge the code, have updated LayoutTests and
> build-webkit integration?
The Android browser still uses the Android port, but as you point out,
it's not fully upstreamed. We're continuing to work on this.
> Since then, WebCore/Android.mk has been modified 81 times, but
On Thu, Apr 21, 2011 at 9:14 AM, Ariya Hidayat wrote:
>> I started to look into the state of the Android port/platform and the state
>> in
>> WebKit. It appears to me that the Android team at Google has decided to use
>> the chromium tree as upstream (it might have changed with Android 3.0),...
>
> I started to look into the state of the Android port/platform and the state in
> WebKit. It appears to me that the Android team at Google has decided to use
> the chromium tree as upstream (it might have changed with Android 3.0),...
On a side note, Android 3.0 (Honeycomb) is actually the beginn
Hi all,
I started to look into the state of the Android port/platform and the state in
WebKit. It appears to me that the Android team at Google has decided to use
the chromium tree as upstream (it might have changed with Android 3.0), it
appears to me that there are still things not merged to the
6 matches
Mail list logo
