Hi Matteo, On 1 June 2014 at 15:37, Matteo Fasiolo wrote: | Hi Dirk, | | thanks for the fix. Both the package created using | RcppArmadillo.package.skeleton() and my original | package work on Windows when the new flag is added and the new RcppArmadillo | version is used.
Perfect! | I was a bit surprised to see that they work also on win-builder, which (I | guess) links against the old RcppArmadillo version. Maybe it was a side-effect -- I tossed versions up there for testing -- but you'd think they'd run in a separate environment. I have submitted this version to CRAN, unless something comes up it should be the release version by tomorrow. Thanks, Dirk | Thanks, | | Matteo | | | On Sat, May 31, 2014 at 8:16 PM, Dirk Eddelbuettel <e...@debian.org> wrote: | | | Matteo, | | Try updating RcppArmadillo from the GitHub repo. It now contains a release | candidate for 0.4.300.7.0, based on an updated Armadillo 4.300.7 in which | Conrad added | #define ARMA_DONT_USE_CXX11 | which you should set, either via a -DARMA_DONT_USE_CXX11 to, say, | PKG_CXXFLAGS | in src/Makevars (or just src/Makevars.win), or in your code before you | #include <RcppArmadillo.h> | | With this, and even though you turn on C++11 for _your code_ it will not | use | C++11 in Armadillo avoiding the issue experienced on Windows where g++ | 4.6.2 | is not new enough for some of the idioms used inside Armadillo. | | But as Armadillo is so neatly #ifdef'ed you should still be able to set up | your package and proceed. | | Give it a spin and let us know how it goes. I plan to ship this version of | RcppArmadillo to CRAN in the next few days. | | Cheers, Dirk | | -- | Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com | | -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com _______________________________________________ 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