I think that C++11 isn't a requirement of RcppArmadillo, it's an option
that is used if available. (Assuming you are using the CRAN version,
not an experimental/devel version.) A user of the header file can include
#define ARMA_USE_CXX11
which would make it a system requirement of whatever package did that,
even though it isn't a system requirement for RcppArmadillo.
But I could be wrong about this...
Duncan Murdoch
On 30/11/2020 11:06 a.m., Mark Clements wrote:
[Apologies for cross-posting]
A colleague uses a package I maintain (rstpm2) as a dependency in their
package (rsimsum) with testing using GitHub Actions. They found that
testing failed against R versions 3.3, 3.4 and 3.5 because recent
versions of RcppArmadillo (which is a dependency in rstpm2) require
C++11. As a dependency diagram:
rsimsum --> rstpm2 --> RcppArmadillo
Should I update rstpm2 to include "CXX_STD = CXX11" in the Makevars and
Makevars.win files and add "SystemRequirements: C++11" to the
DESCRIPTION, or is there a simple way in GitHub Actions to use C++11 for
older versions of R?
Moreover, as a principle, should a package need to change the Makevars
and DESCRIPTION files to suit the most recent updates of their
dependencies? I would have thought that such a need would break many
packages.
Sincerely, Mark.
När du skickar e-post till Karolinska Institutet (KI) innebär detta att KI kommer att
behandla dina personuppgifter. Här finns information om hur KI behandlar
personuppgifter<https://ki.se/medarbetare/integritetsskyddspolicy>.
Sending email to Karolinska Institutet (KI) will result in KI processing your
personal data. You can read more about KI’s processing of personal data
here<https://ki.se/en/staff/data-protection-policy>.
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
