Dear Ramon, You should be able to work around this by putting the line
CXX_STD = CXX11 in the package's Makevars file (or Makevars.win for Windows). The idea of putting SystemRequirements: C++ in the DESCRIPTION file was to provide a shortcut for packages that have no Makevars file. From your description, it sounds like this shortcut has the unintended consequence of overriding the user's Makevars file. I will look into it, but you can make this task a lot easier by telling me which packages using C++11 are affected and give me some examples of specific Makevars entries that are ignored. Martyn On Fri, 2015-06-19 at 12:01 +0200, Ramon Diaz-Uriarte wrote: > Dear All, > > Some of my packages use > > SystemRequirements: C++11 > > in the DESCRIPTION. But then .R/Makevars seems to be ignored (e.g., flags > such as -Wall or using clang) in all that concerns C++ (only CXX and > CXXFLAGS are ignored, not CC or CFLAGS). So I keep commenting that line for > normal development and uncommenting it for final checking before release. > > > I vaguely remember reading somewhere this is the way things work, but this > is not what I understand from reading again > http://cran.r-project.org/doc/manuals/r-devel/R-exts.html#Using-C_002b_002b11-code. > > After googling I have not been able to locate anything, and since I guess > it is probably common to use both C++11 and a custom .R/Makevars I think > something is wrong somewhere in my setup. But I have no idea what. I am > using Debian (a mix of testing and unstable), both with stock Debian R and > with custom built Rs. > > > Best, > > > R. > > ----------------------------------------------------------------------- This message and its attachments are strictly confidenti...{{dropped:8}} ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
