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
t
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. My thought was that we should either generate a
fully working solution or failing that generation enough
pointers/documentation
On 19 October 2013 at 15:40, JJ Allaire wrote:
|
| Maybe you could follow the example of Rcpp.package.skeleton() and just
drop
| an empty yet amply commented file there? By "being there" users have a
| better chance of stumbling over it :)
|
|
| Since this would involve creating a
> Maybe you could follow the example of Rcpp.package.skeleton() and just drop
> an empty yet amply commented file there? By "being there" users have a
> better chance of stumbling over it :)
>
Since this would involve creating a new directory (inst/include) perhaps I
could instead emit comments a
On 19 October 2013 at 15:14, JJ Allaire wrote:
| RcppExports.cpp will automatically include a .h that has the same name as
| the package and is located in inst/include, iirc.
Hah!
| This is indeed the current solution to the problem of typedefs, however I
admin
| that it's a bit diffi
> RcppExports.cpp will automatically include a .h that has the same name as
> the package and is located in inst/include, iirc.
This is indeed the current solution to the problem of typedefs, however I
admin that it's a bit difficult to take advantage of without wading through
documentation and/o
Le 19/10/13 20:09, Dirk Eddelbuettel a écrit :
On 19 October 2013 at 17:55, Romain Francois wrote:
| Try putting your declarations into a RItools.h file in inst/include/ or
| src/ in your package, i.e. have this in RItools.h
|
| typedef double (*testStat)(NumericVector, NumericVector);
|
| and a
On 19 October 2013 at 17:55, Romain Francois wrote:
| Try putting your declarations into a RItools.h file in inst/include/ or
| src/ in your package, i.e. have this in RItools.h
|
| typedef double (*testStat)(NumericVector, NumericVector);
|
| and add:
|
| PKG_CPPFLAGS += -I../inst/include/
(
Le 19/10/13 05:13, Mark Fredrickson a écrit :
Hello,
Short version: Is it possible to instruct the code generator in
`compileAttributes` to source local header files when generating
RcppExports.cpp?
Long version: I'm trying to crib from the Dirk's examples in his recent
UCB talk examples about
>
> The same trick was already used in RcppDE (which was a proof of concept
> about
> converting DEoption from 700 lines of plain C to 400 lines of C++ / Rcpp)
> where I have
>
> typedef double (*funcPtr)(SEXP);
>
> and the rest works like a 'plain old package'.
>
Certainly. And while I ha
On 18 October 2013 at 22:13, Mark Fredrickson wrote:
| Short version: Is it possible to instruct the code generator in
| `compileAttributes` to source local header files when generating
| RcppExports.cpp?
I'll let JJ take the Attributes aspect but maybe it is something else...
| Long version: I
11 matches
Mail list logo
