On 19/04/10 10:41, Peter wrote: > On Sun, Apr 18, 2010 at 6:50 PM, Laurent Gautier<lgaut...@gmail.com> wrote: >> >>>>> Why isn't rpy2 checking the registry to find R (a regression from rpy1)? >>>> >>>> It does, but only at run time. >>>> >>>> Building is a more advanced operation (and I filtering candidate that can't >>>> edit the %Path% out ;-) ). >>> >>> Would you accept a patch to "fix" this? >> >> I have mixed feelings about it. A building machine may have several >> versions of R, and getting the R version automagically from the registry >> might become a headache. >> (I am considering that changing the %Path% is easier than modify the >> registry). > > Doing nothing is *much* easier than changing the path. More importantly > this covers the usual situation where there is one and only one version of > R installed, and it can be found via the registry.
Compiling R / rpy2 on windonws is nowhere near an "usual" situation, IMHO ;-) I am really reluctant to introduce anything that is not explicit or easy to tweek - and the registry does not qualify for any - > Also, because when you install R is sets the registry by default (you > can tell it not to), this typically means the last installed R is the default. > In normal use, this means the latest version of R. Easy :) > >> If there is a strong consensus against me for having it patched, I'd >> surrender ;-) > > OK. > >>> Any idea how calling "R CMD config --cppflags" behaved? That seems to >>> be the stumbling block at the moment and has nothing to do with Python >>> or the compiler for rpy2. It could be something funny on my machine... >> >> You need the R development toolkit (mingw and some unix tools). Check >> the R FAQ for Windows. > > You're right. I'd resolved this, I was missing make. With that installed > via cygwin doing "R CMD config --cppflags" and related calls works fine. > I sent some follow up emails about the next problems (using either the > MS compiler or mingw32) on 14 April. > > Thanks, > > Peter > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > rpy-list mailing list > rpy-list@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/rpy-list ------------------------------------------------------------------------------ _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
