Hi inf0phile,
you can just run the command generated by devtools (including the step that
generates the package.so file) manually on the command line in the src
folder. Just remember to replace -g O2 with -g O0, then you get the
unoptimized shared object that shouldn't make any problems in debugge
On Fri, 12 Jun 2020, rmendelss gmail wrote:
Thank you for these efforts. I imagine it will also make it easier to
eventually have these on CRAN.
Do you have the possibility to try out the affected packages in your
workflows to provide feedback? At the moment, user feedback can help guide
I will do the install sometime over the weekend, and test what I have (mainly
the packages I have that use these). Today is kind of tis up (I mean I can do
the install easily enough, just no time to do any testing).
Thanks,
-Roy
> On Jun 12, 2020, at 7:17 AM, Roger Bivand wrote:
>
> On
Thank you for these efforts. I imagine it will also make it easier to
eventually have these on CRAN.
-Roy
> On Jun 12, 2020, at 7:11 AM, Prof Brian Ripley wrote:
>
> I have put binary packages on CRANextras for lwgeom rgdal rgeos sf built with
> GEOS 3.8.1, GDAL 3.1.0, PROJ 6.3.2.
>
> Inst
I have put binary packages on CRANextras for lwgeom rgdal rgeos sf built
with GEOS 3.8.1, GDAL 3.1.0, PROJ 6.3.2.
Install with (e.g.)
options(repos="https://www.stats.ox.ac.uk/pub/RWin";)
install.packages('rgdal', type = 'binary')
(This needed a development version of the rgdal sources.)
This
* I made a minimal example in order to be reproduced:
library(Rcpp)
library(RcppArmadillo)
RcppArmadillo.package.skeleton()
which create the package anRpackage.
Setting the working directory in this package, I load it by:
library(devtools)
devtools::load_all()
* Then the basic function rcpparma
