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

Unified 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 side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: README.txt
diff --git a/README.txt b/README.txt
index dfcbb3c40f98c30306f068ef3529026941496f64..3cf16df7929f783f1c815bfcab32d29954313f26 100644
--- a/README.txt
+++ b/README.txt
@@ -1,23 +1,36 @@
To use frog:
-1) Create a symbol link for the VM:
- # From the frog folder:
- mkdir bin
- ln -s $DART/$OUTDIR_PREFIX/Release_ia32/dart_bin bin/dart_bin
+1) Frog is now included in the checkout of the public repo of the bleeding_edge
+ branch. The code will be located under $DART/frog.
-2) Make sure you have 'node' in your path (http://nodejs.org/, and
+ Note that $DART/frog/ is a separate dependency in 'all.deps/DEPS', for this
+ reason changes in the frog directory will have to be submitted separately
+ from changes to the rest of the dart repo.
+
+ (git users): If you'd prefer to use git, you can do the following to have a
+ git setup for the frog subdirectory:
+ $ rm -rf $DART/frog/
+ $ cd $DART
+ $ git svn clone -rHEAD https://dart.googlecode.com/svn/experimental/frog frog
+
+2) Create a symbol link for the VM:
+ $ cd $DART/frog/
+ $ mkdir bin
+ $ ln -s $DART/$OUTDIR_PREFIX/Release_ia32/dart_bin bin/dart_bin
+
+3) Make sure you have 'node' in your path (http://nodejs.org/, and
https://github.com/joyent/node/wiki/Installation for how to install)
You can then do:
-$ ../tools/build.py --mode=release,debug frog
-$ ../tools/test.py --report -t 5 -p color --mode=release,debug frog
+ $ ../tools/build.py --mode=release,debug
+ $ ../tools/test.py --report -t 5 -p color --mode=release,debug frog
The 'release' version of frog is the self-hosted frog.
The 'debug' version of frog is frog running on the VM.
To use the self-hosted compiler called frogsh (for frog self-hosted), run:
-./frog.py --js_out=frogsh -- frog.dart
+ $ ./frog.py --js_out=frogsh -- frog.dart
(this will make frogsh the same as
$DART/frog/$OUTDIR_PREFIX/Release_ia32/dart_bin)
@@ -26,11 +39,11 @@ It is recommended that you run this command on every commit.
To run the self-hosted compiler, you can just type frogsh.
-> ./frogsh tests/hello.dart
-hello world
+ $ ./frogsh tests/hello.dart
+This should print 'hello world'.
Running html tests:
-> ./frog.py --html -- tests/htmltest.dart
-> ./frog.py --html -- tests/canvastest.dart
+ $ ./frog.py --html -- tests/htmltest.dart
+ $ ./frog.py --html -- tests/canvastest.dart
-These will open a browser--verify in the console that no errors happened.
+These will open a browser -- verify in the console that no errors happened.
« 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