I am just trying to adjust one of my packages so the C code builds in
Windows. This is code that has been around for a long time, and I'm am
only a casual reader of C, so it has had the "if it is not broken don't
touch it" approach for many years. The section 1.2.1 "Using Makevars"
of "Writing R extensions" starts:
"Sometimes writing your own configure script can be avoided by supplying
a file Makevars: also one of the most common uses of a configure script
is to make Makevars from Makevars.in." ...
I am still a bit confused about whether packages src/ should have, in
addition to Makevars.win, a file Makevars or a file Makevars.in. The
rest of the section seems to imply that the file should be Makevars, but
the first four examples I pulled of CRAN all have Makevars.in. My
confusion is about whether R scripts will automatically turn Makevars.in
into Makevars or would I need my own configure script to do this (and I
am hoping not to need a configure script).
Which is preferred? (And could the first paragraph of the section be
made more explicit?)
Thanks,
Paul
====================================================================================
La version française suit le texte anglais.
------------------------------------------------------------------------------------
This email may contain privileged and/or confidential in...{{dropped:26}}
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
