Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(374)

Side by Side Diff: README.txt

Issue 8396026: Fix readme for frog. (Closed) Base URL: https://dart.googlecode.com/svn/experimental/frog
Patch Set: '' Created 9 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 To use frog: 1 To use frog:
2 2
3 1) Create a symbol link for the VM: 3 1) Frog is now included in the checkout of the public repo of the bleeding_edge
4 # From the frog folder: 4 branch. The code will be located under $DART/frog.
5 mkdir bin
6 ln -s $DART/$OUTDIR_PREFIX/Release_ia32/dart_bin bin/dart_bin
7 5
8 2) Make sure you have 'node' in your path (http://nodejs.org/, and 6 Note that $DART/frog/ is a separate dependency in 'all.deps/DEPS', for this
7 reason changes in the frog directory will have to be submitted separately
8 from changes to the rest of the dart repo.
9
10 (git users): If you'd prefer to use git, you can do the following to have a
11 git setup for the frog subdirectory:
12 $ rm -rf $DART/frog/
13 $ cd $DART
14 $ git svn clone -rHEAD https://dart.googlecode.com/svn/experimental/frog frog
15
16 2) Create a symbol link for the VM:
17 $ cd $DART/frog/
18 $ mkdir bin
19 $ ln -s $DART/$OUTDIR_PREFIX/Release_ia32/dart_bin bin/dart_bin
20
21 3) Make sure you have 'node' in your path (http://nodejs.org/, and
9 https://github.com/joyent/node/wiki/Installation for how to install) 22 https://github.com/joyent/node/wiki/Installation for how to install)
10 23
11 You can then do: 24 You can then do:
12 $ ../tools/build.py --mode=release,debug frog 25 $ ../tools/build.py --mode=release,debug
13 $ ../tools/test.py --report -t 5 -p color --mode=release,debug frog 26 $ ../tools/test.py --report -t 5 -p color --mode=release,debug frog
14 27
15 The 'release' version of frog is the self-hosted frog. 28 The 'release' version of frog is the self-hosted frog.
16 The 'debug' version of frog is frog running on the VM. 29 The 'debug' version of frog is frog running on the VM.
17 30
18 To use the self-hosted compiler called frogsh (for frog self-hosted), run: 31 To use the self-hosted compiler called frogsh (for frog self-hosted), run:
19 32
20 ./frog.py --js_out=frogsh -- frog.dart 33 $ ./frog.py --js_out=frogsh -- frog.dart
21 34
22 (this will make frogsh the same as 35 (this will make frogsh the same as
23 $DART/frog/$OUTDIR_PREFIX/Release_ia32/dart_bin) 36 $DART/frog/$OUTDIR_PREFIX/Release_ia32/dart_bin)
24 37
25 It is recommended that you run this command on every commit. 38 It is recommended that you run this command on every commit.
26 39
27 To run the self-hosted compiler, you can just type frogsh. 40 To run the self-hosted compiler, you can just type frogsh.
28 41
29 > ./frogsh tests/hello.dart 42 $ ./frogsh tests/hello.dart
30 hello world 43 This should print 'hello world'.
31 44
32 Running html tests: 45 Running html tests:
33 > ./frog.py --html -- tests/htmltest.dart 46 $ ./frog.py --html -- tests/htmltest.dart
34 > ./frog.py --html -- tests/canvastest.dart 47 $ ./frog.py --html -- tests/canvastest.dart
35 48
36 These will open a browser--verify in the console that no errors happened. 49 These will open a browser -- verify in the console that no errors happened.
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698