Fix ddc USAGE doc.

Fix ddc USAGE doc.

The only substantive change is adding the missing
"--dart-sdk-summary=build" parameter to building the SDK. I went ahead
and prettied up the Markdown too while I was at it.

R=vsm@google.com

Committed: https://github.com/dart-lang/sdk/commit/e5a45ffb5c205184da874c718ef9ea6d845c5cc2

[Bob Nystrom, 2017-01-11 00:12:23]

rnystrom@google.com changed reviewers:
+ vsm@google.com

[vsm, 2017-01-11 00:23:45]

https://codereview.chromium.org/2620203002/diff/1/pkg/dev_compiler/USAGE.md
File pkg/dev_compiler/USAGE.md (right):

https://codereview.chromium.org/2620203002/diff/1/pkg/dev_compiler/USAGE.md#n...
pkg/dev_compiler/USAGE.md:13: 1.  Clone the [DDC
repository](https://github.com/dart-lang/dev_compiler) and
This should now point to the sdk:

https://github.com/dart-lang/sdk

with DDC_PATH pointing to the pkg/dev_compiler subdir.

https://codereview.chromium.org/2620203002/diff/1/pkg/dev_compiler/USAGE.md#n...
pkg/dev_compiler/USAGE.md:23: 3.  Create a node compatible version of the
dart_sdk:
I think you can skip step #3 altogether and replace #4 with:

export NODE_PATH=$DDC_PATH/lib/js/common:.

https://codereview.chromium.org/2620203002/diff/1/pkg/dev_compiler/USAGE.md#n...
pkg/dev_compiler/USAGE.md:86: ## Feedback
Now that we're built as part of the SDK, someone who just want to play with the
prebuilt dartdevc snapshot - and not checkout the dart repo - could do the above
with
`dartdevc` instead of `dart $DDC_PATH/bin/dartdevc.dart`

and

NODE_PATH=$DART_SDK/lib/dev_compiler/common:.

(assuming DART_SDK points to their installed SDK).

Do you think that's worth adding?

[Bob Nystrom, 2017-01-11 00:55:16]

https://codereview.chromium.org/2620203002/diff/1/pkg/dev_compiler/USAGE.md
File pkg/dev_compiler/USAGE.md (right):

https://codereview.chromium.org/2620203002/diff/1/pkg/dev_compiler/USAGE.md#n...
pkg/dev_compiler/USAGE.md:13: 1.  Clone the [DDC
repository](https://github.com/dart-lang/dev_compiler) and
On 2017/01/11 00:23:45, vsm wrote:
> This should now point to the sdk:
> 
> https://github.com/dart-lang/sdk
> 
> with DDC_PATH pointing to the pkg/dev_compiler subdir.

Done.

https://codereview.chromium.org/2620203002/diff/1/pkg/dev_compiler/USAGE.md#n...
pkg/dev_compiler/USAGE.md:23: 3.  Create a node compatible version of the
dart_sdk:
On 2017/01/11 00:23:45, vsm wrote:
> I think you can skip step #3 altogether and replace #4 with:
> 
> export NODE_PATH=$DDC_PATH/lib/js/common:.

Done.

https://codereview.chromium.org/2620203002/diff/1/pkg/dev_compiler/USAGE.md#n...
pkg/dev_compiler/USAGE.md:86: ## Feedback
On 2017/01/11 00:23:45, vsm wrote:
> Now that we're built as part of the SDK, someone who just want to play with
the
> prebuilt dartdevc snapshot - and not checkout the dart repo - could do the
above
> with
> `dartdevc` instead of `dart $DDC_PATH/bin/dartdevc.dart`
> 
> and
> 
> NODE_PATH=$DART_SDK/lib/dev_compiler/common:.
> 
> (assuming DART_SDK points to their installed SDK).
> 
> Do you think that's worth adding?
> 

...yes, but I wasn't planning to rewrite this whole doc right now. :)

[vsm, 2017-01-11 02:06:29]

lgtm!

[Bob Nystrom, 2017-01-11 17:51:39]

Description was changed from

==========
Fix ddc USAGE doc.

The only substantive change is adding the missing
"--dart-sdk-summary=build" parameter to building the SDK. I went ahead
and prettied up the Markdown too while I was at it.
==========

to

==========
Fix ddc USAGE doc.

The only substantive change is adding the missing
"--dart-sdk-summary=build" parameter to building the SDK. I went ahead
and prettied up the Markdown too while I was at it.

R=vsm@google.com

Committed:
https://github.com/dart-lang/sdk/commit/e5a45ffb5c205184da874c718ef9ea6d845c5cc2
==========

[Bob Nystrom, 2017-01-11 17:51:40]

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