Dear List, R packages may specify a "LinkingTo" attribute to specify dependencies to the source code (mainly the header files) of other packages.
Unfortunately, it is not possible to also have a reference to the generated library (.dll on Windows) of the other package. So including a header file from another package to call an (exported) function will just not help. I've tried to implement a workaround for my package rcom (depending on exported functions from rscproxy) by "manually" setting the library when linking, but unfortunately this does not work for me, when rscproxy gets installed into a different library (not the default one). OK, I could set the library path relative to the source drive and absolute for the standard library, so the "R CMD check" on CRAN is passed, but I don't think this would be a good solution. Of course, I could implement true dynamic binding by getting a handle to the rscproxy.dll (which already has been loaded at the time of loading rcom) and getting out procedure addresses, but I don't think this is a good (general and portable) solution either. How can this issue be addressed? How can I solve the problem of linking to another package's library (if possible by just using "LinkingTo") Best regards, Thomas Baier ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
