Re: [R-pkg-devel] Status of -mmacosx-version-min

2023-12-09 Thread Dirk Eddelbuettel
PS One aspect I didn't mention clearly (my bad) that this does not affect all or even most packages: in most cases the src/Makevars should indeed be as simple as possible. But in _some_ cases we need to cooperate with external libraries and in some of these cases the switch has been seen to be

Re: [R-pkg-devel] Status of -mmacosx-version-min

2023-12-09 Thread Dirk Eddelbuettel
On 10 December 2023 at 17:07, Simon Urbanek wrote: | As discussed here before packages should *never* set -mmacosx-version-min | or similar flags by hand. a) That is in conflict with what was said in the past; we have used an explicit min version of 10.14 for the C++17 we were using then (and

Re: [R-pkg-devel] Status of -mmacosx-version-min

2023-12-09 Thread Simon Urbanek
As discussed here before packages should *never* set -mmacosx-version-min or similar flags by hand. As documented in R-exts 1.2 packages should retrieve compiler flags from R (this includes compiling 3rd party dependencies). Incidentally, older versions of R have included -mmacosx-version-min

[R-pkg-devel] Status of -mmacosx-version-min

2023-12-09 Thread Dirk Eddelbuettel
Last month, I had asked about the setting '-mmacosx-version-min' here. The setting can be used to specify what macOS version one builds for. It is, oddly enough, not mentioned in Writing R Extension but for both r-release and r-devel the R Administration manual states • Current CRAN macOS