Skip to content

Commit 6c75e85

Browse files
committed
recommend importFrom in Rcpp FAQ (closes #1030)
1 parent e77e79c commit 6c75e85

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

ChangeLog

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
2019-12-05 Dirk Eddelbuettel <[email protected]>
2+
3+
* vignettes/rmd/Rcpp-FAQ.Rmd (Rcpp): Add entry about "'dataptr' (or
4+
'enterRNGScope') not provided by Rcpp" recommending proper importFrom
5+
16
2019-12-03 Dirk Eddelbuettel <[email protected]>
27

38
* docker/ci/Dockerfile: Lighter builds as fewer Suggests:

vignettes/rmd/Rcpp-FAQ.Rmd

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1754,3 +1754,10 @@ Rcpp Modules \citep{CRAN:Rcpp:Modules}. Some more background on the linking
17541754
requirement is [in this SO
17551755
question](https://stackoverflow.com/questions/2424836/exceptions-are-not-caught-in-gcc-program).
17561756

1757+
## My package fails with 'dataptr' (or 'enterRNGScope') not provided by Rcpp
1758+
1759+
For your package, it is generally recommended to have both `Imports:` and
1760+
`LinkingTo:` in the file `DESCRIPTION` combined with an explicit
1761+
`importFrom("Rcpp", "evalCpp")` in the file `NAMESPACE`. Doing so ensures
1762+
that certain symbols are registered when your package is loaded by R, and
1763+
that certain Rcpp functions are properly resolved.

0 commit comments

Comments
 (0)