Mercurial > urweb

comparison doc/manual.tex @ 1875:c44bfaa69dd8

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Manual entries for -ccompiler and -print-ccompiler
author Adam Chlipala <adam@chlipala.net>
date Thu, 10 Oct 2013 14:01:19 -0400
parents 30c56e3bcf47
children df6a040f5389
comparison
equal deleted inserted replaced
1874:11d8e220f36f 1875:c44bfaa69dd8
229 229
230 Some other command-line parameters are accepted: 230 Some other command-line parameters are accepted:
231 \begin{itemize} 231 \begin{itemize}
232 \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. 232 \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.
233 233
234 \item \texttt{-ccompiler <PROGRAM>}: Select an alternative C compiler to call with command lines in compiling Ur/Web applications. (It's possible to set the default compiler as part of the \texttt{configure} process, but it may sometimes be useful to override the default.)
235
234 \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. 236 \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.
235 237
236 \item \texttt{-dbms [postgres|mysql|sqlite]}: Sets the database backend to use. 238 \item \texttt{-dbms [postgres|mysql|sqlite]}: Sets the database backend to use.
237 \begin{itemize} 239 \begin{itemize}
238 \item \texttt{postgres}: This is PostgreSQL, the default. Among the supported engines, Postgres best matches the design philosophy behind Ur, with a focus on consistent views of data, even in the face of much concurrency. Different database engines have different quirks of SQL syntax. Ur/Web tends to use Postgres idioms where there are choices to be made, though the compiler translates SQL as needed to support other backends. 240 \item \texttt{postgres}: This is PostgreSQL, the default. Among the supported engines, Postgres best matches the design philosophy behind Ur, with a focus on consistent views of data, even in the face of much concurrency. Different database engines have different quirks of SQL syntax. Ur/Web tends to use Postgres idioms where there are choices to be made, though the compiler translates SQL as needed to support other backends.
268 \item \texttt{-output FILENAME}: Set where the application executable is written. 270 \item \texttt{-output FILENAME}: Set where the application executable is written.
269 271
270 \item \texttt{-path NAME VALUE}: Set the value of path variable \texttt{\$NAME} to \texttt{VALUE}, for use in \texttt{.urp} files. 272 \item \texttt{-path NAME VALUE}: Set the value of path variable \texttt{\$NAME} to \texttt{VALUE}, for use in \texttt{.urp} files.
271 273
272 \item \texttt{-prefix PREFIX}: Equivalent to the \texttt{prefix} directive from \texttt{.urp} files 274 \item \texttt{-prefix PREFIX}: Equivalent to the \texttt{prefix} directive from \texttt{.urp} files
275
276 \item \texttt{-print-ccompiler}: Print the C compiler being used.
273 277
274 \item \texttt{-protocol [http|cgi|fastcgi|static]}: Set the protocol that the generated application speaks. 278 \item \texttt{-protocol [http|cgi|fastcgi|static]}: Set the protocol that the generated application speaks.
275 \begin{itemize} 279 \begin{itemize}
276 \item \texttt{http}: This is the default. It is for building standalone web servers that can be accessed by web browsers directly. 280 \item \texttt{http}: This is the default. It is for building standalone web servers that can be accessed by web browsers directly.
277 281