Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 To integrate frog into a checkout of the public repo, you need to do: | 1 1) Frog is now included in the checkout of the public repo of the bleeding_edge |
| 2 branch. The code will be located under $DART/frog. | |
| 2 | 3 |
| 3 1) Edit the .gclient file of your checkout of the public repo, and | 4 Note that $DART/frog/ is a separate dependency in all.deps/DEPS, for this |
| 4 add to the 'solutions' array: | 5 reason changes in the frog directory will have to be submitted separately |
|
Emily Fortuna
2011/10/26 00:04:39
Merge this stuff with what I checked in, and then
| |
| 5 { | 6 from changes to the rest of the dart repo. |
| 6 "name": "frog.deps", | |
| 7 "url": "https://dart.googlecode.com/svn/experimental/frog/deps", | |
| 8 }, | |
| 9 | 7 |
| 10 See http://www.chromium.org/developers/how-tos/chromium-modularization#Advance d_Usage | 8 Note: if you'd prefer to use git, you can do the following: |
| 11 | 9 $ rm -rf $DART/frog/ |
| 12 Note: if you'd prefer to use git, follow these steps before "gclient sync" | 10 $ cd $DART |
| 13 cd $DART | 11 $ git svn clone -rHEAD https://dart.googlecode.com/svn/experimental/frog frog |
| 14 git svn clone -rHEAD https://dart.googlecode.com/svn/experimental/frog frog | |
| 15 | 12 |
| 16 2) Now sync: | 13 2) Now sync: |
| 17 $ gclient sync | 14 $ gclient sync |
| 18 | 15 |
| 19 3) Create a symbol link for the VM: | 16 3) Create a symbol link for the VM: |
| 20 # From the frog folder: | 17 $ cd $DART/frog/ |
| 21 mkdir bin | 18 $ mkdir bin |
| 22 ln -s $DART/$OUTDIR_PREFIX/Release_ia32/dart_bin bin/dart_bin | 19 $ ln -s $DART/$OUTDIR_PREFIX/Release_ia32/dart_bin bin/dart_bin |
| 23 | 20 |
| 24 4) Make sure you have 'node' in your path (http://nodejs.org/, and | 21 4) Make sure you have 'node' in your path (http://nodejs.org/, and |
| 25 https://github.com/joyent/node/wiki/Installation for how to install) | 22 https://github.com/joyent/node/wiki/Installation for how to install) |
| 26 | 23 |
| 27 You can then do: | 24 You can then do: |
| 28 $ ../tools/build.py --mode=release,debug frog | 25 $ ../tools/build.py --mode=release,debug |
| 29 $ ../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 |
| 30 | 27 |
| 31 The 'release' version of frog is the self-hosted frog. | 28 The 'release' version of frog is the self-hosted frog. |
| 32 The 'debug' version of frog is frog running on the VM. | 29 The 'debug' version of frog is frog running on the VM. |
| 33 | 30 |
| 34 To run the self-hosted compiler, you can just type frog.js. | 31 To run the self-hosted compiler, you can just type frog.js. |
| 35 | 32 |
| 36 > ./frog.js tests/hello.dart | 33 > ./frog.js tests/hello.dart |
| 37 hello world | 34 hello world |
| 38 | 35 |
| 39 Running html tests: | 36 Running html tests: |
| 40 > ./frog.py --html -- tests/htmltest.dart | 37 > ./frog.py --html -- tests/htmltest.dart |
| 41 > ./frog.py --html -- tests/canvastest.dart | 38 > ./frog.py --html -- tests/canvastest.dart |
| 42 | 39 |
| 43 These will open a browser--verify in the console that no errors happened. | 40 These will open a browser--verify in the console that no errors happened. |
| OLD | NEW |