I am writing an R package and would like to make a pdf reference manual of all functions in the package. I understood from here that R CMD check
automatically creates a reference manual.
Here I read that a manual entry is created "of the functions you listed in the export section of NAMESPACE".
My NAMESPACE file looks as follows:
# Export all names
exportPattern(".")
# Import all packages listed as Imports or Depends
import(
LIM
)
so I thought everything will be exported. During R CMD check
on the package directory, at the very end it says:
* checking PDF version of manual ... OK
However, I do not find a reference manual in my package directory (I would assume it would be in inst/doc). What am I missing here?
Another way is to create the reference manual directly using:
R CMD Rd2pdf mypackage
where mypackage
is the folder containing your R package code folder structure including the man
folder with your .Rd files.
For some reason I never get the reference manual during build or check in RStudio, maybe because I've missed a setting somewhere. But running the command like this works fine as well.
R CMD check
creates a directory PACKAGE.RCheck
. In this directory you could find the file PACKAGE-manual.pdf
.
I had the same issue. It seems that when you click Build or Check in Rstudio (when using devtools), by default arguments of '--no-manual' are added to the R CMD options.
I solved this by manually giving the arguments in the R command prompt:
library(devtools)
check(cleanup = FALSE,manual = TRUE,path = getwd())
# without running the examples
check(cleanup = FALSE,args = c('--no-examples'),manual = TRUE,path = getwd())
In this case, a folder called package.Rcheck will contain the manual as package-manual.pdf
Also check for any errors in the output during the check. There might be characters that might crash the documentation.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With