as a motivating example, consider the case where multiple/many R
packages are being developed that all use the same shared object
functions.
each time (during development) that the shared object file changes we
could go alter every single R package directory, or simply have the R
package utilize t
The primary reason is for development.
I do install via the traditional R CMD INSTALL (or variant) method,
but I want to keep the C code external from the R package.
In particular, I want to be able to modify the C code (and thus the
compiled .so library functions) without having to constantly re-
Hi,
On 1/29/10 12:58 PM, Murat Tasan wrote:
problem is, i haven't been able to do this yet.
my workaround is to constantly swap into myRPackage/libs/ directory a
version of the shared object library called myRPackage.so, and load it
via the useDynLib(...) directive in the NAMESPACE file of the
hi all, i posted a question before about this, but i may have been too
cryptic to understand.
in short, there exists an R package that someone is writing. this
package depends on a custom library (written in C,), compiled as a
shared, and called by the package's functions via the .Call(...)
metho
4 matches
Mail list logo
