On 10 October 2013 at 18:02, Romain Francois wrote: | To give some context, I'm taking about using R's linking mechanism. I'm | talking about generating automatically the code that: | - registers a function with R_RegisterCCallable | - grabs the function with R_GetCCallable
[...] | The name as given by nm definitely contains namespace information. You are making the heroic assumption that libraries are never stripped, this is something you have no control. Eg each of the 100+ r-cran-* packages in Debian and Ubuntu will by default be stripped, leading to your approach to go belly-up: edd@max:~$ nm /usr/lib/R/site-library/tseries/libs/tseries.so nm: /usr/lib/R/site-library/tseries/libs/tseries.so: no symbols edd@max:~$ "No symbols". This is a standard distro package a user may have: edd@max:~$ dpkg -S /usr/lib/R/site-library/tseries/libs/tseries.so r-cran-tseries: /usr/lib/R/site-library/tseries/libs/tseries.so edd@max:~$ So this approach can't be assumed to work _portably across compilers and os [distros]_ as I asked about earlier -- and which you chose to ignore. You can look at nm _on your box_ to learn about (unstripped) libraries. But I would surmise that you cannot rely on this to build a tool chain. Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com _______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
