On 27 September 2016 at 15:23, Eric Deveaud wrote:
| so why ~/R/Makevars allows to change CC and not src/Makevars ?
|
| this is pretty confusing.
It seems weird at first, but makes some sense when you think about it like
this:
-- src/Makevars is inside a package and cannot / should not alter "system"
parameters like compiler brand or version as there may only be one
compiler, the one R was built with
it does allow however to set compilation flags, language standards,
include directories etc as needed to build the package
-- (user- or system-level) Makeconf allow compiler changes, but that is
orthogonal to the per-package config and stays local to the machine
| in unix world mechanism of overwriting system default in user and
| package order is something standadr and consistent given the level
|
| priority is package specific stuff overwrite user configuration that
| overwrite system default
|
| mechanism of Makevars is NOT consistent
Yes we sometimes wish we could override system Makeconf settings in a
package, but we can't.
| as a side note I solved the problem of overwritting CC for this
| particular package using MAKEFLAGS="CC=gcc" R CMD INSTALL package
That works and is documented, but is not "portable" to other machines.
Hope this helps, Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
