search for: mypackages

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 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.

...brary from .libPath() while doing some exploratory testing using (the loaded development version of) mypackage. Anyway, this lead to the 2nd part of my query - could / should loadNamespace ensure that at execution time, otherpackage::otherfun actually respects the version contraint specified in mypackages DESCRIPTION file? POSSIBLE ANSWER 1 - THIS IS TOO COMPLEX AND HYPOTHETICAL ================================================= One thought was - this is all getting too complex and hypothetical, there is only so much automatic protection that R / loadNamespace can offer, in which case the answe...

Hi, I need to link mypackage to 2 other packages so I can call some C functions defined in these 2 packages from mine. I've tried Depends: packageA, packageB LinkingTo: packageA, packageB as suggested by the "5.4 Registering native routines" section of the "Writing R Extensions" manual but then only packageA is seen at compilation time (gcc is called with

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

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

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

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

...began to modify a shared Rprofile so that once a week it checks for new packages and updates to the current version of the installed packages on CRAN. Sounds simple enough. Plus some general conditioning statements to make sure that this runs only once a week or so the logic I'm following is: myPackages <- installed.packages() CRANsPackages <- CRAN.packages() missingPackages <- CRANsPackages[is.na(match(CRANsPackages[,1], myPackages[,1])),1] install.packages(missingPackages) Now this might be trivial, but, missingPackages includes bundled packages which are already installed (e.g...

I see 'library(stats)' at the beginning of R-2.10.0/src/library/stats/tests/nls.R. I'm wondering if I am developing my own package 'mypackage' whether I should put 'library(mypackage)' in a .R file in mypackage/tests/? If I do, then it seems awkward to me, because to use 'library(mypackage)', I have to first get 'mypackage' installed. So the

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

Hi I found yum-downloadonly and executed my command do that and save the dependencies in my current directory. Now when I execute my command: rpm -i mypackage all the dependencies are not found even though they are in the current directory. if I do a "yum install mypackage" (and its in the current directory) its not found either. How do I now install the mypackage in the current

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:

Hi all. I started looking at Rcpp, which looks pretty great, actually. At the moment just trying to compile a module to get a feel how it all works without fully understanding how all the pieces fit together. Basically, i took the first example from Rcpp modules vignette: fun.cpp ======================== #include <Rcpp.h> #include <math.h> using namespace Rcpp; double

How does one go about invoking a method within a namespaced package if that package has not been loaded via library method? Given "mypackage" and method "foo" within: mypackage::foo(1, 2, 3) Executing the same method's function call: do.call("foo", list(1, 2, 3)) didn't work. Nor did the following: do.call("mypackage::foo", list(1, 2,

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