I just tried this out with R-4.0.2 on Linux and it looks like
.Rbuildignore does not treat lines with '#'s as comments. E.g.,
% mkdir test test/inst
% touch 'test/inst/#octothorp.txt' 'test/inst/normal.txt'
% echo > test/DESCRIPTION 'Package: test\nVersion: 0.1\nTitle:
test\nDescription: A test
On Mon, 17 Aug 2020 15:56:07 +0200
Thierry Onkelinx wrote:
> Can we add blank lines in .Rbuildignore? Or lines with only comments
> (line starting with #)?
.Rbuildignore is not documented  to allow comments, but the
current implementation does skip empty lines  since 2010 
On Sat, 15 Aug 2020 19:50:41 +0530
Akshit Achara wrote:
> To access these files, I need to use the path of libminizinc (which
> can change per installation). I want to extract this path from either
> Makevars or configure to use it in my package.
Just as Makevars is generated during
Can we add blank lines in .Rbuildignore? Or lines with only comments (line
starting with #)?
ir. Thierry Onkelinx
Statisticus / Statistician
Vlaamse Overheid / Government of Flanders
INSTITUUT VOOR NATUUR- EN BOSONDERZOEK / RESEARCH INSTITUTE FOR NATURE AND
Thanks for your answer!
I also got an answer from Rcpp-devel list by Nik Pocuca. He suggested me to
create an .RData or .rda file
(say config.RData) in the data folder of my package and then execute the
statement given below in Makevars.in
to save the flag in the .RData file.
On Fri, 14 Aug 2020 21:08:55 +0200
Cesko Voeten wrote:
> The package contains functionality to run on cluster nodes that were
> set up by the user and needs to access its own internal functions
> from there.
Apologies for derailing the thread, but I had a similar problem a few
in the configure script of my package RcppCWB, I use the command line call 'R
CMD config ...' to get the installation flags.
Calling 'R CMD config' will display options. For your scenario, you can use 'R
CMD config CPPFLAGS' to get the value of CPPFLAGS.
To call R CMD config