Home My Page Projects Code Snippets Project Openings SML/NJ
Summary Activity Forums Tracker Lists Tasks Docs Surveys News SCM Files

SCM Repository

[smlnj] Diff of /sml/trunk/src/cm/Doc/manual.tex
ViewVC logotype

Diff of /sml/trunk/src/cm/Doc/manual.tex

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 568, Tue Mar 7 03:59:09 2000 UTC revision 569, Tue Mar 7 04:01:07 2000 UTC
# Line 321  Line 321 
321  mapping is initialized by reading two configuration files: an  mapping is initialized by reading two configuration files: an
322  installation-specific one and a user-specific one.  After that, the  installation-specific one and a user-specific one.  After that, the
323  mapping can be maintained using CM's interface functions {\tt  mapping can be maintained using CM's interface functions {\tt
324  CM.Anchor.set}, {\tt CM.Anchor.cancel}, and {\tt CM.Anchor.reset}  CM.Anchor.anchor} and {\tt CM.Anchor.reset} (see
325  (see Section~\ref{sec:api}).  Section~\ref{sec:api}).
326    
327  The default location of the installation-specific configuration file  The default location of the installation-specific configuration file
328  is {\tt /usr/lib/smlnj-pathconfig}.  However, normally this default  is {\tt /usr/lib/smlnj-pathconfig}.  However, normally this default
# Line 529  Line 529 
529    
530  \begin{verbatim}  \begin{verbatim}
531    structure Anchor : sig    structure Anchor : sig
532      val set : { anchor: string, path: string } -> unit      val anchor : string -> string option controller
     val cancel : string -> unit  
533      val reset : unit -> unit      val reset : unit -> unit
534    end    end
535  \end{verbatim}  \end{verbatim}
536    
537  {\tt CM.Anchor.set} creates a new association or replaces an existing  {\tt CM.Anchor.anchor} returns a pair of {\tt get} and {\tt set}
538  association of an anchor name with a directory name.  Both names must  functions that can be used to query and modify the status of the named
539  be given as strings---the directory name in native syntax.  If the  anchor.  Note that the {\tt get}-{\tt set}-pair operates over type
540  directory name is a relative path name, then it will be expanded by  {\tt string option}; a value of {\tt NONE} means that the anchor is
541  prepending the name of the current working directory.  currently not bound (or, in the case of {\tt set}, that it is being
542    cancelled).  The (optional) string given to {\tt set} must be a
543  {\tt CM.Anchor.cancel} deletes the association of the given anchor name  directory name in native syntax.  If it is specified as a relative
544  with its directory should such an association currently exist.  path name, then it will be expanded by prepending the name of the
545  Otherwise it will do nothing.  current working directory.
546    
547  {\tt CM.Anchor.reset} erases the entire existing path configuration  {\tt CM.Anchor.reset} erases the entire existing path configuration
548  mapping.  mapping.
# Line 1375  Line 1374 
1374  \subsection{Parallel bootstrap compilation}  \subsection{Parallel bootstrap compilation}
1375    
1376  The bootstrap compiler\footnote{otherwise not mentioned in this  The bootstrap compiler\footnote{otherwise not mentioned in this
1377  document} with its functions {\tt CMB.make}, {\tt CMB.deliver}, and  document} with its main function {\tt CMB.make} and the corresponding
1378  the corresponding cross-compilation variants of the bootstrap compiler  cross-compilation variants of the bootstrap compiler will also use any
1379  will also use any attached compile servers.  If one intends to  attached compile servers.  If one intends to exclusively use the
1380  exclusively use the bootstrap compiler, one can even attach servers  bootstrap compiler, one can even attach servers that run on machines
1381  that run on machines with different architecture or operating system.  with different architecture or operating system.
1382    
1383  Since the master-slave protocol is fairly simple, it cannot handle  Since the master-slave protocol is fairly simple, it cannot handle
1384  complicated scenarios such as the one necessary for setting up the  complicated scenarios such as the one necessary for compiling the
1385  initial (pervasive) environment during {\tt CMB.make}.  Therefore,  ``init group'' (i.e., the small set of files necessary for setting up
1386  this will always be done locally by the master process.  the ``pervasive'' environment) during {\tt CMB.make}.  Therefore, this
1387    will always be done locally by the master process.
1388    
1389  \section{Example: Dynamic linking}  \section{Example: Dynamic linking}
1390  \label{sec:dynlink}  \label{sec:dynlink}

Legend:
Removed from v.568  
changed lines
  Added in v.569

root@smlnj-gforge.cs.uchicago.edu
ViewVC Help
Powered by ViewVC 1.0.0