Dear R package devels,
I am trying to check a package which depends on fastICA on
win-builder.r-project.org, the checks fail complaining that fastICA is
not installed.
Cheers,
Guido
PS: the log can be found here:
https://win-builder.r-project.org/265alZrIl0s6/00check.log
--
Guido Kraemer
29; current
R-devel is 75412.
Duncan Murdoch
Gabor
On Mon, Oct 8, 2018 at 12:34 PM Duncan Murdoch
wrote:
On 08/10/2018 7:08 AM, Guido Kraemer wrote:
Hi all,
update: I submitted to CRAN and it passes all test just fine
(https://cran.r-project.org/web/checks/check_results_coRanking.htm
Hi all,
update: I submitted to CRAN and it passes all test just fine
(https://cran.r-project.org/web/checks/check_results_coRanking.html). I
still have no idea why travis fails.
Best Regards,
Guido Kraemer
On 09/17/2018 05:45 PM, Guido Kraemer wrote:
Hi all,
Since a couple of days
FYI, the problem just fixed itself.
On 10/8/18 2:52 PM, Guido Kraemer wrote:
Thanks for looking into this:
- I deleted the travis cache and it did not help.
- R should update all its packages before attempting to install the
coRanking package, so old packages shouldn't be a problem.
So I
Dear Rampal:
What version of R are you using? I had this bug appearing a while a go
on r-devel on travis
(https://stackoverflow.com/questions/52532026/r-object-nativeroutines-not-found/52924244#52924244),
it disappeared after a while.
Cheers,
Guido
On 11/6/18 9:27 PM, Rampal Etienne
Hi all,
Since a couple of days travis-ci fails for my package coRanking with "R:
devel".
The error message is:
Error in nativeRoutines[[lib]] <- routines :
object 'nativeRoutines' not found
"R: release" and "R: oldrel" work fine. Did some R internals change or
is the
"R: devel" on travis
under 1Mb, but gives a warning in
`R CMD check --as-cran` because `-flto` doesn't seem to be portable.
Cheers,
Guido
On 12/11/19 2:15 PM, Iñaki Ucar wrote:
On Wed, 11 Dec 2019 at 14:07, Guido Kraemer wrote:
I am building an R package (https://github.com/gdkrmr/zarr-R) that wraps
a couple of C
I am building an R package (https://github.com/gdkrmr/zarr-R) that wraps
a couple of C++ headers and the resulting shared object is huge (>20Mb,
see https://travis-ci.org/gdkrmr/zarr-R). I have tried to set the
following in `./src/Makevars`:
PKG_CPPFLAGS=-I"../inst/include"
` and it works great, it gets the size of the shared
object down to 1.3 Mb.|
|When submitting this to CRAN some day, should I apply this trick or
ignore it and let the user|
|decide with the new ``R CMD install --strip`` option in R 3.6? Cheers,
Guido |
||
|
|
On 12/11/19 2:25 PM, Guido Kraem
I am developing an R package that can make (optional, but strongly
recommended) use of a number of external compression algorithms. What is
the best strategy if I want to distribute this as an R package? Because
the package is for reading large external data sets, the package will
probably not
I am testing building a package on Windows. The package requires C++14.
I have installed the latest versions of R (3.6.2), RTools (3.5), and
RStudio. The package builds fine under Linux.
I get the following error:
> devtools::install_github("gdkrmr/zarr-R")
...
C++14 standard
:
On Tue, Feb 4, 2020 at 5:51 PM Guido Kraemer wrote:
I have also set `~/.R/Makevars.win` as suggested in the manual "Writing
R extensions", Section 1.2.5 "Using C++14 code".
What exactly do you have in src/Makevars.win? Just the simple CXX_STD
= CXX14 or the more complex
and a
proper MSYS environment with a package manager! Is there a due date for
R 4.0.0?
Guido
On 2/4/20 6:14 PM, Dirk Eddelbuettel wrote:
On 4 February 2020 at 17:51, Guido Kraemer wrote:
| I am testing building a package on Windows. The package requires C++14.
You will have to wait.
The current
I need to distribute some 3rd party headers with my package. The headers
make R CMD check produce warnings:
File which contains pragma(s) suppressing important diagnostics:
...
Files which contain pragma(s) suppressing diagnostics:
...
There are some additional NOTEs on the use of
Thanks, just to drive this a bit further:
What if the headers then start producing some ugly compile warnings? Do
I have to fix these, too?
On 1/16/20 5:12 PM, Dirk Eddelbuettel wrote:
On 16 January 2020 at 17:06, Iñaki Ucar wrote:
| On Thu, 16 Jan 2020 at 16:58, Guido Kraemer wrote
I need to set up different compile flags for MacOS, Linux, and Windows.
For Windows I can just use `Makevars.win` but I cannot figure out how to
do the same for MacOS.
Cheers,
Guido
__
R-package-devel@r-project.org mailing list
I have solved it for now using:
UNAME_S := $(shell uname -s)
ifeq ($(UNAME_S),Linux)
PKG_CPPFLAGS=...
PKG_LIBS=...
else
PKG_CPPFLAGS=...
PKG_LIBS=...
endif
But R CMD check now complains about GNU extensions.
Best,
Guido
On 11/25/20 2:50 PM, Guido Kraemer wrote:
I need to set
I am the maintainer of coRanking and got a message about an error, the
error can be found here [1]. I can reproduce the error on my own machine
with the latest R-devel but don't quite understand what the error means
and how I can fix it. A search leads to an issue in Rcpp [2] where the
e generated RcppExports.R via Rcpp's own `compileAttributes()` function (as
I did in PR that Edzer merged hours later).
But none of this helps Guido as his package prefers to do it all by hand --
which is perfectly fine and valid, of course -- but a little bit more work.
Hth, Dirk
--
Dr. Guido Kraemer
Remote
19 matches
Mail list logo
