[Rcpp-devel] Question regarding new pacakge registration requirements
On Thu, Mar 30, 2017 at 4:06 PM, Tim Keitt <tkeitt at utexas.edu> wrote:
On Thu, Mar 30, 2017 at 2:55 PM, Avraham Adler <avraham.adler at gmail.com> wrote:
If so, do I add them asa regards the functions *I* wrote in lamw.cpp or as regards the function wrappers that Rcpp wrote and the .R files call in RcppExports.R?
I'm a bit confused about this as well. My impression is that the only
reason to register functions is so that *other* packages can call them. If
you do not want to make them available, you don't need to register them. Or
I could have that complete wrong.
THK
If you don't want to register anything, this snippet placed in init.c will
get you past CRAN checks currently:
#include <R.h>
#include <Rinternals.h>
#include <R_ext/Rdynload.h>
R_CallMethodDef callMethods[] = {{NULL, NULL, 0}};
R_CMethodDef cMethods[] = {{NULL, NULL, 0}};
void
R_init_myLib(DllInfo *info)
{
R_registerRoutines(info, cMethods, callMethods, NULL, NULL);
R_useDynamicSymbols(info, FALSE);
}
http://www.keittlab.org/
Hello, Tim. Thank you for the quick response. However, there are three packages which import the package, and one which links to it [1], which is why I have Rcpp-created headers in the /inst/include directory [2]. I do not want to do anything which jeopardizes the downstream users but I do want to be in compliance. Thanks, Avi [1] https://cran.r-project.org/web/packages/lamW/index.html [2] https://bitbucket.org/aadler/lamw/src/a3f5b043872b1761dd5140d77216842fcc3adad7/inst/include/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.r-forge.r-project.org/pipermail/rcpp-devel/attachments/20170330/73915f2b/attachment-0001.html>