similar to: R CMD check in Windows

Dear friends, I am building an R package called *mypackage*. I followed every possible steps (to my understanding) for the same. I got following problem while doing *R CMD check mypackage*. * installing *source* package 'mypackage' ... ** libs cygwin warning: MS-DOS style path detected: C:/PROGRA~1/R/R-213~1.0/etc/i386/Makeconf Preferred POSIX equivalent is:

Function/file names are hypothetical. Say I have written myfunction.R, which calls myfunction.c via .C("myfunction", ...). I've compiled successfully myfunction.c via R CMD SHLIB myfunction.c in the terminal. Then, in the R console: dyn.load("myfunction.so") source("myfunction.R") test <- myfunction() # works fine So everything is in order, myfunction works

Folks: sessionInfo() R version 2.15.0 (2012-03-30) Platform: i386-pc-mingw32/i386 (32-bit) locale: [1] LC_COLLATE=English_United States.1252 [2] LC_CTYPE=English_United States.1252 [3] LC_MONETARY=English_United States.1252 [4] LC_NUMERIC=C [5] LC_TIME=English_United States.1252 attached base packages: [1] datasets splines grid tcltk stats graphics grDevices [8] utils

Folks: sessionInfo() R version 2.15.0 (2012-03-30) Platform: i386-pc-mingw32/i386 (32-bit) locale: [1] LC_COLLATE=English_United States.1252 [2] LC_CTYPE=English_United States.1252 [3] LC_MONETARY=English_United States.1252 [4] LC_NUMERIC=C [5] LC_TIME=English_United States.1252 attached base packages: [1] datasets splines grid tcltk stats graphics grDevices [8] utils

I'm trying to get ready to submit a package to CRAN, but in order for the package to install on OS X, I need to temporarily set the environment variable NOAWT=1. I put 'export NOAWT=1' in my package's 'configure' script, and 'R CMD INSTALL MyPackage' returns with no errors. However when I do 'R CMD CHECK MyPackage', the installation test fails, because

I'm trying to get ready to submit a package to CRAN, but in order for the package to install on OS X, I need to temporarily set the environment variable NOAWT=1. I put 'export NOAWT=1' in my package's 'configure' script, and 'R CMD INSTALL MyPackage' returns with no errors. However when I do 'R CMD CHECK MyPackage', the installation test fails, because

Hello, All: How can I obtain the location of an example data file in a package during "R CMD check"? I want to include sample raw data files in a package and have them read by a function in the package. It occurs to me to put such a file in "\inst\rawdata" and have examples find the data using something like "system.file('rawdata',

I have been working on an R package that calls C code using .C(). I recently started including some functions from the GNU Scientific Library in my code. The code runs fine on my machine when not wrapped in the package. But I get the following error from "R CMD check" * checking whether the package can be loaded ... ERROR Loading required package: splancs Loading required package: sp

The help page for INSTALL says, in part, Some package sources contain a `configure' script that can be passed arguments or variables via the option `--configure-args' and `--configure-vars', respectively, if necessary. The latter is useful in particular if libraries or header files needed for the package are in non-system directories. In this case, one can

Hi All, Apologies in advance if this is not the right email to post this question. I successfully created my first R package myPackage1. Now I want to create another R package myPackage2 which requires functions from myPackage1. However when I try R CMD check myPackage2 I get the following error * checking for working pdflatex ... OK * using log directory

Dear R-users, I am having some issues with a package I am working on (using R 2.12.1 in a Linux environment) and would like to have your opinions/advises. My package - let's call it mypackage for the purpose of this email - passes all checks of R CMD check, except for the following failure message: Error : .onLoad failed in loadNamespace() for 'mypackage', details: call:

Hello everybody, Currently I'm developing a library, which uses some functions from another package (namely plotrix). Consequently, I listed this dependency in the DESCRIPTION file. When I try to run "R CMD check mypackage", the check fails, for the library plotrix cannot be found on the system. As far as I understood "R CMD check" uses --vanilla implicitly, thus, no

I will repost on R-devel. -- Bert On Tue, Jul 17, 2012 at 10:32 AM, Prof Brian Ripley <ripley@stats.ox.ac.uk>wrote: > On 17/07/2012 18:20, Bert Gunter wrote: > >> Folks: >> >> sessionInfo() >> R version 2.15.0 (2012-03-30) >> Platform: i386-pc-mingw32/i386 (32-bit) >> >> locale: >> [1] LC_COLLATE=English_United States.1252 >> [2]

Dear all, I'm trying to create my own package by following for instance http://epub.ub.uni-muenchen.de/6175/2/tr036.pdf In step 6 (page 19) it says that the command 'R CMD build <mypackage>' should result in a tar.gz file. However, after running the command I end up with a tar file only (no gz extension). I also get the following warnings in the command prompt C:\Program

I have question regarding package installation. What is the difference between check, INSTALL, build and build --binary, which imply which and what order does one normally perform them? I have been trying: R CMD build /mypackage R CMD check /mypackage R CMD build --binary /mypackage in that order but wanted to check that this is right. Also, what portion of the check process can be run

Dear List, I’m doing my first baby steps towards developing own R Packages and ran into the following problem: R CMD check mypackage works fine (no errors, no warnings) R CMD build mypackage works fine (no errors, no warnings) R CMD INSTALL –library=”C:\R\R-2.11.1\library” “something\mypackage\mypackage_1.0.tar.gz” works fine (no errors, no warnings) However, when I try loading the

Dear List, I’m doing my first baby steps towards developing own R Packages and ran into the following problem: R CMD check mypackage works fine (no errors, no warnings) R CMD build mypackage works fine (no errors, no warnings) R CMD INSTALL –library=”C:\R\R-2.11.1\library” “something\mypackage\mypackage_1.0.tar.gz” works fine (no errors, no warnings) However, when I try loading the

Hi I have a package which was built using R 1.9.1 and everything worked fine. I recently upgraded to R 2.0.1 and tried to re-install my package - and I got: Error in library(mypackage) : 'mypackage' is not a valid package -- installed < 2.0.0? So I tried rebuilding it using my new version of R: R CMD BUILD --binary mypackage hhc: not found cp: cannot stat `mypackage.chm': No

Dear all, I have been building R packages under windows on my old pc, successfully. Now I have bought a new pc, still running windows, and I am trying to build the same R packages as before, but now without the same success. I have installed the Rtools, perl, mingw and added them to the environment variables. I am running Windows XP Professional on a Thinkpad T60. I have installed R-2.4.1,

I'm putting together an R package. I would like to show example code in the vignette, where example data files (included in the package) are used to generate an (example) output file. I read about using example data in Hadley Wickham's post ( http://r-pkgs.had.co.nz/data.html), and believe I should keep my example data as raw data, as it must be parsed to generate the output. So, I