Re: [Rd] Rcpp, best method for linking to

From: Dirk Eddelbuettel <>
Date: Sat 25 Feb 2006 - 03:13:51 GMT


On 24 February 2006 at 15:00, Andrew Garbutt wrote:
| Sorry, that's not quite what I was asking. I was asking more of a "best
| practice" kind of question. My own C++ codes compile fine and are
| accessible to R with some great #define magic. I was noting that the
| Rcpp package has some generic classes to handle conversion of SEXP
| structures to STL and back again. As I far as I can see, using them
| would require that I compile the C++ code into a library and link to
| that library. Or copy the code into my own code base, but doing would
| restrict myself to the GPL, as it would be a derivative work?? (IANAL)
| At this point I do not want to commit to any particular licensure for my
| package.

I may be misunderstanding you but here it goes: if you are using Rcpp as a means to get to R, you still end up linking with R itself. It is my understanding that this implies the GPL -- or a suitable GPL-compatible license -- for your code.

I do not see any _additional restriction_ coming in via the addition of Rcpp. You already use GPL'ed object files / libraries via R itself. Plus you're presumably building with R toolchain via 'R CMD INSTALL ....'

Hth, Dirk  

Hell, there are no rules here - we're trying to accomplish something. 
                                                  -- Thomas A. Edison

______________________________________________ mailing list
Received on Sat Feb 25 14:21:45 2006

This archive was generated by hypermail 2.1.8 : Sat 25 Feb 2006 - 13:15:54 GMT