On 13-05-15 19:45, Dirk Eddelbuettel wrote:
On 13 May 2015 at 10:10, Kevin Ushey wrote:
| One other solution that's only a little crazy: you could have a R
| function within your package that generates the appropriate (portable)
| Makevars, and within the package `configure` script call that
|
On Fri, May 15, 2015 at 8:01 AM, Simon Urbanek
wrote:
> On May 13, 2015, at 2:28 PM, Henrik Bengtsson
> wrote:
>
>> While at it: 'Makevars' is an R invention (i.e. documentation of it
>> is only available through the R docs), correct? /Henrik
>>
>
> Well, it's just a Makefile fragment that get
On May 13, 2015, at 2:28 PM, Henrik Bengtsson wrote:
> While at it: 'Makevars' is an R invention (i.e. documentation of it
> is only available through the R docs), correct? /Henrik
>
Well, it's just a Makefile fragment that gets included along with the rest of
the Makefiles, so for all pract
While at it: 'Makevars' is an R invention (i.e. documentation of it
is only available through the R docs), correct? /Henrik
On Wed, May 13, 2015 at 10:10 AM, Kevin Ushey wrote:
> One other solution that's only a little crazy: you could have a R
> function within your package that generates the
On 13-05-15 18:08, Gábor Csárdi wrote:
On Wed, May 13, 2015 at 12:05 PM, Jan van der Laan mailto:rh...@eoos.dds.nl>> wrote:
[...]
Too bad. Since it is only a handful of files, I will probably move
them directly into the src directory and prefix them. It would have
been nice to have
On 13 May 2015 at 10:10, Kevin Ushey wrote:
| One other solution that's only a little crazy: you could have a R
| function within your package that generates the appropriate (portable)
| Makevars, and within the package `configure` script call that
| function. For example"
|
| R --vanilla --s
One other solution that's only a little crazy: you could have a R
function within your package that generates the appropriate (portable)
Makevars, and within the package `configure` script call that
function. For example"
R --vanilla --slave -e "source('R/makevars.R'); makevars()"
And that 'm
On Wed, May 13, 2015 at 12:05 PM, Jan van der Laan
wrote:
[...]
> Too bad. Since it is only a handful of files, I will probably move them
> directly into the src directory and prefix them. It would have been nice to
> have been able to keep them separate.
>
If it is a couple of files, then you c
Dirk Eddelbuettel schreef:
On 13 May 2015 at 17:27, Jan van der Laan wrote:
|
| I have some cpp-files from another library (boost) in a subdirectory
| in my src directory (src/boost_src). I include these using the
| following two lines in my Makevars:
|
| SOURCES = $(wildcard *.cpp boost_src/*
On 13 May 2015 at 17:27, Jan van der Laan wrote:
|
| I have some cpp-files from another library (boost) in a subdirectory
| in my src directory (src/boost_src). I include these using the
| following two lines in my Makevars:
|
| SOURCES = $(wildcard *.cpp boost_src/*.cpp)
| OBJECTS = $(SOURC
I have some cpp-files from another library (boost) in a subdirectory
in my src directory (src/boost_src). I include these using the
following two lines in my Makevars:
SOURCES = $(wildcard *.cpp boost_src/*.cpp)
OBJECTS = $(SOURCES:.cpp=.o)
However, R CMD check complains about my use of 'w
11 matches
Mail list logo
