similar to: Makevars and Makeconf sequencing

Le 27/09/16 ? 13:31, Dirk Eddelbuettel a ?crit : > > On 27 September 2016 at 09:37, Eric Deveaud wrote: > | Hello, > | > | I'm tring to install a Rpackage that holds some C//C++ code > | > | as far as I understood the R library generic compilation mechanism, > | compilation of C//C++ sources is controled > | > | 1) at system level by the ocntentos

Hello, I'm tring to install a Rpackage that holds some C//C++ code as far as I understood the R library generic compilation mechanism, compilation of C//C++ sources is controled 1) at system level by the ocntentos RHOME/etc/Makeconf 2) at user level by the content of ~/.R/Makevars 3) at package level by the content of src/Makevars Problem I have is that src/Makevars is ignored see

Hi, I am trying to package some code to use with R and wanted to call Rscript from within the Makevars file (I am trying to automate the setting of the location of a third party library depending on what is available / the system the package is being installed on). If I just have a simple Makevars containing PKG_LIBS= -lnag_nag -L/fserver/nagprod/FL22/fll6a22df/lib the package is built

Hi, I'm searching for a way to override the default CFLAGS/FFLAGS (-g -02 in my case) per package (e.g with "-g" for packages under development). PKG_CFLAGS/PKG_FFLAGS is prepended to the remaining flags, so it can't delete a globally set "-O2" flag. Of course I can edit the global Makeconf file, but I was wondering if there is a possibility to override variables from

Why is it that R places CFLAGS after PKG_CFLAGS and not before when compiling a package (e.g. through R CMD build pkg)? This can be problematic if, for instance, you want to use -O3, but -O2 is in R_HOME/etc/Makeconf. If -O2 (in CFLAGS) appears after -O3 (in PKG_CFLAGS), you are left with what you didn't want: -O2. In R-exts, it says that "Flags which are set in file etc/Makeconf

Hello, In the src folder of my R package I have a.cc b.cc f/g/x.cc my Makevars.in has all: $(SHLIB) upon installing only, a.o and b.o is build and the final dll is comprised of a.o and b.o How can I instruct $(SHLIB) to pick up its source files from all subdirectories (or maybe a subset, though here it will be all) in src ? Much thanks Saptarshi

In trying to compile a package with c code using Rtools, -O3 is added by default. This comes from Makeconf? Compiler flags (CFLAGS="-O0 -g" ) set in src/Makevars.win or src/Makevars appear before this. nm pkg.dll reveals no symbols! How can I compile a Windows package with "-O2 -g"? Thanks, RT -- View this message in context:

As a package author, it is in my opinion irresponsible to override these system settings (which is why it is also impossible). You have no idea what system it is being deployed on, I mean, you don't even know if the compiler is gcc. If a user wants (say) heavy optimization they will compile R with optimization. (For this reason I also don't think users should modify their ~/.R/Makevars,

Sometimes I find it useful to put C or Fortran sources under subdirs of "mypackage/src", especially to distinguish between my own files and e.g. lapack or blas sources. To get this working I would need a Makefile in my package which contains the appropriate dependencies to these sources in subdirs. But I don't want to add a complete Makefile, I want only a Makevars file containing

Hello, I'm using a Makevars.in file and running my code through gdb. I understand i should turn of -O2, but R's makeconf overrides my settings /ln/meraki/custom/lib64/R/etc/Makeconf:112: warning: overriding commands for target `.cc.o' in Makevars.in .cc.o: g++ -g ${PKG_CXXFLAGS} ${PKG_LIBS} ${RINC} ${RLIB} -c $< -o $@ Thank you S.

When I install an R package with cpp codes such as rrcov via CRAN (under R 3.1.1, using no Makevars file and under Ubuntu 14.04 using GCC 4.8), the cpp code is compiled with the -o3 flag (in fact, looking at the Makeconf file this seem to again be the default since R 3.1.1) But when I install my own package via CRAN it is compiled with the -o2 flag. My questions are what is causing my

On 27 September 2016 at 09:37, Eric Deveaud wrote: | Hello, | | I'm tring to install a Rpackage that holds some C//C++ code | | as far as I understood the R library generic compilation mechanism, | compilation of C//C++ sources is controled | | 1) at system level by the ocntentos RHOME/etc/Makeconf | 2) at user level by the content of ~/.R/Makevars | 3) at package level by the content

On Sun, 16 Mar 2003, Duncan Temple Lang wrote: > The "fix" is relatively simple. One can change the order of the > suffixes listed in $R_HOME/etc/Makeconf (i.e. the Makeconf.in version) > to alter the precedence. If one changes the line > > .SUFFIXES: .c .cc .cpp .C .d .f .lo .o > > to place the '.c' after the '.cc', your example will work as you

I sent the message below to r-sig-mac yesterday, but having no reply I decided to explore a bit myself and found that editing: /Library/Frameworks/R.framework/Versions/2.3/Resources/share/make/ shlib.mk yzzy: diff shlib.mk shlib.mk~ 3c3 < include $(R_HOME)/etc/Makeconf --- > include $(R_HOME)/etc${R_ARCH}/Makeconf restored the functionality of R CMD INSTALL. Is this a known issue?

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

On May 13, 2015, at 2:28 PM, Henrik Bengtsson <henrik.bengtsson at ucsf.edu> wrote: > While at it: 'Makevars' is an R invention (i.e. documentation of it > is only available through the R docs), correct? /Henrik > Well, it's just a Makefile fragment that gets included along with the rest of the Makefiles, so for all practical purposes it's just a Makefile which

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

R developers, On windows, it seems like R_HOME/etc/Makeconf has SHELL = /bin/sh instead of the location of Rtools' sh. I think this is because R_HOME/src/gnuwin32/fixed/etc/Makeconf needs to define SHELL as just sh (since Rtools/bin has to be on the PATH). This is of consequence with R CMD config. R version 2.7.0 Under development (unstable) (2007-10-19 r43218) Copyright (C) 2007 The R

Hi We are currently embedding a rather large C++ library in R (BioC), and we want some comments on the portability of how we have approach this. First of, we are not really able to do much about the portability of the basic library, which of course is the main question :) We have an approach which seems to work, I just want a bit of feedback on it.... The way we integrate it into R is

Read in the Windows release notes for 2.4.0 that: There is a new file etc/Makeconf that provides an approximation to the Unix version and may help with src/Makefile's. Yet when I look at the CRAN binary I have for 2.4.1patched, there are five files in the $R_HOME/etc directory, but no Makeconf. Is the file only available with custom installs?