- I’m unsure how to remove only put
RcppEigen
under theLinkingTo
and not theImports
headers. I’ve gotten different instructions and am very confused what to do. I’ve been learning how to use Eigen myself, so I’m not sure if I did something wrong in writing. I’ve seen Do I need to import RccpEigen in the DESCRIPTION file for an R package using it, or is “LinkingTo” enough? and understand it should - Should my code using RcppEigen be in header files or .cpp files? My understanding was that .h was just for empty definitions of the functions if you need to use it in other cpp files, and .cpp was for the implementation of those functions. Right now I’ve been using .cpp and
#include <RcppEigen.h>
and letting Rcpp generate the requiredRcppExports.cpp
files
I’ve tried testing the package with devtools::check_win_devel()
since that’s what CRAN does and got the reply:
“Package in Depends/Imports which should probably only be in LinkingTo: ‘RcppEigen’“.
So accordingly, I removed RcppEigen from the Imports
and left it in the LinkingTo
section, but now the package fails the R CMD check --as-cran
with:
“Namespace dependency missing from DESCRIPTION Imports/Depends entries: ‘RcppEigen’
See section ‘The DESCRIPTION file’ in the ‘Writing R Extensions’
manual.“
user25262461 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.