Re: [R-pkg-devel] The correct way to put additional DLLs on windows?

2019-07-01 Thread Jeff Newmiller
A) You cannot assume the package code will have write access to the library directories. The user/admin who installs the package may never load the package. B) Downloading binary files for execution without the direct involvement of the user/admin is a security risk. C) Open-source package

[R-pkg-devel] The correct way to put additional DLLs on windows?

2019-07-01 Thread Jialin Ma
Hi everyone, Currently my package has a script downloading additional DLLs into "inst/libs" and being called in "Makevars.win". In this way these DLLs get copied to libs when installing the package and I am able to load them with "library.dynam". However R CMD check gives the following warning.

Re: [R-pkg-devel] "Progress reports" for examples in packages.

2019-07-01 Thread Henrik Bengtsson
FWIW, when running R CMD check mypkg_1.0.tar.gz the example output is captured to the file 'mypkg.Rcheck/mypkg-Ex.Rout', so you could monitor that one for what's going on. /Henrik On Mon, Jul 1, 2019 at 7:00 PM Rolf Turner wrote: > > > I am currently working on a package such that when "R CMD

[R-pkg-devel] "Progress reports" for examples in packages.

2019-07-01 Thread Rolf Turner
I am currently working on a package such that when "R CMD check" is run the procedure seems to disappear into a black hole when it gets to the "* checking examples ..." stage. Strangely, when I run the examples individually, although they take a rather long time, they do not take an