RSpectra does not use CHOLMOD, so probably it is not helpful here. I would suggest that you build CHOLMOD as an external library with headers, and then directly link Eigen and your code to the external CHOLMOD, ignoring the one shipped with Matrix. It is just like all other R packages that require external libraries.
Best, Yixuan 2018-01-17 7:35 GMT-05:00 Dirk Eddelbuettel <e...@debian.org>: > > On 17 January 2018 at 13:10, Simon Barthelmé wrote: > | I'm trying to use some CHOLMOD functionality inside an R package > | (specifically, sparse Cholesky updates/downdates). There's an > | CHOLMOD/Eigen interface for that, but unfortunately the header I need is > | not shipped as part of either the Matrix package or the Rcpp package. > | The file is cholmod_modify.h, and it does appear in the src/ directory > | of the Matrix package, but not in the include/ directory. > | > | If I include it by hand I risk version conflicts, because the rest of > | CHOLMOD is provided by the Matrix package via RcppEigen. What's the > | clean way of handling that? Thanks for your input! > > I know "some" (eg rstan) have completemented the BH package with local > headers when BH was missing what they needed (as BH grew, I think we by now > added all they need). So you could just do that, being careful to stick with > the same version. > > Or would Yixuan's RSpectra help? https://cran.r-project.org/package=RSpectra > > 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 -- Yixuan Qiu <yixuan....@cos.name> Department of Statistics, Purdue University _______________________________________________ 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
