Le 19/10/13 22:37, JJ Allaire a écrit :
Another alternative would be to create a new mechanism: an RcppExports.h file written into src (and thus not requiring modification of Makevars). This could include a comment explaining that anything "extra" the user wants in RcppExports.cpp should be declared there.
I don't like this. I think we should encourage people to use inst/include eitrher by doing it automatically as part of compileAttributes or by means of documentation.
On Oct 19, 2013, at 4:15 PM, Dirk Eddelbuettel <e...@debian.org> wrote: On 19 October 2013 at 16:06, JJ Allaire wrote: | For it to actually work though we'd need to modify Makevars as well (as Romain | pointed out) so that the RcppExports.cpp could see the include file. This might | get trickly. Well right now we simply set people up to fail / having to create it themselves. Rcpp.package.skeleton() has always created src/Makevars{.win} but currently does not include PKG_CPPFLAGS = ... Maybe it should. Anyway... | My thought was that we should either generate a fully working | solution or failing that generation enough pointers/documentation to get most | users over the hump. The thread is long enough, so maybe the next someone struggles with this they may find. If someone is itching to fix this, we will gladly take patches. Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com
-- Romain Francois Professional R Enthusiast +33(0) 6 28 91 30 30 _______________________________________________ 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
