Hi Dirk thanks for the feedback. So I guess that means those are new WARNING messages on CRAN that were not there at the time RInside was accepted on CRAN, right? I would suggest moving the discussion to R-pkg-devel to see if CRAN could recommend a way to support install-time compilation of the static library that we need. If CRAN is not willing/able to accommodate that, we could just put the C++ source code somewhere other than pkg/src, and then compile it AFTER the package has been installed, when the user requests that we fuzz their Rcpp package. That won't be much of a drawback / portability issue, because anyways the main functionality of our package requires a compiler on the user's system.
On Sat, Jun 27, 2020 at 4:51 PM Dirk Eddelbuettel <e...@debian.org> wrote: > > Toby, Akhila, > > My bad, I'm sorry! > > So I went back glancing at > > https://cloud.r-project.org/web/checks/check_results_RInside.html > > and the only clear suggestion is that one would probably no longer get a > package like that admitted. That is potentially bad news for your project. > > Sorry to be bearer of bad news, but I do not make or impose these rules. > > Dirk > > -- > http://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
