Hi, I'm looking into creating R bindings for a medium sized C library. I have read up on how to access simple C functions using the .C and .Call methods and what I'm looking for now is a way to automate the generation of the necessary glue code. Ideal would be a SWIG-like package that does most of the leg work of the interface generation for R. Any tips or suggestions in that regard would be appreciated. Best, Benjamin --- Benjamin Georgi Max-Planck-Institute for Molecular Genetics Computational Molecular Biology --- Ihnestrasse 73 mail: georgi at molgen.mpg.de D-14195 Berlin, Germany phone: +49-30-8413-1146
On 18 October 2006 at 11:15, Benjamin Georgi wrote: | I'm looking into creating R bindings for a medium sized C library. I | have read up on how to access simple C functions using the .C and .Call | methods and what I'm looking for now is a way to automate the generation | of the necessary glue code. | | Ideal would be a SWIG-like package that does most of the leg work of the | interface generation for R. Swig 1.3.30 will have basic R support. You can check it out from their CVS. I haven't used it yet so I do not know how far this will get you. Dirk -- Hell, there are no rules here - we're trying to accomplish something. -- Thomas A. Edison
Maybe Matching Threads
- ./configure --prefix and R_LIBS
- labRow/labCol options in heatmap()
- Is there a way to represent the ... argument in signature?
- browser() is called incidentally (?) somewhere from inside methods::as
- 2 images with 2 color scales on one graphic device. How to get it?