Hi Dirk,
On Fri, 19-06-2015, at 15:04, Dirk Eddelbuettel wrote:
> Hi Ramon,
>
> On 19 June 2015 at 12:01, Ramon Diaz-Uriarte wrote:
> | Some of my packages use
> |
> | SystemRequirements: C++11
> |
> | in the DESCRIPTION. But then .R/Makevars seems to be ignored (e.g., flags
> | such as -Wal
Dear Martyn,
On Fri, 19-06-2015, at 14:59, Martyn Plummer wrote:
> 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 fil
Hi Ramon,
On 19 June 2015 at 12:01, Ramon Diaz-Uriarte wrote:
| 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
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
de
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 developmen
