Folks:
What is the policy on adding Windows executables to an R package? My gdalUtils
package could REALLY use this ability (right now it requires users to manually
install GDAL which can cause headaches for folks). Related: what about
linux/mac executables?
Are there reasonable tutorials on
Awesome -- the key was the "RD", so for me:
docker run -v /Users:/Users --rm -ti rocker/r-devel RD
(where, on a Mac, I was binding my Mac's /Users to the Docker's /Users
directory)
Thanks, all!
--j
On Wed, Jan 15, 2020 at 2:53 PM Dirk Eddelbuettel
mailto:e...@debian.org>> wrote:
Jonathan,
One of the issues I'm running into is that it seems every time there's a Mac
update something gets broken with regards to compilers, making it incredibly
challenging to get the development install of R working with Rcpp (which is a
requirement for the packages I need to use to check my packages)
Folks:
My package gdalUtils is a wrapper for a set of binaries on disk (the GDAL
Utilities) -- these have about as many places to install as there are people
installing it, and the system environment variables aren't always much help
(they aren't always set) for locating them. My package is tr
