[Rcpp-devel] RcppEigen needs 1GB memory to compile
Kasper Daniel Hansen
kasperdanielhansen at gmail.com
Tue Dec 3 14:36:59 CET 2013
Could I suggest taking all of this example code and move it into something
like RcppExample or RcppTesting, which RcppXX could suggest and use for
testing. This will have the benefit of having a testing package that also
does the outside package linking. If this is done as a split of the basic
package into a core package and a testing package, I don't see why this
would be a problem with JSS. This would essentially just be refactoring of
On Tue, Dec 3, 2013 at 7:25 AM, Dirk Eddelbuettel <edd at debian.org> wrote:
> On 3 December 2013 at 12:51, Romain Francois wrote:
> | Le 03/12/2013 12:38, Dirk Eddelbuettel a écrit :
> | > And headers-only wasn't an option when fastLm() was first set up.
> | Of course it was. We could definitely have RcppEigen header only even
> | with CRAN not header only Rcpp.
> Point taken but the first fastLm() verson was written against the GSL
> even RcppGSL existed :) That very much required linking.
> | Those are two orthogonal things.
> | > Might be time to improve on things after the 0.10.7 / 0.11.0 release.
> | Releasing a new version of packages that depend on Rcpp after the header
> | only version is released is a cheap and good way to deal with
> | compatibility issues, e.g. deal with RcppEigen expecting libRcpp.
> True too.
> Doug, let us know your thoughts. JSS's preference is clear, but we have
> reasons suggesting a decoupling would be beneficial. In any event,
> RcppArmadillo is of course not bound by JSS.
> Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com
> Rcpp-devel mailing list
> Rcpp-devel at lists.r-forge.r-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Rcpp-devel