On 7 July 2012 at 02:47, Silkworth,David J. wrote:
| I need explicit help building a plugin that will do the same things that
Makevars.win did in the example package. Perhaps we could call this plugin
"RcppGSL.win" or something similar and make it available to everyone.
Actually, the same plug
>> | Unfortunately, I still don't know how to direct gcc to these header files
>> while using inline.
> The Rcpp-FAQ vignette has a worked example on how to specify a plugin which
> should apply to this case, see question 3.6 (or possibly 3.7 if you need just
> a single setting).
>
> Dirk
>
> -
On 7 July 2012 at 00:31, Silkworth,David J. wrote:
| After the glow of success with configuring GSL headers and libraries for
compilation in Windows, I have run into a problem duplicating this success
using inline for compiling.
|
| I have attempted the inline example directly from the RcppGSL
After the glow of success with configuring GSL headers and libraries for
compilation in Windows, I have run into a problem duplicating this success
using inline for compiling.
I have attempted the inline example directly from the RcppGSL Vignette. It is
clear that the includes are not being ac
Argh.. Apologies guys.. Found the error myself.
Constructor and deconstructor must be specified with {} even if no code is
foreseen for them.
A novice error, hope at least highlighting it could be useful to other newbies
like me :-)
cheers,
Francesco
On 6 Jul 2012, at 15:37, Lescai, Francesco
Hi there,
I've seen other posts similar to this one, but I'm a complete novice in the use
of Rcpp and couldn't really figure out how to solve the issue.
I'm learning how to use Rcpp before connecting R to some C++ classes I'm
developing.
I started with a simple home made example, but in both cas