Also, it is important that all compiler flags are set consistently among all compilation units to insure proper linkage, and this policy helps keep those settings in one place.
On November 5, 2020 6:10:55 PM PST, Dirk Eddelbuettel <e...@debian.org> wrote: > >On 4 November 2020 at 15:24, Jon Davidson wrote: >| I have an existing Rcpp module that has already been compiled into a >.so. >| How can I integrate this into an R package? > >I am afraid you can't as an .so file can only be used on one >architecture, >and likely one subsets thereof (i.e. a Debian object file may not work >on >Fedora, or Ubuntu, or maybe even a different Debian version). > >That is why "the documentation" (ie WRE, CRAN Policy) say source only. > >| The existing vignette for packaging an Rcpp module involves including >the >| C++ source in the package folder, which will not be feasible for my >| setup. I can, however, have the compiled .so file in the folder. >Thanks for >| your help! > >Dirk > >-- >https://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 -- Sent from my phone. Please excuse my brevity. _______________________________________________ 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
