similar to: shared object location

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

Dear R users, we are trying to build a R package that includes a precompiled shared library, let's say mylib.so. We created the skeleton of the package and we moved the mylib.so file into the libs folder that we created at the same level of the folders man and R. Moreover we created the file NAMESPACE and we added the line useDynLib(mylib, .registration=TRUE). The building step seems to work

Dear R users, we are trying to build a R package that includes a precompiled shared library, let's say mylib.so. We created the skeleton of the package and we moved the mylib.so file into the libs folder that we created at the same level of the folders man and R. Moreover we created the file NAMESPACE and we added the line useDynLib(mylib, .registration=TRUE). The building step seems to work

I have a package that I'm developing that I need to unload the library. Long story short I figured out that the leaving the compiled code loaded lead to a segmentation fault, but unloading the code will fix it. I've read the documentation and it appears that there are several ways to do this? What is the popper accepted current standard for unloading compiled code? The options as I

I am using the .Call interface to call c++ code from R. For that, I am trying to create a dynamic library (mylib.so) using "R CMD SHLIB" by linking my own c++ code and an external c++ library (blitz++). The makefile works fine on my Mac, produces mylib.so and I am able to call .Call() from R, but on a linux server (I think Debian), I got the following error: ---------- /usr/bin/ld:

I am using the .Call interface to call c++ code from R. For that, I am trying to create a dynamic library (mylib.so) using "R CMD SHLIB" by linking my own c++ code and an external c++ library (blitz++). The makefile works fine on my Mac, produces mylib.so and I am able to call .Call() from R, but on a linux server (I think Debian), I got the following error: ---------- /usr/bin/ld:

Hi, I'm trying to write modified versions of R save/load functions which read from/write to a char array instead of a file pointer. I want to compile my functions into a library and dyn.load them. Of course the new functions mySave/Load will use some of the internal R functions used by save/load, for example "MarkSave" (to be found in .../src/main/saveload.c). I declared them as

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

Hello, I am trying to get a package to pass R CMD check on an iMac running Mac OS X. When the package is named safeBinaryRegression I get the following warning from R CMD check: * checking whether the name space can be loaded with stated dependencies ... WARNING Error in dyn.load(file, DLLpath = DLLpath, ...) : function 'make_lp' not provided by package 'lpSolveAPI'

Hi, I had a problem passing characters from R into c-code by dyn.load() and .C(). test.c: void R2Cdouble(double *db) { printf("\n my double: %f \n", db[0]); } test.R: dyn.load("mylib.so"); .C("R2Cdouble", as.double(0.5)); worked fine, but test1.c: void R2Cstr(char *str) { printf("\n my char: %s \n", str[0]); } test1.R:

Is there a way to query a package to see what dynamic shared libraries are loaded with it? The reason I ask is because during development, I want to unload libraries so that they can be reloaded without restarting R. I want to make it automatic so that you can just pass in the name of the package, and it will unload all the relevant shared libraries. Typically, the name of the shared library is

Hi, Has something changed regarding the useDynLib in the NAMESPACE file in packages? I've written a package that works in e.g. 2.12/2.13 but simply cannot find the dynamic library under windows. The version on CRAN is older than the one I'm talking about and depends on a newer version of R but I want to make the package available to people with older versions. >

I'm writing a package that interfaces to the FAME database, via a library of compiled C routines accessible through a Linux .so file. My .onLoad() function loads the .so like this: dyn.load("/opt/fame/timeiq/lib/linux_x86/libjchli.so", local = F) and after that I also load my own fame.so via library.dynam("fame", package = "fame") The code in fame.so uses

Hi, I wonder whether a package with namespace & dynamic library can be installed with the version number attached, ie. with the argument --with-package-versions. Is this currently possible? Using R 1.9.1 on Debian 3.0 I encounter a problem when trying to load a package installed with R91 CMD INSTALL --with-package-versions -l /mnt/local/R/R-1.9.x-libs-EpiR RIO in R started with R91

I am a little confused about the relationship between library.dynam and dyn.load >From the documentation: library.dynam(chname, Load the specified file of compiled code if it has not been loaded already, or unloads it. Where chname is a character string naming a shared library to load. and dyn.load(x, local = TRUE, now = TRUE) Load or unload shared libraries, and test whether a C function

Hello, I'm creating a package for R. This package containes a fortran (wrapped C) *.so . This dynamic library is compiled to be multi-threaded (-parallel -openmp -threads .. options). When I call this library from R : dyn.load("mylib.so") the execution is one threaded ! Where could be a problem and how to correct it ? Thank you ! [[alternative HTML version deleted]]

Luis, C_rnorm is a symbol but it's not exported. This means that you *can* do this by using stats:::C_rnorm. That said, it's not exported, which means that it's not supported to do this. So your package likely would not be allowed on CRAN, for example. Best, ~G On Jun 30, 2016 2:08 PM, "Luis Usier" <luis.henrique.usier at gmail.com> wrote: > Hi all, > >

Now I try to add some C and Fortan code to my package, so the NAMESPACE file is useDynLib(eha) importFrom(survival, Surv) export(mlreg.fit, risksets) but I get ..... * checking R files for library.dynam ... OK * checking S3 generic/method consistency ... WARNING Error in .try_quietly({ : Error in library(package, lib.loc = lib.loc, character.only = TRUE, verbose = FALSE) :

Hi, I have a problem with an external library on a previous R version. We've created our own package containing a mixture of C++ as well as R code which works fine under R 2.12.1. However, trying to install the very same package ZIP file on R 2.11.1 will issue an error when loading a library: > utils:::menuInstallLocal() package 'quasar' successfully unpacked and MD5 sums

Hi all, Looking at the body for the function rnorm, I see that the body of the function is: .Call(C_rnorm, n, mean, sd) I want to implement functions that generate normal (and other) random variables. Now, I understand that I can perfectly well just call the R wrapper for these functions and that will be almost indistinguishable for most purposes, but for whatever reason I wanted to try and