R devel - May 2015 - Alternative for wildcard gnu extension in Makevars

Dirk Eddelbuettel <edd at debian.org> 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/*.cpp)
> | OBJECTS = $(SOURCES:.cpp=.o)
> |
> | However, R CMD check complains about my use of 'wildcard'. How do
I
> | handle this without any gnu extensions?
>
> I looked into this a few weeks (months?) ago, and it would appear that you
> cannot.
>
> I would recommend the alternative offered in Writing R Extensions: renamed
it
> GNUmakefile or add a SystemRequirements: GNU make.
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.

Thanks!
Jan

On Wed, May 13, 2015 at 12:05 PM, Jan van der Laan <rhelp at 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 been able to keep them separate.
>
If it is a couple of files, then you can also just list them in SOURCES (or
even just OBJECTS, with a .o suffix), and leave them where they are.

Gabor

[...]

	[[alternative HTML version deleted]]

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 'makevars()' function could generate portable
'Makevars(.win)' files for your package.

Kevin

On Wed, May 13, 2015 at 9:08 AM, G?bor Cs?rdi <csardi.gabor at gmail.com>
wrote:
> On Wed, May 13, 2015 at 12:05 PM, Jan van der Laan <rhelp at
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 been able to keep them separate.
>>
>
> If it is a couple of files, then you can also just list them in SOURCES (or
> even just OBJECTS, with a .o suffix), and leave them where they are.
>
> Gabor
>
> [...]
>
>         [[alternative HTML version deleted]]
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

On 13-05-15 18:08, G?bor Cs?rdi wrote:
> On Wed, May 13, 2015 at 12:05 PM, Jan van der Laan <rhelp at eoos.dds.nl
> <mailto:rhelp at 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 been able to keep them separate.
>
>
> If it is a couple of files, then you can also just list them in SOURCES
> (or even just OBJECTS, with a .o suffix), and leave them where they are.
>

That would be a nice solution, but it is a couple (~10) files in the 
src/boost_src directory. Directly under the src directory there are much 
more files, and the names and number of these will frequently change so 
I don't want to keep maintaining this list. Although I could add the 
generation of Makevars to my build script.

Thanks for the suggestion.

Jan