Update Build and Running documentation.

Update Build and Running documentation.

- Added links to Android build with information on how to pull Android parts of
  Chromium repo.
- Reordered running instruction to follow the order in which one would use.
- Added infomration on the underlying adb command to use instead of build
  scripts.
- Added information on running the Blimp client in an Emulator.

BUG=

Committed: https://crrev.com/0b6a45f4dd3b47a1f3214d53cd5934aa62b891f5
Cr-Commit-Position: refs/heads/master@{#403255}

[Sriram, 2016-06-28 18:35:49]

sriramsr@chromium.org changed reviewers:
+ kmarshall@chromium.org, nyquist@chromium.org

[Sriram, 2016-06-28 18:35:49]

kmarshall@chromium.org: Please review changes in 

nyquist@chromium.org: Please review changes in

[Kevin M, 2016-06-28 22:31:53]

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/build.md
File blimp/docs/build.md (right):

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/build.md#newcode4
blimp/docs/build.md:4: If you want to build the Android client then you would
need to follow
will need

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/build.md#newcode5
blimp/docs/build.md:5: instruciton
[here](https://www.chromium.org/developers/how-tos/android-build-instructions)
typo: "instructions"

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md
File blimp/docs/running.md (right):

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:121: 1. Build apk matching the emulator cpu type. Emulator
cpu type is most likely
an APK

The emulator

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:122: x86 while the default Android build cpu type is ARM.
Follow Android build
x86, while

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:122: x86 while the default Android build cpu type is ARM.
Follow Android build
Follow the

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:126: fonts are rendered correctly and also you have latest
Play services binaries.
Too long of a sentence- ". Also ensure that you have the latest Play Services
installed."

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:128: 3. Some of scripts under `build/android` will fail to
run as it uses `adb scp`.
This detail seems like it should be more of an addendum than a discrete numbered
step.

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:131: 4. To connect to an Engine running on the host
machine, you would have to use
would have to => should

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:133: the emulator itself. There is no need of setting up
no need to set up

[Sriram, 2016-06-28 23:22:38]

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/build.md
File blimp/docs/build.md (right):

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/build.md#newcode4
blimp/docs/build.md:4: If you want to build the Android client then you would
need to follow
On 2016/06/28 22:31:52, Kevin M wrote:
> will need

Done.

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/build.md#newcode5
blimp/docs/build.md:5: instruciton
[here](https://www.chromium.org/developers/how-tos/android-build-instructions)
On 2016/06/28 22:31:52, Kevin M wrote:
> typo: "instructions"

Done.

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md
File blimp/docs/running.md (right):

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:121: 1. Build apk matching the emulator cpu type. Emulator
cpu type is most likely
On 2016/06/28 22:31:53, Kevin M wrote:
> an APK
> 
> The emulator

Done.

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:122: x86 while the default Android build cpu type is ARM.
Follow Android build
On 2016/06/28 22:31:53, Kevin M wrote:
> x86, while

Done.

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:122: x86 while the default Android build cpu type is ARM.
Follow Android build
On 2016/06/28 22:31:53, Kevin M wrote:
> x86, while

Done.

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:126: fonts are rendered correctly and also you have latest
Play services binaries.
On 2016/06/28 22:31:53, Kevin M wrote:
> Too long of a sentence- ". Also ensure that you have the latest Play Services
> installed."

Done.

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:128: 3. Some of scripts under `build/android` will fail to
run as it uses `adb scp`.
On 2016/06/28 22:31:53, Kevin M wrote:
> This detail seems like it should be more of an addendum than a discrete
numbered
> step.

This is a gotcha list and not steps and I am inclined to leave it here.

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:131: 4. To connect to an Engine running on the host
machine, you would have to use
On 2016/06/28 22:31:53, Kevin M wrote:
> would have to => should

Done.

https://codereview.chromium.org/2104003003/diff/1/blimp/docs/running.md#newco...
blimp/docs/running.md:133: the emulator itself. There is no need of setting up
On 2016/06/28 22:31:53, Kevin M wrote:
> no need to set up

Done.

[Kevin M, 2016-06-29 20:23:58]

lgtm % nits

https://codereview.chromium.org/2104003003/diff/20001/blimp/docs/running.md
File blimp/docs/running.md (right):

https://codereview.chromium.org/2104003003/diff/20001/blimp/docs/running.md#n...
blimp/docs/running.md:60: The engine sends partially rendered content to the
client. To request the
Line is longer than >80 chars.

(Do we care about this for MD?)

https://codereview.chromium.org/2104003003/diff/20001/blimp/docs/running.md#n...
blimp/docs/running.md:86: The script under the cover uses adb to start the
application:
Do we need to duplicate the shell script contents? Maybe suggest that the reader
to inspect the contents of adb_run_blimp_client for more details?

https://codereview.chromium.org/2104003003/diff/20001/blimp/docs/running.md#n...
blimp/docs/running.md:121: 1. Build an APK matching the emulator cpu type. The
emulator cpu type is most
Can you use bullet points instead of numbers then, if these aren't steps?

[Sriram, 2016-06-30 19:00:13]

https://codereview.chromium.org/2104003003/diff/20001/blimp/docs/running.md
File blimp/docs/running.md (right):

https://codereview.chromium.org/2104003003/diff/20001/blimp/docs/running.md#n...
blimp/docs/running.md:60: The engine sends partially rendered content to the
client. To request the
On 2016/06/29 20:23:58, Kevin M wrote:
> Line is longer than >80 chars.
> 
> (Do we care about this for MD?)

Fixed just to be consistent.

https://codereview.chromium.org/2104003003/diff/20001/blimp/docs/running.md#n...
blimp/docs/running.md:86: The script under the cover uses adb to start the
application:
On 2016/06/29 20:23:58, Kevin M wrote:
> Do we need to duplicate the shell script contents? Maybe suggest that the
reader
> to inspect the contents of adb_run_blimp_client for more details?

adb_run_blimp_client has additional arguments that are not needed when launching
the app so skipped it here. I am going to leave it here as it is easier to copy
paste as well when using an emulator.

https://codereview.chromium.org/2104003003/diff/20001/blimp/docs/running.md#n...
blimp/docs/running.md:121: 1. Build an APK matching the emulator cpu type. The
emulator cpu type is most
On 2016/06/29 20:23:58, Kevin M wrote:
> Can you use bullet points instead of numbers then, if these aren't steps?

Done.

[Sriram, 2016-06-30 19:00:20]

The CQ bit was checked by sriramsr@chromium.org

[Sriram, 2016-06-30 19:00:20]

The patchset sent to the CQ was uploaded after l-g-t-m from
kmarshall@chromium.org
Link to the patchset: https://codereview.chromium.org/2104003003/#ps40001
(title: "Addressing Kevin's CR comments")

[commit-bot: I haz the power, 2016-06-30 19:01:43]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-06-30 19:42:41]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-06-30 19:42:52]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-06-30 19:46:02]

Description was changed from

==========
Update Build and Running documentation.

- Added links to Android build with information on how to pull Android parts of
  Chromium repo.
- Reordered running instruction to follow the order in which one would use.
- Added infomration on the underlying adb command to use instead of build
  scripts.
- Added information on running the Blimp client in an Emulator.

BUG=
==========

to

==========
Update Build and Running documentation.

- Added links to Android build with information on how to pull Android parts of
  Chromium repo.
- Reordered running instruction to follow the order in which one would use.
- Added infomration on the underlying adb command to use instead of build
  scripts.
- Added information on running the Blimp client in an Emulator.

BUG=

Committed: https://crrev.com/0b6a45f4dd3b47a1f3214d53cd5934aa62b891f5
Cr-Commit-Position: refs/heads/master@{#403255}
==========

[commit-bot: I haz the power, 2016-06-30 19:46:03]

Patchset 3 (id:??) landed as
https://crrev.com/0b6a45f4dd3b47a1f3214d53cd5934aa62b891f5
Cr-Commit-Position: refs/heads/master@{#403255}