+If you want to change the configuration options for the build process,
+place your configuration options in build/config.make
+
+A list of variables that control the build are listed in the file
+build/config-default.make.
+
+Build profiles? What?
+======================
+
+Don't worry about them too much. If you're wondering which to use:
+use the default if you can (that's why it's the default!) and use
+the atomic if you have to.
+
+The default profile uses the C# compiler and class libaries as they
+are built. This lets you build MCS without needing to have already
+installed it, but can fail if the libraries change significantly.
+(This is the source of the dreaded "corlib out of sync" warning, most
+of the time.)
+
+The atomic profile tries to use the system compiler and preexisting
+MCS libraries. New libaries are built against this constant reference
+point, so if a newly built library has a binary incompatibility, the
+rest of your build can proceed.
+
+If you want to always use the atomic profile, run this command:
+
+ ./configure --profile=atomic
+
+More About the Build System
+===========================
+
+More information is found in build/README.*. Here's a quick rundown
+of the features:
+
+ * Unified build system for Windows and Linux. Windows is still
+ fairly untested, but "should work." Unfortunately I don't
+ have a Windows machine to test on, but Gonzalo can get
+ corlib to build I think and that's about as complicated as
+ it gets.
+
+ * Profile support. 'make PROFILE=profilename' or 'export
+ PROFILE=profilename ; make' will work. Profiles are defined
+ in build/profiles/profilename.make ; right now there isn't
+ too much going on. The 'bootstrap' profile will build the
+ way makefile.gnu did on Linux, by setting MONO_PATH and
+ using mcs/mcs.exe; the default profile will build against
+ the existing system libraries and compile with 'mcs', which
+ should reduce a lot of 'corlib out of sync' warnings.
+
+ * Important variables are shared among makefiles now; you can
+ edit build/config.make (see build/config-default.make for a
+ template) and give global settings, or just have a much
+ saner time of writing new makefiles.
+
+ * Response files, stamps, and other build trivia now all land
+ in build/deps/, making the library build directories
+ cleaner.
+
+ * Test libraries now live in class/Library/Library_test.dll,
+ not class/Library/Test. 'make test' will build the test DLL,
+ 'make run-test' will actually run the nunit tests. Set the
+ variable TEST_HARNESS to run with a program other than
+ nunit-console (for example, nunit-gtk).
+
+ * Standardized recursive targets: all, clean, install, test,
+ run-test. Read build/README.makefiles for definitions of
+ what they should do