Re: [R-pkg-devel] registering native routines

2018-04-11 Thread Henric Winell
Den 2018-04-10 kl. 23:30, skrev Rampal Etienne: Dear Thomas, Yes, I followed all those suggestions but it did not fix the x64 notes. Indeed I am using Windows. I am going to try this on a Linux system. On a 64-bit system you need to have 64-bit versions of the necessary tools on the path,

Re: [R-pkg-devel] registering native routines

2018-04-11 Thread Marcelino de la Cruz Rot
Thank you  for the hint, Henric. I was also having the same NOTE. Changing the path from \Rtools\mingw_32\bin to \Rtools\mingw_64\bin solved it completely. Cheers, Marcelino El 11/04/2018 a las 11:56, Henric Winell escribió: Den 2018-04-10 kl. 23:30, skrev Rampal Etienne: Dear Thomas, Yes,

Re: [R-pkg-devel] registering native routines

2018-04-11 Thread Dirk Eddelbuettel
On 10 April 2018 at 23:30, Rampal Etienne wrote: | Yes, I followed all those suggestions but it did not fix the x64 notes. | Indeed I am using Windows. I am going to try this on a Linux system. You could consider the R Hub service at https://builder.r-hub.io/ and/or via the CRAN package

Re: [R-pkg-devel] registering native routines

2018-04-11 Thread Rampal Etienne
Changing the path solved the problem. Thanks everyone! Rampal On 11-Apr-18 14:24, Marcelino de la Cruz Rot wrote: Thank you for the hint, Henric. I was also having the same NOTE. Changing the path from \Rtools\mingw_32\bin to \Rtools\mingw_64\bin solved it completely. Cheers, Marcelino El

Re: [R-pkg-devel] GPL + other licence

2018-04-11 Thread Martyn Plummer
I agree with Brian. This type of license is classified by the Free Software Foundation as "lax" or "permissive" because it does not prevent incorporation of the code into proprietary software. Here is what Richard Stallman has to say: https://www.gnu.org/licenses/ license-compatibility.en.html

[R-pkg-devel] Saving output of check()

2018-04-11 Thread J C Nash
Hi, In trying to test that an upgrade to my optimx package does not break other packages, I wanted to loop over a list of all such packages in alldep, with nall the length of this list. cat("Check the dependent packages\n") for (ii in 1:nall){ cpkg <- alldep[ii] dd <-

Re: [R-pkg-devel] Saving output of check()

2018-04-11 Thread Georgi Boshnakov
Hi, Not really an answer but I only recently discovered devtools::revdep(), which automates checking reverse dependencies. Georgi Boshnakov From: R-package-devel [r-package-devel-boun...@r-project.org] on behalf of J C Nash

Re: [R-pkg-devel] Saving output of check()

2018-04-11 Thread Uwe Ligges
Not sure why nobody dicusses the R internal check functionality, also for reverse dependencies, from the tools package? That is what CRAN uses for the reverse dependency checks. Best, Uwe Ligges On 11.04.2018 23:14, J C Nash wrote: Another workaround is to use tlogl <-

Re: [R-pkg-devel] Saving output of check()

2018-04-11 Thread Ben Bolker
I have at various times tried the built-in (tools package) solution; fairly complex hand-rolled stuff I did myself; and revdepcheck. I found that revdepcheck handled installation of needed dependencies, including caching packages where necessary, more easily. It felt like the 'tools'

Re: [R-pkg-devel] Saving output of check()

2018-04-11 Thread Henrik Bengtsson
R CMD check, which is used internally runs checks in standalone background R processes. Output from these is not capturable/sinkable by the master R process. The gist of what's happening is: > sink("output.log") > system("echo hello") ## not sinked/captured hello > sink() >

Re: [R-pkg-devel] Saving output of check()

2018-04-11 Thread J C Nash
Another workaround is to use tlogl <- readLines(attr(cpkg.chk, "path")) Possibly this may suggest a way to improve functionality. JN On 2018-04-11 03:24 PM, Henrik Bengtsson wrote: > R CMD check, which is used internally runs checks in standalone > background R processes. Output from these is

Re: [R-pkg-devel] Saving output of check()

2018-04-11 Thread J C Nash
I got several responses to my query. Henrik's does suggest "why", but I am rather unhappy that R has this weakness. (See below for a sort of workaround for Linux users.) In particular, note that the check_built() function DOES return an object, but it does NOT print(). In fact, putting alldep <-

Re: [R-pkg-devel] Saving output of check()

2018-04-11 Thread J C Nash
Indeed these are useful for one of my present tasks. Thanks. JN On 2018-04-11 03:10 PM, Georgi Boshnakov wrote: > > Hi, > > Not really an answer but I only recently discovered devtools::revdep(), > which automates checking reverse dependencies. > > Georgi Boshnakov > > > > >