Introduction

This code is used to build, re-build, and trouble shoot the building of the package, including

  1. Building/compiling diffrent components
  2. Building the pkgdown website

These are mostly commands that can be launched from within RStudio via the GUI, except pkgdown::build_site()

devtools functions

library(devtools)

Clean vignettes

“This uses a fairly rudimentary algorithm where any files in ‘inst/doc’ with a name that exists in ‘vignettes’ are removed.”

Build vignettes

“Builds package vignettes using the same algorithm that R CMD build does”

Build documentation

document()

devtools::document(roclets=c('rd', 'collate', 'namespace'))

Load all

Check

check_failures

pckgdown functions

Build package down website

Single function to build whole site: “This will generate a docs/ directory. The home page will be generated from your package’s README.md, and a function reference will be generated from the documentation in the man/ directory.”

Build piece by piece

pkgdown::clean_site (pkg = “.”)

– Initialising site

Building home

Building function reference

Build vignettes

Keep logs files (?)

options(keep.source.pkgs = TRUE)
devtools::check()

Rcmd.exe

“Clean and rebuild” ==> Rcmd.exe INSTALL –preclean –no-multiarch –with-keep.source mammalsmilk

“Install restart” ==> Rcmd.exe INSTALL –no-multiarch –with-keep.source mammalsmilk

devtools::check(env_vars = )

devtools::check()

See ‘C:/Users/lisanjie/Documents/1_R/git/git-aviary/FACavian.Rcheck/00install.out’ for details. Information on the location(s) of code generating the ‘Note’s can be obtained by re-running with environment variable R_KEEP_PKG_SOURCE set to ’yes’.