On 18 December 2017 at 16:10, Jeroen Ooms wrote: | On Mon, Dec 18, 2017 at 2:40 PM, Dirk Eddelbuettel <e...@debian.org> wrote: | > | > (Moderately wrong list: r-package-devel for packaging questions, rcpp-devel | > for Rcpp questions) | > | > On 18 December 2017 at 13:24, Stravs, Michael wrote: | > | I am trying to make a package B that extends another package A. Package A uses Rcpp, and I want to extend a class X used there. | | Another, perhaps simpler example is the xslt package which is an | extension for the xml2 package. The xml2 package exposes its object | types (via ./inst/include/xml2_types.h) so that the xslt package get | to the underlying libxml2 objects.
That is nice too, but doesn't in your case the object code comes from the external libxml2 only? Michael wanted to get at code from another R package, and those shared libraries from R packages are not system-wide visible. Hence the problem. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
