Thanks, that helped. However, a user with gcc < 4.7 will still get cryptic
errors.
I had another idea: I created a file src/AAA_check_cpp11.cpp, checking the
preprocessor directive “__cplusplus”, see
https://github.com/mnwright/ranger/blob/master/ranger-r-package/ranger/src/AAA_check_cpp11.cpp
On 16 November 2015 at 16:45, Marvin Wright wrote:
| Thanks, that helped. However, a user with gcc < 4.7 will still get cryptic
| errors.
|
| I had another idea: I created a file src/AAA_check_cpp11.cpp, checking the
| preprocessor directive “__cplusplus”, see https://github.com/mnwright/ranger/
On 16 November 2015 at 13:07, Marvin Wright wrote:
| I would like to check for C++11 support in a package. The package requires
gcc >= 4.7 or clang >= 3.0. Windows is handled differently in Makevars.win. I
tried two approaches in Makevars so far, but both give warnings in CRAN checks.
|
| Appr
On 16/11/2015 7:07 AM, Marvin Wright wrote:
Dear all,
I would like to check for C++11 support in a package. The package requires gcc >=
4.7 or clang >= 3.0. Windows is handled differently in Makevars.win. I tried two
approaches in Makevars so far, but both give warnings in CRAN checks.
Approa
Dear all,
I would like to check for C++11 support in a package. The package requires gcc
>= 4.7 or clang >= 3.0. Windows is handled differently in Makevars.win. I tried
two approaches in Makevars so far, but both give warnings in CRAN checks.
Approach 1:
## Check for gcc >= 4.7
ifeq ($(shell
