similar to: Usage of R CMD INSTALL

Thanks to Tim Hoar and Kurt Hornik for taking the time to answer my question about the usage of R CMD INSTALL. Tim suggested: > R CMD INSTALL --configure-args=--with-netCDF=/opt/local/netcdf-3.5.0 netCDF > no quotes at all, no spaces ... Kurt wrote: > R CMD INSTALL --configure-vars='LIBS=-L/mylibs' mypackage Alas, I am not smart enough to know whether there is a contradiction

hi, i'm having some trouble getting a package to load a shared library object in .onLoad(...) i have a shared object file, say "mylib.so". if i start an R session, and via the CLI specify the actual library via: > dyn.load("mylib.so") everything works quite well (i.e. i can then follow with some .Call (...) methods) now, i'd like to include this shared library in

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

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:

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

hi all - i have a source package i'm writing that i'd like to be able to install with a special library that my R src files rely on. to be more precise, i have a normal R package directory structure (i.e. src/ R/ man/ DESCRIPTION NAMESPACE etc.). i also have another directory here called depPkg, and it has it's own configure file for the canonical './configure && make

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

Hi all, R CMD check does not work for me under Windows. This is the error R CMD check mypackage.tar.gz * checking for working latex ... OK tar: and: Not found in archive tar: Settings/miguez/ ... /00_pkg_src: Not found in archive tar: Error exit delayed from previous errors Error: cannot untar mypackage.tar.gz I know tar is available because R CMD build created the tarball in the first place

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

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

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

Dear r-devel list, I've observed at both of my submissions that issues arise at submission that were not pointed out by R cmd check --as-cran For example at my last submission: You have VignetteBuilder: knitr but there is nothing looking like a vignette in your source package.... We also see: * checking DESCRIPTION meta-information ... NOTE Author field differs from that derived from

When I run the following: cd \Rpkgs rcmd install mypackage -l library I get a message that it cannot find quadprog which is a library that mypackage depends on. Error: package 'quadprog' could not be loaded I previously used C:\Program Files\R\rw2011\library as my library for CRAN packages and did not have a problem but now that I use C:\Program Files\R\library this problem

Dear All, I have seen a number of e mails on this topic but I have not seen a general solution to date. I have Fortran and C source codes and they have been compiled successfully using: R CMD build mypackage And R CMD install mypackage Without error messages. I then open R and tests out two functions and get: > pgl(0.2,1,2,3,4) Error in

Dear All, I have seen a number of e mails on this topic but I have not seen a general solution to date. I have Fortran and C source codes and they have been compiled successfully using: R CMD build mypackage And R CMD install mypackage Without error messages. I then open R and tests out two functions and get: > pgl(0.2,1,2,3,4) Error in

I have some questions about 1. nomenclature, 2. recommended file locations and 3. overall procedure related to creating packages. To the extent that it matters, examples here relate to Windows XP R 2.0.1 beta. The questions are interspersed and prefaced with ***. My understanding is that there are actually 6 forms of a package that one should use in package development: 1.

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