similar to: installing packages and libraries

Hello. I have what I know to be a simple question, but never having done anything like this it is pretty tough. I'm trying to write an R package. I have a collection of functions that I loaded into R and then used package.skeleton(). After editing everything in the resulting folder, call it NewPackage, I tried to follow along with some instructions I found for Windows users. I installed

My setup: Windows XP, R-2.6.0, Cygwin (not the Rtools version) When I tried to build a package, I was given this message: tar: c\:/X/Rpkgs/Drydown_1.41.tar: Cannot open: Input/Output error Even manually typing the following caused the same error: tar chf 'c:/X/Rpkgs/Drydown_1.41.tar' Drydown I looked at the 2.5.1 and 2.6.0 build scripts. After restoring this section to the 2.6.0 build

I noticed that in "R version 2.4.0 alpha (2006-09-16 r39365)" on Windows XP that I get this error: C:\Rpkgs>Rcmd install mypkg no Perl script 'install' The same command worked with no error in 2.3.1pat. If I capitalize INSTALL it does work; however, this was not necessary previously. Note that C:\Rpkgs>Rcmd check mypkg unlike install, still works in either lower or

I'm sorry but that is not a working example. A working example needs to create the plots being used. For example, stealing some code from https://rpkgs.datanovia.com/ggpubr/reference/ggarrange.html #================================================================= data <https://rdrr.io/r/utils/data.html>("ToothGrowth")df <- ToothGrowthdf$dose <- as.factor

Dear Gabor, Thank your for helping me so much! I have loaded R the newest version 2.1.1. Then I setup it in the path of D:\program files\R\ 1. unpack tools.zip into c:\cygwin 2. install Active perl in c:\Perl 3. install the mingw32 in c:\mingwin 4. add "c:\cygwin; c:\mingwin\bin" in "Control Panel -> System -> Advanced -> Environment Variables -> Path ->

When I try to build/install the quadprog package under R1.50 and NT4 it seems to have trouble finding blas routines. I'm currently using the generic blas routines, rather than ATLAS or some other tuned implementation: > Rcmd INSTALL d:/temp/quadrprog ... gcc --shared -s -o quadprog.dll quadprog.def quadprog.a quadprog_res.o -Lc:/a pps/rw1050/src/gnuwin32 -lg2c -lR

Dear colleagues, I am having issues trying to build a R package I recently wrote. I am using R 2.14.0 and my package depends on another package called aod. Running: R CMD Sweave vignette.Rnw is perfectly fine and the vignette compiles properly. but when I use R CMD build mypackage to build the tar.gz I get the following error: * installing the package to re-build vignettes * creating

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

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:

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

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

Hi, I have not been able to use R in my macbook pro. I am getting the following error message every time i try to install a package * installing *source* package ?Hmisc? ... ** package ?Hmisc? successfully unpacked and MD5 sums checked ** libs *** arch - i386 sh: make: command not found ERROR: compilation failed for package ?Hmisc? * removing ?/Users/ravshonbek/Library/R/2.15/library/Hmisc? *

Dear Sirs, I am trying to perform a garch analysis to some data time series.Therefore, I've downloaded the package "tseries", as the garch analysis is not available in the main R program.When I try to load the "tseries package" from the R-Console screen, the following message appears: local({pkg <- select.list(sort(.packages(all.available = TRUE))) + if(nchar(pkg))

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

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.

Hi, all, I just recently upgraded my computer though I'm using the same OS (XP). But now I'm having difficulty building packages and I cannot seem to solve the problem. I'm using R-2.1.1pat on Windows XP. Here is what I tried: D:\Users\sundard\slib\sundar\R>R CMD CHECK sundar * checking for working latex ... OK * using log directory

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