[R-pkg-devel] "Progress reports" for examples in packages.
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 "endless" amount of time, so I am
puzzled. I would like to be able to isolate where the hang-up is
occurring so that I can rectify the problem.
I guess I could, successively, wrap all but one of the examples in
\dontrun{} and see what happens in each case. But this is rather
tedious. Is there any to get some diagnostic output as to, e.g. which
example is being checked at the given moment? Doing R CMD check --help
does not reveal any useful looking options.
Thanks for any tips.
cheers,
Rolf Turner
--
Honorary Research Fellow
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] "Progress reports" for examples in packages.
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 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 "endless" amount of time, so I am
> puzzled. I would like to be able to isolate where the hang-up is
> occurring so that I can rectify the problem.
>
> I guess I could, successively, wrap all but one of the examples in
> \dontrun{} and see what happens in each case. But this is rather
> tedious. Is there any to get some diagnostic output as to, e.g. which
> example is being checked at the given moment? Doing R CMD check --help
> does not reveal any useful looking options.
>
> Thanks for any tips.
>
> cheers,
>
> Rolf Turner
>
> --
> Honorary Research Fellow
> Department of Statistics
> University of Auckland
> Phone: +64-9-373-7599 ext. 88276
>
> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] The correct way to put additional DLLs on windows?
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. * checking package subdirectories ... WARNING Found the following non-empty subdirectories of 'inst' also used by R: inst/libs It is recommended not to interfere with package subdirectories used by R. I was wondering what would be the best practice for my case, or I am safe to ignore this warning (suppose I am planing for a CRAN submission). I know many packages will download static library and link them at compile time. But I haven't see any example with additional DLL files. Thanks. Jialin Ma __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] The correct way to put additional DLLs on windows?
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 license means the source code is part of the package. Downloading binaries later fails this requirement. On July 1, 2019 10:03:07 PM PDT, Jialin Ma wrote: >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. > > * checking package subdirectories ... WARNING > Found the following non-empty subdirectories of 'inst' also used by R: >inst/libs > It is recommended not to interfere with package subdirectories used by > R. > >I was wondering what would be the best practice for my case, or I am >safe >to ignore this warning (suppose I am planing for a CRAN submission). > >I know many packages will download static library and link them at >compile >time. But I haven't see any example with additional DLL files. > >Thanks. >Jialin Ma > >__ >R-package-devel@r-project.org mailing list >https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sent from my phone. Please excuse my brevity. __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
