Add support for -boot flag, which allows in-tree execution of Ur/Web

The boot flag rewrites most hardcoded paths to point to the build
directory, and also forces static compilation.  This is convenient
for developing Ur/Web, or if you cannot 'sudo make install' Ur/Web.

The following changes were made:
* Header files were moved to include/urweb instead of include;
  this lets FFI users point their C_INCLUDE_PATH at this directory
  at write <urweb/urweb.h>.  For internal Ur/Web executables,
  we simply pass -I$PATH/include/urweb as normal.
* Differentiate between LIB and SRCLIB; SRCLIB is Ur and JavaScript
  source files, while LIB is compiled products from libtool.  For
  in-tree compilation these live in different places.
* No longer reference Config for paths; instead use Settings; these
  settings can be changed dynamically by Compiler.enableBoot ()
  (TODO: add a disableBoot function.)
* config.h is now generated directly in include/urweb/config.h,
  for consistency's sake (especially since it gets installed
  along with the rest of the headers!)
* All of the autotools build products got updated.
* The linkStatic field in protocols now only contains the name of the
  build product, and not the absolute path.

Future users have to be careful not to reference the Settings files
to early, lest they get an old version (this was the source of two
bugs during development of this patch.)

1 files changed, 2 insertions, 0 deletions

diff --git a/doc/manual.tex b/doc/manual.tex
index 06731357..853febe7 100644
--- a/doc/manual.tex
+++ b/doc/manual.tex
@@ -225,6 +225,8 @@ Communication happens via a UNIX domain socket in file \cd{.urweb\_daemon} in th
 
 Some other command-line parameters are accepted:
 \begin{itemize}
+\item \texttt{-boot}: Run Ur/Web from a build tree (and not from a system install).  This is useful if you're testing the compiler and don't want to install it.  It forces generation of statically linked executables.
+
 \item \texttt{-db <DBSTRING>}: Set database connection information, using the format expected by Postgres's \texttt{PQconnectdb()}, which is \texttt{name1=value1 ... nameN=valueN}.  The same format is also parsed and used to discover connection parameters for MySQL and SQLite.  The only significant settings for MySQL are \texttt{host}, \texttt{hostaddr}, \texttt{port}, \texttt{dbname}, \texttt{user}, and \texttt{password}.  The only significant setting for SQLite is \texttt{dbname}, which is interpreted as the filesystem path to the database.  Additionally, when using SQLite, a database string may be just a file path.
 
 \item \texttt{-dbms [postgres|mysql|sqlite]}: Sets the database backend to use.