Updated build instructions.

build/howto.txt

@@ -1,4 +1,4 @@
-HOW TO BUILD PROCESSING ON YOUR FAVORITE PLATFORM
+HOW TO BUILD ARDUINO ON YOUR FAVORITE PLATFORM
 
 With frequently asked questions, scroll to the end of the file.
 
@@ -45,32 +45,20 @@ installer every few months to keep things fresh.
     up through the more recent Xcode stuff. 
 
 
-1c. On Linux, you're pretty much on your own.. You need a pretty 
+1c. On Linux, you're pretty much on your own.. You need jikes (or
-    standard development setup.
+    edit make.sh to use a different compiler), java, avr-gcc, make,
+    and subversion.  You'll also have to set some environment
+    variables (see make.sh for details).
 
 
-2. GRAB THE CODE FROM SOURCEFORGE
+2. GRAB THE CODE FROM BERLIOS
 
-* this grabs the code as an anonymous user. if you have a sourceforge
+* this grabs the code as an anonymous user. 
-  account, you should know how to grab the code as yourself.
 
-# first do this
+# grab the code, it'll take a while
-cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/processing login
+svn co svn://svn.berlios.de/arduino/trunk
-# just hit enter when it asks for a password
-
-# then do this (may take a while)
-cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/processing co processing
 # (maybe even a long while for you dialup and international folks)
 
-# gonna do a few things in the p5 folder
-cd processing
-
-# a quick cleanup, removes empty (dead/old) folders
-cvs update -P
-
-# get back to the processing/ folder
-cd ..
-
 
 3. INSTALL QUICKTIME FOR JAVA (windows users only)
 
@@ -90,13 +78,13 @@ cd ..
 4. BUILD IT
 
 # now to build for the first time:
-cd /path/to/processing/build/windows
+cd /path/to/arduino/build/windows
 
 # or if you're on linux
-cd /path/to/processing/build/linux
+cd /path/to/arduino/build/linux
 
 # for the followers of goatee man
-cd /path/to/processing/build/macosx
+cd /path/to/arduino/build/macosx
 
 # and then..
 ./make.sh
@@ -118,34 +106,15 @@ cd /path/to/processing/build/macosx
 
 5a. Each time you want to update to latest version from cvs:
 
-cd /path/to/processing
+cd /path/to/arduino
-cvs -z3 update
+svn update
-# -z3 means make it snappy (using compression)
 
 
 5b. If new folders have been added, or you're gettin odd errors, use:
 
-# get to the processing folder
-cd /path/to/processing
-
 # remove the work directory
 rm -rf work
 
-# -d grabs new directories and -P cleans out old (empty) ones
-# cvs is a little brain dead about this stuff
-cvs -z3 update -d -P
-
-Unfortunately there isn't a way to know (?) if new folders have
-since been added. but if you're getting "class not found" errors
-while building, then that's a good indicator that something is
-missing from a subfolder.
-
-If there have been significant changes, or you get weird build
-errors, try deleting your 'work' folder. This will create a 
-fresh build. This includes any changes to the reference, 
-the examples, the libraries, jikes, or just about any time you
-have to use -d -P with the update.
-
 
 ////////////////////////////////////////////////////////////////////
 
@@ -159,10 +128,12 @@ seem. Hopefully it's just a matter of following the instructions
 above (and being patient). If not, let us know where you have trouble
 so we can fix things.
 
-Conceivably, it wouldn't take much to make Processing build under
+Conceivably, it wouldn't take much to make Arduino build under
 Eclipse or any other IDE, but we don't do it by default. Same goes for 
 ANT. We don't use it, but if someone were to make build scripts that 
 emulated everything that the current build scripts do (not just build
 the code, but all the other annoying crap that the build scripts do) 
 then maybe we could switch to it. It's all about reaching some kind 
 of critical mass. 
+
+$Id:$