Fixed directions for release build.

Fixed directions for release build.

R=jamesr@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/0ac4ba45ca77ce9f13769a0a34489f5020edb217

[jimbe, 2015-02-13 21:14:53]

jimbe@chromium.org changed reviewers:
+ jamesr@chromium.org

[jamesr, 2015-02-13 21:15:44]

lgtm, although maybe these should all prefer debug

[jimbe, 2015-02-13 21:31:11]

New patchsets have been uploaded after l-g-t-m from jamesr@chromium.org

[jimbe, 2015-02-13 21:32:45]

On 2015/02/13 at 21:31:11, jimbe wrote:
> New patchsets have been uploaded after l-g-t-m from jamesr@chromium.org

I referred the reader to the instructions earlier in the document. Also fixed
some internal inconsistencies.

[jamesr, 2015-02-13 22:27:22]

https://codereview.chromium.org/926723002/diff/20001/README.md
File README.md (right):

https://codereview.chromium.org/926723002/diff/20001/README.md#newcode38
README.md:38: $ ninja -C out/Debug -j 10
can you update this too?

[jimbe, 2015-02-14 00:44:50]

https://codereview.chromium.org/926723002/diff/20001/README.md
File README.md (right):

https://codereview.chromium.org/926723002/diff/20001/README.md#newcode38
README.md:38: $ ninja -C out/Debug -j 10
On 2015/02/13 22:27:22, jamesr wrote:
> can you update this too?

I'm happy to update it, but can you clarify what you want updated? It is for use
outside of Google, so the -j parameter is okay. In the next paragraph I talk
about using mojob.py, but I note that you can't specify targets with that
strategy.

[jamesr, 2015-02-14 00:50:11]

Ah, I see.  That's fine then.

[jamesr, 2015-02-18 22:46:31]

(still lgtm if you were waiting)

[jimbe, 2015-02-18 22:56:04]

Committed patchset #2 (id:20001) manually as
0ac4ba45ca77ce9f13769a0a34489f5020edb217 (presubmit successful).