\HeaderA{PkgUtils}{Utilities for Building and Checking Add-on Packages}{PkgUtils}
\aliasA{build}{PkgUtils}{build}
\aliasA{check}{PkgUtils}{check}
\keyword{utilities}{PkgUtils}
\begin{Description}\relax
Utilities for checking whether the sources of an \R{} add-on package
work correctly, and for building a source or binary package from
them.
\end{Description}
\begin{Usage}
\begin{verbatim}
R CMD build [options] pkgdirs
R CMD check [options] pkgdirs
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{pkgdirs}] a list of names of directories with sources of \R{}
add-on packages.
\item[\code{options}] further options to control the processing, or for
obtaining information about usage and version of the utility.
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
\code{R CMD check}
checks \R{} add-on packages from their sources, performing a wide
variety of diagnostic checks.

\code{R CMD build}
builds \R{} source or binary packages from their sources.  It will
create index files in the sources if necessary, so it is often helpful
to run \code{build} before \code{check}.

Use
\code{R CMD foo --help}
to obtain usage information on utility \code{foo}.

Several of the options to \code{build --binary} are passed to
\code{\LinkA{INSTALL}{INSTALL}} so consult its help for the details.
\end{Details}
\begin{SeeAlso}\relax
The sections on \dQuote{Checking and building packages} and
\dQuote{Processing Rd format} in \dQuote{Writing \R{} Extensions}
(see the \file{doc/manual} subdirectory of the \R{} source tree).

\code{\LinkA{INSTALL}{INSTALL}} is called by \code{build --binary}.
\end{SeeAlso}