Hello,
I am writing you about the GNU R-Project,
as part of by effort to help GNU projects provide a better, more
consistent build system.
Currently, your project does not support the DESTDIR variable in
generated Makefiles (marked as optional in the GNU coding policies, make and
automake manual)
G'day all,
> "HW" == hadley wickham <[EMAIL PROTECTED]> writes:
>> There aren't any immediate plans to change help(package=XXX), but I
>> think in the long run, if package?XXX receives wider support than it has
>> now, it would make sense to make that change.
HW> When was this
On Fri, 24 Feb 2006, Dirk Eddelbuettel wrote:
> 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.
Hi Claudio,
On 25 February 2006 at 03:11, Claudio Fontana wrote:
| Hello,
|
| I am writing you about the GNU R-Project,
| as part of by effort to help GNU projects provide a better, more
| consistent build system.
|
| Currently, your project does not support the DESTDIR variable in
| generated
The R package previously named Rcpp has been renamed to
RcppTemplate (version 1.4), and it is on its way to CRAN.
This is clearer because now RcppTemplate is an R package,
RcppExample is a sample R function, and Rcpp is a C++
class library.
The new package contains the Rcpp class library released
Brian,
On 25 February 2006 at 10:07, Prof Brian Ripley wrote:
| > 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
| > lic
