Re: [R-pkg-devel] CRAN incoming feasibility Error

On 9 June 2015 at 10:24, Seth Wenchel wrote: | Hi All, | | I'm running into an error with R CMD check --as-cran on R 3.2.0 for | windows. Obviously i've tried googling but i haven't found this specific | issue. I was wondering if it is because of my company's network settings. | FWIW, it makes

Re: [R-pkg-devel] CRAN incoming feasibility Error

...Error in utils::contrib.url(urls, | source) : |   trying to use CRAN without setting a mirror | Execution halted | | | | On Tue, Jun 9, 2015 at 11:27 AM, Dirk Eddelbuettel e...@debian.org wrote: | | | On 9 June 2015 at 10:24, Seth Wenchel wrote: | | Hi All, | | | | I'm running

Re: [R-pkg-devel] how to skip tests on CRAN but NOT on travis-ci?

Hi Jenny, And a warm welcome here. I hope you enjoy this place and its ability to form questions (and answers) beyond the 140 char limit posed elsewhere. :-) On 21 June 2015 at 07:46, Jennifer Bryan wrote: | I hope this is an appropriate to place to ask this. My question involves add-on tools

Re: [R-pkg-devel] license for package

On 29 May 2015 at 08:23, Drew Schmidt wrote: | | On 05/29/2015 07:56 AM, Dirk Eddelbuettel wrote: | Lastly, in many cases [eg when you link against libR], the aggregate work | will be under GPL (= 2) anyway. But within the aggregate work the code | you added can be under a different license

Re: [R-pkg-devel] how to make r-release-osx-x86_64-mavericks machine support rgl 3D plots

On 12 August 2015 at 09:07, Duncan Murdoch wrote: | On 12/08/2015 8:26 AM, Dirk Eddelbuettel wrote: | I frequently tests against all reverse dependencies against some of my | packages, ie Rcpp, RcppArmadillo, ... and packages using rgl generally fail | during these tests. [...] | A while

Re: [R-pkg-devel] [[openmx-dev]] Re: openmp

On 24 August 2015 at 11:02, Joshua N Pritikin wrote: | Currently, we have a configure script for package OpenMx that only | enables openmp if gcc is the compiler (OS X only). Nice to hear that | openmp is supported on Windows. Interesting that you opt to ignore OpenMP support on the platform

Re: [R-pkg-devel] openmp

On 24 August 2015 at 09:14, Joshua N Pritikin wrote: | On Sun, Aug 23, 2015 at 08:01:08AM +0200, Mark van der Loo wrote: | Afaik, openmp is available on windows. According to writing R | extensions: | | There is nothing to say what version of OpenMP is supported: version | 3.0

Re: [R-pkg-devel] .tar vs. binary builds

On 3 August 2015 at 19:32, Glenn Schultz wrote: | Got it thanks - I want to achieve maximum exposure and transparency So provide access to the source code, as well as to installable binaries. That is a recipe many of us have used for years if not decades. Dirk -- http://dirk.eddelbuettel.com

Re: [R-pkg-devel] R CMD build with configure-args

Besides what Duncan said, relying on user to supply arguments is pretty bad as it more or less guarantees _any_ automated test will not succeed (for lack of involvement of the sage user). Writing configure scripts feels like yet another painful step, but it really is not that hard if you know a

Re: [R-pkg-devel] CRAN submission which requires third party software?

On 11 August 2015 at 11:49, Charles Determan wrote: | I am beginning to reach the completion of a new package I would like to | submit to CRAN. However, there are a few aspects of it that I would like | some guidance prior to submitting. | | 1. It requires some third party software (i.e. an

Re: [R-pkg-devel] Listing a package in Imports: when it's used outside of R directory

On 14 August 2015 at 23:36, Dean Attali wrote: | Since the Shiny app is an integral part of the package, and the app uses the | DT package, I want to place DT under the Imports: field. But then I ran | into the above error. The code checkers are heuristics. They cannot get everything right. If

Re: [R-pkg-devel] how to make r-release-osx-x86_64-mavericks machine support rgl 3D plots

Hi Søren, On 12 August 2015 at 11:44, Søren Havelund Welling wrote: | Dear all | | I have a package(forestFloor) which produces an test error when built on the r-release-osx-x86_64-mavericks machine. I'm quite sure it's due to Xquartz(or similar) graphical resources have to be installed for

Re: [R-pkg-devel] Best practices for vignettes

On 27 July 2015 at 12:50, Henrik Bengtsson wrote: | Have a look at tools::buildVignette() - it builds a vignette the same | way as R CMD build does it. It's a good start for troubleshooting. Seconded. | /Henrik | | On Mon, Jul 27, 2015 at 1:31 AM, Lenth, Russell V | russell-le...@uiowa.edu

Re: [R-pkg-devel] Best practices for vignettes

On 26 July 2015 at 18:42, Lenth, Russell V wrote: | What's the best way to manage vignettes? All the young ones will of course tell you to use Markdown :) I still use Sweave / LaTeX as well, along with a custom driver: highlight, as we once figured out how to make it create pretty shaded boxen

Re: [R-pkg-devel] Note about No repository set, so cyclic dependency check skipped

On 20 July 2015 at 08:53, Martyn Plummer wrote: | On Mon, 2015-07-20 at 07:36 +0200, Antonio José Saez Castillo wrote: | When checking a package I am getting | | * checking package dependencies ... NOTE | No repository set, so cyclic dependency check skipped | | This is an old source

Re: [R-pkg-devel] Setting up R-devel in Linux Mint 17.1 64-bit

On 20 July 2015 at 18:05, MAURICIO ZAMBRANO BIGIARINI wrote: | Dear list, | | I'm trying to set up the development version of R (R-devel ) for | testing some packages before submitting them to CRAN. I'm using Linux | Mint 17.1 64-bit, which is an Ubuntu-based distro. | | I followed the advice

Re: [R-pkg-devel] Setting up R-devel in Linux Mint 17.1 64-bit

On 20 July 2015 at 18:56, MAURICIO ZAMBRANO BIGIARINI wrote: | how can I be sure that I I enabled the shared library support ? edd@max:~/svn/r-devel$ ./configure --help | grep enable-R-sh --enable-R-shlibbuild the shared/dynamic library 'libR' [no] edd@max:~/svn/r-devel$ Make sure you

Re: [R-pkg-devel] invalid 'envir' argument note from R-devel

On 14 July 2015 at 08:06, Duncan Murdoch wrote: | It looks like a bug in codetools. It handles a number of functions | specially; data() is one, binomial() is another. I think there are some | implicit assumptions in it that stats and utils are on the search path, | but in the new tests, they

Re: [R-pkg-devel] configure.win for multiple architectures

On 12 November 2015 at 07:17, Charles Determan wrote: | I am trying to compile a package (using Rcpp) where the libraries needed | for linking (assigned with PKG_LIBS) are in different locations depending | upon the architecture (32 or 64 bit). [...] Maybe you can borrow this short piece from

Re: [R-pkg-devel] Problem (with complex.h?) under Microsoft Windows

On 13 November 2015 at 20:24, Roebuck,Paul L wrote: | Too bad you couldn't just use C++ std::complex, but that's a no-go if your function needs C linkage. | | | suggests MS-specific topic, but answers explain

Re: [R-pkg-devel] Checking for C++11

On 16 November 2015 at 16:45, Marvin Wright wrote: | Thanks, that helped. However, a user with gcc < 4.7 will still get cryptic | errors. | | I had another idea: I created a file src/AAA_check_cpp11.cpp, checking the | preprocessor directive “__cplusplus”, see

Re: [R-pkg-devel] Checking for C++11

On 16 November 2015 at 13:07, Marvin Wright wrote: | I would like to check for C++11 support in a package. The package requires gcc >= 4.7 or clang >= 3.0. Windows is handled differently in Makevars.win. I tried two approaches in Makevars so far, but both give warnings in CRAN checks. | |

Re: [R-pkg-devel] Using the correct R binary in configure script

On 26 September 2015 at 10:27, Jack Wasey wrote: | Having just read section 1.2 in Writing R extensions, a fragment of a | configure script is offered in order to determine the correct compiler | options. It starts by setting R_HOME with: | | : ${R_HOME=`R RHOME`} | | | `R` is called, even if,

Re: [R-pkg-devel] Using the correct R binary in configure script

On 26 September 2015 at 12:32, Jack Wasey wrote: | Dirk, thanks for detailed reply. I may not have explained myself well enough. I | think the problem is that the recommended configure command assumes 'R', not If and only if R_HOME is unset. But witness: edd@max:~$ R --slave -e

Re: [R-pkg-devel] Using the correct R binary in configure script

On 26 September 2015 at 22:29, peter dalgaard wrote: | | > On 26 Sep 2015, at 17:43 , Dirk Eddelbuettel <e...@debian.org> wrote: | > | > R_HOME is set to the result of the command R RHOME if and only it is unset. | > | > And it usually is unset. | | Did you actually

Re: [R-pkg-devel] Multi-threaded C with R's RNG

On 27 November 2015 at 19:48, Guillaume Chapron wrote: | Has anyone written a package with a C code that uses R's RNG but in a multi-threaded way (e.g. to parallelize Monte Carlo simulations)? I do not have the knowledge to figure out myself how to solved this and would need to see an example.

Re: [R-pkg-devel] compileAttributes() and 'using namespace' directives

Georgi, Wrong list? Try rcpp-devel for Rcpp question. On 8 December 2015 at 14:37, Georgi Boshnakov wrote: | Hi, | | With a collaborator we are working on a package which uses Rcpp and RcppArmadillo. Our *.cpp files start with something like | | // [[Rcpp::depends(RcppArmadillo)]] Use

Re: [R-pkg-devel] Run-away R CMD check ?

On 12 December 2015 at 12:10, Dirk Eddelbuettel wrote: | | On 12 December 2015 at 18:57, Uwe Ligges wrote: | | CRAN has different approaches. | | | | Under Windows, I typically have an R process that controls the check | | process and writes out the process id and timestamp and then starts R

Re: [R-pkg-devel] --as-cran URL check

Kurt, I am emailing you directly in extension of a thread from r-package-devel for which you can see the full (short, five posts) history at http://thread.gmane.org/gmane.comp.lang.r.packages.devel/581 Not long ago I had the idea of defining macros for GitHub pull requests and issue tickets.

Re: [R-pkg-devel] Problem (with complex.h?) under Microsoft Windows

On 3 January 2016 at 09:48, Pierre Lafaye de Micheaux wrote: | Thank you for your comments. | | It is indeed the RcppFaddeeva package. I had also tried to put | RcppFaddeeva on the LinkingTo line with no success. | But I will try to ask on the Rcpp mailing list. The RcppFaddeeva package does

Re: [R-pkg-devel] Calls to exported dplyr functions from DBI/dplyr backend

On 9 January 2016 at 12:20, Imanuel Costigan wrote: | * I import all these dplyr functions into my package (or call with ::) and make CRAN errors go away This is emerging as a recommended idiom for packages. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: [R-pkg-devel] --as-cran URL check

On 18 December 2015 at 07:14, Dirk Eddelbuettel wrote: | | Kurt, | | I am emailing you directly in extension of a thread from r-package-devel for | which you can see the full (short, five posts) history at | http://thread.gmane.org/gmane.comp.lang.r.packages.devel/581 | | Not long ago I had

Re: [R-pkg-devel] modification of warning messages

On 22 June 2016 at 18:29, Hadley Wickham wrote: | Try warningcall(R_NilValue, "message") Nice one: R> cppFunction("void foo(std::string txt) { Rf_warningcall(R_NilValue, txt.c_str()); }") R> foo("magic!") Warning message: magic! R> Dirk -- http://dirk.eddelbuettel.com |

Re: [R-pkg-devel] How to link executables for non-R-users?

On 16 June 2016 at 15:56, Michael Cysouw wrote: | I really like the possibility of projects like docopt , providing a bash interface to R functionality. IMHO this is a great way to allow non-R-users to include R functionality in their workflows. There is a docopt package for

Re: [R-pkg-devel] compiling and executing binaries while testing

Dear 'code M', We all participate here with 'vizors up' and clear view of each other's identities. Please consider doing the same. On 3 February 2016 at 09:37, code M wrote: | hi, i am sorry if this has been asked already, | but i could not find an answer. | | in short: am i allowed to

Re: [R-pkg-devel] Previous messageNext messageBack to messages The following files should probably not be installed‏

On 20 January 2016 at 14:10, Daniel Marcelino wrote: | Hi, I used to have some pictures in ‘inst/doc’ for decoration of the README.MD text, most for the Github repository. | I was able to build the package without any NOTE on this, but since I updated to R 3.2.3 and created a vignette folder

Re: [R-pkg-devel] R CMD check yielding different results for me than CRAN reviewer

On 26 January 2016 at 14:03, Adah Zhang wrote: | I am running R CMD check (and also with the --as-cran flag), which results | in all OK's in my 00check.log. However, after submitting the package, the | CRAN reviewer tells me of a warning/error regarding one of my examples | (which is easily

Re: [R-pkg-devel] R CMD check yielding different results for me than CRAN reviewer

one ftp away: | >> On 26 Jan 2016, at 20:54, Dirk Eddelbuettel <e...@debian.org> wrote: | >> -- thanks to Uwe you have r-release and r-devel on Windows just one ftp | >> submission away Dirk -- http://dirk.eddelbuettel.com | @eddelb

Re: [R-pkg-devel] R CMD check yielding different results for me than CRAN reviewer

evel digest..." | > | > | > Today's Topics: | > | >1. R CMD check yielding different results for me thanCRAN | > reviewer (Adah Zhang) | >2. Re: R CMD check yielding different results for me than CRAN | > reviewer (Ben Bolker) | >3.

Re: [R-pkg-devel] Data-generating scripts in R packages

Kevin, The inst/ directory gives a good handle to pass arbitrary directory layouts of your choosing through. You just need to avoid inst/data as it would clash with an existing data/ directory. I think I have seen inst/rawData inst/extData# as in 'external data' and

Re: [R-pkg-devel] Scripts to generate data objects

On 31 March 2016 at 14:14, Kirill Müller wrote: | The devtools::use_data_raw() function But the question was about the best way ;-) Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org __ R-package-devel@r-project.org mailing

Re: [R-pkg-devel] Submitting CRAN packages with hard-to-meet dependencies

My $0.02: On 18 April 2016 at 20:23, boB Rudis wrote: | I would hope CRAN would let this in with some validation (even to the | point of it possibly adding a new field to DESCRIPTION). It may never | run on Slolaris or Plan 9, and I - who now runs a CRAN mirror in the | hopes to eventually have

Re: [R-pkg-devel] Submitting CRAN packages with hard-to-meet dependencies

On 18 April 2016 at 20:48, boB Rudis wrote: | So, how do we create a solid alternative to CRAN? github drat wld have | been impossible at my previous gig (for good reasons). Is it time to | try to get rOpenSci to be a legit CRAN alternative? Add enough process | around it to support things like

Re: [R-pkg-devel] Handling Not-Always-Needed Dependencies?

See eg https://www.debian.org/doc/debian-policy/ch-relationships.html We have other big fish to fry. Eg many packages have LinkingTo: BH (as Boost headers are indeed awesome) but this 120 mb (!!) payload is needed _once_ during package compilation / installation and never again afterwards. So

Re: [R-pkg-devel] Handling Not-Always-Needed Dependencies?

On 2 August 2016 at 11:36, Joshua Ulrich wrote: | Maybe I'm missing something, but isn't that the point of calling | requireNamespace()? For example: | if (requireNamespace("suggestedPackage")) | stop("suggestedPackage required but not installed") | | That doesn't seem like a heavy burden for

Re: [R-pkg-devel] Handling Not-Always-Needed Dependencies?

On 2 August 2016 at 13:12, Duncan Murdoch wrote: | On 02/08/2016 1:01 PM, Dirk Eddelbuettel wrote: | > | > On 2 August 2016 at 11:36, Joshua Ulrich wrote: | > | Maybe I'm missing something, but isn't that the point of calling | > | requireNamespace()? For example: | > | if (r

Re: [R-pkg-devel] Handling Not-Always-Needed Dependencies?

On 3 August 2016 at 16:00, Uwe Ligges wrote: | On 03.08.2016 14:24, Dirk Eddelbuettel wrote: | > Then again, users of TravisCI know that just toggling | > | > _R_CHECK_FORCE_SUGGESTS_=FALSE | | I was travelling, hence a delayed response: | | Why users of TravisCI? It is documented in t

Re: [R-pkg-devel] Pkgs with ToS violations

On 3 August 2016 at 22:26, Bob Rudis wrote: | I came across https://cran.rstudio.com/web/packages/boxoffice/index.html | in CRAN today and while I don't expect CRAN to be a legal authority, | should there not be some kind of policy for excluding R packages that | deliberately violate (data) site

Re: [R-pkg-devel] Handling Not-Always-Needed Dependencies?

On 3 August 2016 at 13:44, Duncan Murdoch wrote: | On 03/08/2016 11:17 AM, Dirk Eddelbuettel wrote: | > | > On 3 August 2016 at 16:21, Uwe Ligges wrote: | > | | > | | > | On 03.08.2016 16:14, Dirk Eddelbuettel wrote: | > | > | > | > On 3 August 2016

Re: [R-pkg-devel] openMP/reduction statement causes build crash on travis-ci

On 3 August 2016 at 08:13, Mark van der Loo wrote: | Dear pkg developers, | | | I'm working on a package using C code and openMP. The package builds and | tests fine on my own machine[1] and also on r-hub[2]. However on travis-ci | the build crashes[3] with the following message (plus a few

Re: [R-pkg-devel] [Learning] the secret of Win[dows C-backed packages]

h nu-get but add-ons failed before | On Sat, Aug 13, 2016 at 13:09 Dirk Eddelbuettel <e...@debian.org> wrote: | | | I don't think there is a good "generally applicable" solution.  We have a | bunch of hacks. Below are three quickly picked examples from packages of |

Re: [R-pkg-devel] Source code of an existing package

On 10 August 2016 at 22:14, Ben Bolker wrote: | | Easiest way: | | library(boot) | boot.ci | | Alternatively, go to https://cran.r-project.org/package=boot , | download the tarball, unpack it, and look around in the R/ directory. Uwe Ligges wrote an 'R Help Desk' piece in R News about

Re: [R-pkg-devel] Accessing R's linked PCRE library from inside a package

On 10 August 2016 at 19:35, Oliver Keyes wrote: | Neat; thanks Dirk! Will be interesting to see if I can get that finnagled on | Windows when I get back to Boston. Come to think about it, there is a bit of good fortune in my use as I - don't need to bother with include flags as pcre as a

Re: [R-pkg-devel] Accessing R's linked PCRE library from inside a package

On 10 August 2016 at 18:15, Oliver Keyes wrote: | I'm trying to incorporate PCRE-compliant regular expressions into C | code in an R package. | | >From digging around in R's source code, it appears that R (pretty | much?) guarantees the presence of either a system-level PCRE library, | or an

Re: [R-pkg-devel] Is S3 class registration essential for CRAN?

On 12 July 2016 at 17:47, S Ellison wrote: | A short question: How necessary is explicit S3 class registration for CRAN submission? | R-forge's check is giving me a note on this for a handful of methods in a package, and I'm unclear whether it is something that _needs_ to be fixed for CRAN

Re: [R-pkg-devel] Handling Not-Always-Needed Dependencies?

On 2 August 2016 at 16:07, Duncan Murdoch wrote: | On 02/08/2016 1:41 PM, Dirk Eddelbuettel wrote: | > | > On 2 August 2016 at 13:12, Duncan Murdoch wrote: | > | On 02/08/2016 1:01 PM, Dirk Eddelbuettel wrote: | > | > | > | > On 2 August 2016 at 11:36, Joshua Ulrich wrote

Re: [R-pkg-devel] Fwd: R-package-devel@R-project.org: RANDR

On 24 January 2017 at 15:11, Cathy Lee Gierke wrote: | I'm cleaning up the problems in my build, but there are a few I do not | understand, like this one. What is this telling me? | | | | * checking for unstated dependencies in examples ...Warning in grep("^Xlib: |

Re: [R-pkg-devel] Multiple architectures on Windows

we fetch from Bloomberg (in configure.win) but unpack as needed: - ## -*- mode: Makefile; tab-width: 8 -*- ## ## Makefile.win -- Windows build system ## ## Copyright (C) 2015 Whit Armstrong and Dirk Eddelbuettel ## ## This file is part of Rblpapi ## ##

Re: [R-pkg-devel] Handling Not-Always-Needed Dependencies? - Part 2

On 4 August 2016 at 11:46, Paul Gilbert wrote: | If my package has a test that needs another package, but that package is | not needed in the /R code of my package, then I indicate it as | "Suggests", not as "Depends" nor as "Imports". If that package is not | available when I run R CMD

Re: [R-pkg-devel] Handling Not-Always-Needed Dependencies?

On 2 August 2016 at 19:45, Duncan Murdoch wrote: | Why not put together code to implement your idea, and see how big the | problem would be to phase it in, by seeing how many packages fail under it? Ahh, the old 'put-up-or-shut-up' gambit, very nice. Big fan of that myself. I have been sitting

Re: [R-pkg-devel] Wrapping a third-party c++ library

On 23 August 2016 at 11:13, Sean Davis wrote: | Thanks for the reply and feedback, Dirk. Pleasure! | > On Aug 23, 2016, at 10:59 AM, Dirk Eddelbuettel <e...@debian.org> wrote: | > Local shared libraries is hard(est). I would not start there. I missed one line here: "Hard(est)

Re: [R-pkg-devel] Wrapping a third-party c++ library

hi Sean, On 23 August 2016 at 09:13, Sean Davis wrote: | I am trying to wrap a third-party toolkit that provides a C++ API. The code is open source and includes a license that allows me to include it directly in an R package. Right now, I am happy if I can get ANY build (linux, windows, or

Re: [R-pkg-devel] robust download function in R (similar to wget)?

On 25 August 2016 at 08:24, Joshua Ulrich wrote: | Try downloader: https://cran.r-project.org/package=downloader Also, if you really want wget / know how to parameterise wget you can ... just depend on _wget itself_ which you can a) test for via Sys.which("wget") b) select as an option for

Re: [R-pkg-devel] Validate CRAN package using a linked library

On 14 September 2016 at 12:52, Dorel, Mathurin wrote: | I developed a package using the symbolic calculus C library ginac (http://www.ginac.de/). | I want to submit

Re: [R-pkg-devel] C++11: which is currently the most portable option?

On 30 September 2016 at 09:16, Charles Determan wrote: | I believe you could just put the following in your DESCRIPTION file so the | R version takes care of the C++11 flag. | | SystemRequirements: C++11 This is _one_ of _two_ equivalent choices, the other (which is my preference) is to add

Re: [R-pkg-devel] Relicense to GPL-3?

On 6 November 2016 at 02:28, Lenth, Russell V wrote: | I received an email from a user telling me that another package that | depends on my package is licensed GPL(>=3), whereas mine is licensed GPL-2; | and that therefore, the other package is in violation of its GPL-3 license. That is

Re: [R-pkg-devel] Relicense to GPL-3?

On 6 November 2016 at 09:11, Lenth, Russell V wrote: | A correction and clarification... | | It is MY package's GPL-2 license that is being violated by the other package -- not its GPL-3 license. No, let's stop here. I don't think that is legally (or conceptually !!) possible. Your code, your

Re: [R-pkg-devel] Relicense to GPL-3?

On 6 November 2016 at 16:53, Lenth, Russell V wrote: | Permission of "all other copyright holders" as in developers of all packages that depend on 'foo'? Please do have a look at the two FAQs I referenced before: https://www.gnu.org/licenses/gpl-faq.en.html

Re: [R-pkg-devel] Submitting to CRAN a package depending on RGtk2

On 19 October 2016 at 23:24, Lorenzo Busetto wrote: | thanks for the answer. Yes, I know that that does the trick. In fact, | in our github README we have | the following intructions: | | "Install the following required dependencies: | | Cairo >= 1.0.0, ATK >= 1.10.0, Pango >= 1.10.0, GTK+ >=

Re: [R-pkg-devel] Submitting to CRAN a package depending on RGtk2

For this subproblem: On 19 October 2016 at 22:14, Lorenzo Busetto wrote: | On Linux builds, the problem is related but a bit different. | | 1. First of all, package "RGTk2" requires some external libraries to yu can just install r-cran-rgtk2 on your (Debian or Ubuntu) system and you should

Re: [R-pkg-devel] package in 'Suggests'

On 19 October 2016 at 19:29, Berry Boessenkool wrote: | A package I am developing will have one additional (not core) function depending on RCurl. | To keep dependencies low, I am considering to put RCurl in 'Suggests' instead of 'Imports'. | Also, I guess some users / systems may not have

Re: [R-pkg-devel] using optimx in a package

On 16 October 2016 at 18:05, Glenn Schultz wrote: | All, | | I am using optimx in my package to fit the term structure of interest rates.   When I call the function from the package I get the following error: | | Error in optimx.check(par, optcfg$ufn, optcfg$ugr, optcfg$uhess, lower, : |

Re: [R-pkg-devel] Error in dyn.load(dllfile) : unable to load shared object

On 1 December 2016 at 17:15, Aarti Singh wrote: | Hello, | | I am new to R package development. I am working on a package that has in | its src folder one (prime) cpp file and some helper cpp (X.Cpp, Y.Cpp) and | one c file (Z.C) and their header files (X.h, Y.h and Z.h) | | I am getting the

Re: [R-pkg-devel] Weird MAKEFLAGS bug

On 10 January 2017 at 11:55, Costas Tsirogiannis wrote: | Greetings and thanks for previously offered solutions, | | I am developing a package that makes use of C++ code, and I want to compile | this code for testing reasons with the "R CMD SHLIB" command. Using Ubuntu | and gcc 5.4, and because

Re: [R-pkg-devel] Including Rcpp in an existing package

On 22 December 2016 at 14:15, Duncan Murdoch wrote: | On 22/12/2016 1:55 PM, Glenn Schultz wrote: | > All, | > My package was not initially built with the rcpp use in mind. I have to include C++ source code for a particular project so I will have edit the description file add src files, etc.

Re: [R-pkg-devel] Registering compiled functions and Winbuilder pre-check error

On 24 March 2017 at 08:52, Jeremy Beaulieu wrote: | * checking compiled code ... NOTE | File 'hisse/libs/i386/hisse.dll': | Found no call to: 'R_registerRoutines' | File 'hisse/libs/x64/hisse.dll': | Found no call to: 'R_registerRoutines' | | It is good practice to register native routines and

Re: [R-pkg-devel] Makevars.win cppflags

On 15 March 2017 at 08:54, Charles Determan wrote: | I am working on an R package that contains some CUDA code. As such, it | needs to use the 'nvcc' compiler. I then need to use some of the R header | files such as R.h. On a linux machine, I can handle this with my configure | script using

Re: [R-pkg-devel] Warning of DDRTree

On 14 April 2017 at 01:49, Xiaojie Qiu wrote: | We are planning to update the DDRTree package but found the following | warnings: | | d:/RCompile/CRANpkg/lib/3.4/BH/include/boost/unordered/detail/buckets.hpp:586:29: | warning: ISO C++ 1998 does not support 'long long' [-Wlong-long] |

Re: [R-pkg-devel] R_registerRoutines, etc.

On 24 April 2017 at 10:45, Rolf Turner wrote: | On 24/04/17 10:31, Dirk Eddelbuettel wrote: | > On 24 April 2017 at 10:18, Rolf Turner wrote: | > | One more (I hope it's the last!) question: | > | | > | One of my subroutines has an argument of type *logical*. There is no | > | lo

Re: [R-pkg-devel] R_registerRoutines, etc.

On 24 April 2017 at 11:47, Rolf Turner wrote: | | On 24/04/17 11:22, Dirk Eddelbuettel wrote: | | > I would be surpised if init.c was Fortran. Anyway... | | It isn't of course. But it is the device used for "registering | routines" of all both flavours (i.e. both C and Fortr

Re: [R-pkg-devel] R_registerRoutines, etc.

On 23 April 2017 at 09:25, Rolf Turner wrote: | I have, like many others it would appear, been struggling with | the new-ish convention of requiring --- or quasi-requiring --- that | "routines" be "registered" and the warning generated by R CMD check to | the effect: | | > Found no calls to:

Re: [R-pkg-devel] maintainer built vignette

On 6 April 2017 at 20:17, Ian Carroll wrote: | How do I package an rmarkdown vignette that cannot be built on win-builder? The vignette in question demonstrates interaction with a SLURM cluster, which is not available to win-builder or travis. In my `.travis.yml` I can include `r_build_args:

Re: [R-pkg-devel] Help with Windows build failure

On 2 April 2017 at 17:21, Alexandre Sieira wrote: | Hi, everyone. | | I have done some work this weekend to allow the SnakeCharmR package ( | https://github.com/asieira/SnakeCharmR) to be compiled under Windows. For | reference, this is an Rcpp-based packages that links to the system's |

Re: [R-pkg-devel] Seamless way for a CRAN-bound package to depend on a Bioconductor package?

On 28 July 2017 at 12:42, Pavel Krivitsky wrote: | Dear All, | | There is a Bioconductor package (S4Vectors) whose functionality I want | to use in one of my packages, which I usually submit to CRAN. | | At this time, install.packages() does not automatically fetch | dependencies from

Re: [R-pkg-devel] package dependencies not detected?

On 16 August 2017 at 09:11, Berry Boessenkool wrote: | if a function in a package uses graphics::legend in the code, but does not import it in the namespace, shouldn't there be a warning in the check? The 'graphics' package is a base package, and as such *always* available where R is -- see its

Re: [R-pkg-devel] package dependencies not detected?

On 16 August 2017 at 12:51, peter dalgaard wrote: | > On 16 Aug 2017, at 11:11 , Berry Boessenkool wrote: | > | > if a function in a package uses graphics::legend in the code, but does not import it in the namespace, shouldn't there be a warning in the check? | >

Re: [R-pkg-devel] package dependencies not detected?

On 16 August 2017 at 09:44, Duncan Murdoch wrote: | On 16/08/2017 8:31 AM, Dirk Eddelbuettel wrote: | > | > On 16 August 2017 at 12:51, peter dalgaard wrote: | > | > On 16 Aug 2017, at 11:11 , Berry Boessenkool <berryboessenk...@hotmail.com> wrote: | > | > | > | > i

Re: [R-pkg-devel] CRAN checks errors

On 12 August 2017 at 14:01, Jernej Jevšenak wrote: | Dear R-package-devel community, recently I have released my R package | dendroExtra | 0.0.2 on CRAN. | | CRAN cheks |

Re: [R-pkg-devel] CRAN checks errors

On 12 August 2017 at 15:40, Jernej Jevšenak wrote: | Ok, I see now, that actually everything is OK. | | ERROR on older versions of R is therefore not a problem, right? "Ideally" those would show OK too but it is of lesser importance / sometimes explainable. Life goes on. | One more thing, a

Re: [R-pkg-devel] The Help (e.g. links) is not working for my packages

On 9 August 2017 at 08:38, Duncan Murdoch wrote: | Nothing that you've written is reproducible by others. See if you can | put together a short self-contained series of instructions that display | the problems (or just one of them). It might involve installing from | Github, or making a

Re: [R-pkg-devel] CRAN submission pretest warning about Rcpp version used to build dplyr

On 13 July 2017 at 16:58, Anderson,Brooke wrote: | I got the following warning when submitting a package to CRAN that I am struggling to understand: | | | Warning: Installed Rcpp (0.12.12) different from Rcpp used to build dplyr (0.12.11). It's a dplyr "thing". And for them, 'thing :=

Re: [R-pkg-devel] CRAN submission pretest warning about Rcpp version used to build dplyr

On 13 July 2017 at 19:52, Iñaki Úcar wrote: | Or, in other words, Brooke, now you have to wait until Rcpp 0.12.12 | appears on CRAN and then one or two days more until dplyr is rebuilt. | Then, try to resubmit your package. I disagree. That was a false alert, and it can be ignored. News at

Re: [R-pkg-devel] CRAN submission pretest warning about Rcpp version used to build dplyr

On 13 July 2017 at 12:13, Dirk Eddelbuettel wrote: | | On 13 July 2017 at 16:58, Anderson,Brooke wrote: | | I got the following warning when submitting a package to CRAN that I am struggling to understand: | | | | | | Warning: Installed Rcpp (0.12.12) different from Rcpp used to build dplyr

Re: [R-pkg-devel] Package submission with external library

On 30 June 2017 at 16:13, Nicolas Hiot wrote: | Thanks for your reply. | | 1. I don't want to depend on other packages that implement GSL. (Too | heavy for my purpose) That is *not* what Uwe suggested. He suggested you look at _other packages_ which _successfully use the GSL_ which include

Re: [R-pkg-devel] DllInfo & native routine registration

On 9 May 2017 at 15:59, Hannes Mühleisen wrote: | Hello R-package-devel, | | I have just completed porting the MonetDBLite package to use registered native routines [1]. This worked fine except one minor issue: MonetDBLite (and I suppose other software) extensively uses dlsym to find its own

Re: [R-pkg-devel] Note about portable file names

Konstantin, RcppMsgPack 0.1.1, containing MsgPack headers from msgpack-c 1.4.2, is now on CRAN. It should work for your purposes with a simple LinkingTo: RcppMsgPack. I turned of Windows builds; there is a weird interaction that may just be one of these include header order things but I haven't

Re: [R-pkg-devel] Package submission - Issue with pandoc in R CMD check

On 22 June 2017 at 16:36, Uwe Ligges wrote: | This should be resolved in general now. I appreciate your work on this, as well Gabor's help in providing new binaries. But correct me here if I wrong: It still does not help with this issue as long as _any other pandoc binary_ is called, correct?

Re: [R-pkg-devel] Package submission - Issue with pandoc in R CMD check

On 22 June 2017 at 16:23, Gábor Csárdi wrote: | So, along these lines, I was thinking if we could / should build a | pandoc R package, that could just pull the right binary at install | time. Would that make sense? It is a bit unusual, but I think a lot of | users would like it, and it would help

Re: [R-pkg-devel] R package with RcppArmadillo

On 8 June 2017 at 16:53, Maity, Arnab K wrote: | Some background information: I am trying to develop a package "afths" with | some R and C++ functions. I developed the package skeleton using | RcppArmadillo.package.skeleton(). As of today, CRAN contains 352 packages using RcppArmadillo. I like

Re: [R-pkg-devel] dependency cycle

On 13 June 2017 at 13:01, Berry Boessenkool wrote: | | Hi, | | I have a package A. Some of its functions are used in package B. | | B imports A in the DESCRIPTION, both are on CRAN. | | A has a function fff where I want to add some optional functionality. | | The problem: that optional stuff

  1   2   3   4   5   6   >