An embedded and charset-unspecified text was scrubbed... Name: not available Url: https://stat.ethz.ch/pipermail/r-devel/attachments/20060224/aa7635ad/attachment.pl
Rcpp, best method for linking to
3 messages · Andrew Garbutt, Andrew Finley, Dominick Samperi
Hi Andy,
Follow the suggestions for c++ in the Writing R Extensions document.
Wrap your c++ code in extern "C"{}, include your classes in the includes
(e.g., #include "myclass.h") and put the myclass.h and myclass.cpp in
the src directory along with your other code. Then R CMD build ... and R
CMD INSTALL ... This works for me.
-Andy
On Fri, 2006-02-24 at 13:11 -0800, Andrew Garbutt wrote:
Dear all, After a bit of reading I came across the Rcpp example package. There are a few classes that I would like to use and I am not sure how best to include them in my own package. Is it best to compile it as an independent library and link to it? Or is there some way to `require` it for my own package? Re-write using the code as an example (unsure how best to do this at this moment, as the Rcpp package is licensed under the GPL v2 and I am unsure of the license that I wish to use for my own package.) Any thoughts or ideas would be appreciated. Thanks, Andy [[alternative HTML version deleted]]
______________________________________________ R-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Research Fellow Department of Forest Resources University of Minnesota Office: 305 Green Hall Phone: (612) 624-1714 Fax: (612) 625-5212 web: http://blue.fr.umn.edu
Hi Andy (and Andy),
I'm not sure why there should be any licensing issues. R itself is GPL-ed,
so I just followed this convention.
Of course, you can do it yourself with extern "C" and all that. The
purpose of Rcpp.{cpp,hpp} is to enable you to write
readable code (for a C++ programmer) while hiding the error-prone
macro gymnastics that is required to fetch R parameters when using
the .Call interface. There is also a fair amount of type checking done
in the Rcpp package that relieves you of the trouble of putting many
checks in your R code.
If you are using the older, simpler .C interface this may not be
important to you. But note that the same functionality is available
through Rcpp, with the added convenience that list item names
are not dropped like they are when you use the .C interface.
Dominick
Andrew Finley wrote:
Hi Andy,
Follow the suggestions for c++ in the Writing R Extensions document.
Wrap your c++ code in extern "C"{}, include your classes in the includes
(e.g., #include "myclass.h") and put the myclass.h and myclass.cpp in
the src directory along with your other code. Then R CMD build ... and R
CMD INSTALL ... This works for me.
-Andy
On Fri, 2006-02-24 at 13:11 -0800, Andrew Garbutt wrote:
Dear all, After a bit of reading I came across the Rcpp example package. There are a few classes that I would like to use and I am not sure how best to include them in my own package. Is it best to compile it as an independent library and link to it? Or is there some way to `require` it for my own package? Re-write using the code as an example (unsure how best to do this at this moment, as the Rcpp package is licensed under the GPL v2 and I am unsure of the license that I wish to use for my own package.) Any thoughts or ideas would be appreciated. Thanks, Andy [[alternative HTML version deleted]]
______________________________________________ R-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel