Sorry for being slow to respond (very busy morning at work and play, got five such emails myself) but as Inaki and Georgi helpfully pointed out already the issue is _known_ and has a _fix_ at either the default branch of the Rcpp repo, or, if you prefer, via the Rcpp drat repo as detailed in this comment of issue #1287 at the Rcpp repo
https://github.com/RcppCore/Rcpp/issues/1287#issuecomment-1829886024 from which I quote (and, again, sorry for not posting here sooner) Yes, I actually got five such emails myself today for packages of mine using Rcpp. The fix is simple thanks to PR #1288 we made two days ago. Install Rcpp 1.0.11.5 from the Rcpp drat repo via, e.g., Rscript -e 'install.packages("Rcpp", \ repos=c("https://RcppCore.github.io/drat";, getOption("repos")))' and then re-run compileAttributes(). That will fix the RcppExports.cpp file for you. You then need to upload your updated package to CRAN. It has no change in its run-time dependency on Rcpp so you do not need to change anything in DESCRIPTION. Just re-run compileAttributes(). Of course, you can also use whichever tool runs `compileAttributes()` for you. I tend to use `littler` script `compAttr.r` on the command-line. Others rely on RStudio which automagically does it if it notices you rebuild a package using Rcpp. I believe the devtools/usethis nexus has this in `document_all()` (?), and I am sure someone somewhere cooked something up for VSCode too. The key is the provided function Rcpp::compileAttributes() which remains at your service and is now updated. I may also push an updated `rocker/drd` container which I recently switched to being based on ubuntu and r2u (rather than debian). Then installing your build dependencies for you packages is trivial (I run `installDeps.r` inside the container) and it will come with an r-devel build. You "only" need to create `~/.R/Makevars` to tell the compiler to use extended format warnings. That allows you to replicate the CRAN warnings, and ensure rebuild RcppExports.cpp addresses it. If I find time I'll post an example on my blog. Cheers, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org _______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
