[R-pkg-devel] CRAN and CMake

I am thinking of writing an R wrapper for some code that uses cmake. If I include that code under the src directory (ie in src/the_other_project/), am I likely to run into problems with CRAN? Never been down that road and would like to know if this is feasible. I guess I would have to call cmake

Re: [R-pkg-devel] Force namespace prefix for a loaded package function

ion of namespaces in R. I was trying to suggest that it be fixed. (Probably should have sent this to r-devel actually.) THK > Cheers > Joris > On 26 Jun 2016 19:37, "Tim Keitt" <tke...@utexas.edu> wrote: > >> It would be rather nice if we could defin

[R-pkg-devel] Force namespace prefix for a loaded package function

It would be rather nice if we could define functions in our packages that must be called with the namespace prefix. I'd like to do #' @protected (or some such) f = function(...) list(...) in package scope and then library(x) f(1) # fails x::f(1) # succeeds Currently unless

[R-pkg-devel] What to do with build-time-only utility scripts in package

I created a couple of R scripts to assist my package 'configure' script. I put them in the top-level of the package and that gives a check error obviously. So I added them to .Rbuildignore and then the package would not build (at least on Travis CI) saying the script files were not found. That's

Re: [R-pkg-devel] What to do with build-time-only utility scripts in package

http://www.keittlab.org/ On Fri, Apr 15, 2016 at 11:40 AM, Dirk Eddelbuettel <e...@debian.org> wrote: > > On 15 April 2016 at 10:27, Tim Keitt wrote: > | I created a couple of R scripts to assist my package 'configure' script. > I > | put them in the top-level of the p

Re: [R-pkg-devel] AppVeyor with LinkingTo: field

On Mon, Feb 13, 2017 at 9:19 AM, Dirk Eddelbuettel wrote: > [1] http://eddelbuettel.github.io/r-travis/ > This looks useful. I'll have to investigate. THK http://www.keittlab.org/ [[alternative HTML version deleted]] __

Re: [R-pkg-devel] AppVeyor with LinkingTo: field

On Mon, Feb 13, 2017 at 10:36 AM, Dirk Eddelbuettel wrote: > Not true. > It seems to be a work-around for Travis, but as you say not a general packaging requirement. THK http://www.keittlab.org/ [[alternative HTML version deleted]]

Re: [R-pkg-devel] AppVeyor with LinkingTo: field

On Mon, Feb 13, 2017 at 10:31 AM, Tim Keitt <tke...@utexas.edu> wrote: > I am almost there -- only failing on devel in Travis CI. It failing at the > "R CMD build" phase. > > * installing *source* package ‘odeintr’ ... >> ** libs >> I/home/travis/R-bin/l

Re: [R-pkg-devel] Package Submission: issues with R_registerRoutines', 'R_useDynamicSymbols'

On Thu, Apr 13, 2017 at 10:14 AM, Vineetha Warriyar Kodalore Vijayan < vineethawarriyar@ucalgary.ca> wrote: > Can someone help to resolve this issue? I wrote a short R script that will read your RcppExports.cpp and emit the corresponding init.c file. I call it from my configure script, but

[R-pkg-devel] -Wlong-long

Anyone have a fix for: Found the following significant warnings: ../windows/libpq-9.5.2/include/pg_config_ext.h:8:28: warning: ISO C++ 1998 does not support 'long long' [-Wlong-long] ? I tried prepending __extension__ to the definition and adding CXX_STD = CXX11 to Makevars. This is external

[R-pkg-devel] (no subject)

I'm seeing: * checking re-building of vignette outputs ... [3s] WARNING > Error in re-building vignettes: > ... > Quitting from lines 24-60 (strider.Rmd) > Error: processing vignette 'strider.Rmd' failed with diagnostics: > package 'dplyr' is not installed for 'arch = x64' > Execution halted

Re: [R-pkg-devel] Avoid reprocessing Rmd vignette

http://www.keittlab.org/ On Mon, Mar 19, 2018 at 2:18 AM, Iñaki Úcar <i.uca...@gmail.com> wrote: > 2018-03-19 3:57 GMT+01:00 Tim Keitt <tke...@utexas.edu>: > > http://www.keittlab.org/ > > > > On Sun, Mar 18, 2018 at 8:14 PM, Dirk Eddelbuettel <e...@de

Re: [R-pkg-devel] Avoid reprocessing Rmd vignette

an aching desire for an answer does not > ensure that a reasonable answer can be extracted from a given body of data. > ~ John Tukey > > /////// > > <https://www.inbo.be> > > 2018-03-19 8:18 GMT+01:00 Iñaki Úcar <i.uca...@gmail.com>: >

Re: [R-pkg-devel] Avoid reprocessing Rmd vignette

http://www.keittlab.org/ On Mon, Mar 19, 2018 at 6:41 AM, Dirk Eddelbuettel <e...@debian.org> wrote: > > On 18 March 2018 at 21:57, Tim Keitt wrote: > | That's a great idea, however my problem is with building a vignette, not > | running tests, unless they are link

[R-pkg-devel] Travis/appveyor with CXX14/17

I bumped a package to CXX14/17 and it failed on Travis/Appveyor while checking fine locally. I assume I need to request different compilers or something like that. Anyone have a quick recipe for that? THK [[alternative HTML version deleted]]

Re: [R-pkg-devel] Travis/appveyor with CXX14/17

On Fri, Jun 7, 2019 at 11:09 AM Dirk Eddelbuettel wrote: > > On 7 June 2019 at 10:13, Tim Keitt wrote: > | I bumped a package to CXX14/17 and it failed on Travis/Appveyor while > | checking fine locally. I assume I need to request different compilers or > > Correct. > >

Re: [R-pkg-devel] import 'as' from another package

the Imports: statement in your DESCRIPTION file and see if that > >helps. (Maybe I should file a bug report about that error message - it > >confuses me every time.) > > > >On 7/20/20 12:34 PM, Tim Keitt wrote: > >> It works but "check" gives > >&g

Re: [R-pkg-devel] import 'as' from another package

r message - it confuses me > every time.) > On 7/20/20 12:34 PM, Tim Keitt wrote: > > It works but "check" gives > > > checking package dependencies ... ERROR > Namespace dependency not required: ‘methods’ > > THK > > On Mon, Jul 20, 2020 at 1

[R-pkg-devel] Vignette depends on BH

I have an RMarkdown vignette in a package that uses Rcpp and depends on BH. I added BH to the Suggests list. It is still generating warnings about BH. What is the correct way to handle this? Thanks. THK [[alternative HTML version deleted]] __

[R-pkg-devel] import 'as' from another package

I have if (!inherits(x, "RasterLayer")) x <- as(x, "RasterLayer") in a package and its not finding the coerce definition from the raster package. I know I need to add an @import roxygen2 directive of some kind, but I'm not sure the correct syntax. My first try generated a warning that it was

Re: [R-pkg-devel] import 'as' from another package

It works but "check" gives > checking package dependencies ... ERROR Namespace dependency not required: ‘methods’ THK On Mon, Jul 20, 2020 at 11:24 AM Ben Bolker wrote: > @importFrom methods as > > ? > > On 7/20/20 12:06 PM, Tim Keitt wrote: > >

Re: [R-pkg-devel] C++17

Kind of figured that out looking around on github. I added a config (borrowed from one of your repos) to test for CXX17. I'm not sure its quite working for me yet but I will figure it out. A couple of questions: 1) I had C++17 in the system requirements in the description file but might remove it

Re: [R-pkg-devel] Ongoing CXX17 woes

On Fri, Aug 6, 2021 at 4:05 PM Ivan Krylov wrote: > On Fri, 6 Aug 2021 15:51:37 -0500 > Tim Keitt wrote: > > > CXX17=`${R_HOME}/bin/R CMD config --all | awk '{print $1}' | grep \ > > "^CXX17$"` > > This seems to output "CXX17" on a machine with

Re: [R-pkg-devel] Ongoing CXX17 woes

On Fri, Aug 6, 2021 at 4:22 PM Tim Keitt wrote: > > > On Fri, Aug 6, 2021 at 4:05 PM Ivan Krylov wrote: > >> On Fri, 6 Aug 2021 15:51:37 -0500 >> Tim Keitt wrote: >> >> > CXX17=`${R_HOME}/bin/R CMD config --all | awk '{print $1}' | grep \ >> &

Re: [R-pkg-devel] Ongoing CXX17 woes

Fixed. Thanks. THK On Fri, Aug 6, 2021 at 4:33 PM Tim Keitt wrote: > > > On Fri, Aug 6, 2021 at 4:22 PM Tim Keitt wrote: > >> >> >> On Fri, Aug 6, 2021 at 4:05 PM Ivan Krylov wrote: >> >>> On Fri, 6 Aug 2021 15:51:37 -0500 >>> Tim Kei

[R-pkg-devel] windows and configure scripts

As configure is not run on windows, but according to the writing extensions docs you can run commands in Makevars, is that not preferable for simple cases? What shell is active in Makevars? Is it "/bin/sh" or is make the interpreter here? Can we use $(shell ...cmd...) in Makevars on windows? I'm

[R-pkg-devel] Ongoing CXX17 woes

Hi Folks, I have a package that compiles fine under C++11 but it throws an "Error: C++17 standard requested but CXX17 is not defined" error when checking under Solaris. My configure looks like: #!/bin/sh # Borrowed from https://github.com/eddelbuettel/rcppsimdjson/blob/master/configure :

[R-pkg-devel] C++17

Hi Folks, It appears that c++17 is not supported on all platforms used by CRAN. Is there a workaround? I have CXX_STD = CXX17 in the package Makevars file, but see https://cran.r-project.org/web/checks/check_results_kdtools.html I assume if CXX17 is not defined, it is not available on that