Peter,
On 11 June 2015 at 19:07, Peter Rossi wrote:
| I have made a package that includes a src/makevars file generated
automatically
| by Rcpp. It passes all checks.
You can also create src/Makevars by hand... BTW it wants a capital M on OS
with case-sensitive file systems.
| contents of src/makevars:
| PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS)
| PKG_CPPFLAGS += -I../inst/include/
|
| I submitted to CRAN and got the following message:
|
| * checking for GNU extensions in Makefiles ... WARNING
| Found the following file(s) containing GNU extensions:
| src/Makevars
| Portable Makefiles do not use GNU extensions such as +=, :=, $(shell),
|
| Clearly, I have to remove the += wildcard. How should I change it to make it
| "portable"?
"Nothing else here" -- R CMD check should stop complaining if you '=' instead
of '+='.
I looked this up the last time I had to do that [ (for the more involved
Makefile for the RInside examples) -- in that case I went the other way (per
Writing R Extensions / CRAN Policy) and just renamed the Makefile to
GNUMakefile. ] There is some documentation on-line, but "portable make" is
truly restriction. No shell, no if, ...
| also, CRAN complains about the lack of a LF at the end of src/makevars. Any
| thoughts on how to achieve this?
Maybe cat("\n", append=TRUE, con=fileconnection) ?
Also remember that you can test against R-devel by submitting to win-builder.
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
_______________________________________________
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
