shared object location
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 package. but this is cumbersome and doesn't allow other people to have a single version of the R package to use as part of a team effort to debug/test both the package's R code and my C code for the library functions. hopefully this makes a bit more sense, and if anyone has any tips on how R actually loads shared objects it would be greatly appreciated.
I'm afraid I don't have a solution for you. Reading through your post, I'm confused about why you want to have your .so file outside of the package? Why not follow the usual scheme and R CMD INSTALL yourPkg with the version of R code and C code you want to use/test. This would best allow other people to have a single version of the R package, no? + seth
Seth Falcon | @sfalcon | http://userprimary.net/user