R on Unix can be run from where it is built, and I frequently move where
it is built/change symbolic links. You definitely do not want where it is
going to be installed, as make check is run where it is built (not that
that matters when the R(.sh) scripts sets R_HOME).
On Sun, 30 Nov 2003, Sim
On Nov 29, 2003, at 9:33 PM, Prof Brian Ripley wrote:
On Sat, 29 Nov 2003, Simon Urbanek wrote:
BTW: This is not Mac specific - I was fighting this on Windows (and
unix for that matter) as well - it is possible to run an .exe linked
to
R.dll from anywhere, if R.dll is in the PATH. But then, one
On 30 Nov 2003, Peter Dalgaard wrote:
> Prof Brian Ripley <[EMAIL PROTECTED]> writes:
>
> > On Sat, 29 Nov 2003, Simon Urbanek wrote:
> >
> > > The current R needs R_HOME to be set before using it even in its
> > > embedded form. Now this defeats the idea of location independence of
> > > the
Prof Brian Ripley <[EMAIL PROTECTED]> writes:
> On Sat, 29 Nov 2003, Simon Urbanek wrote:
>
> > The current R needs R_HOME to be set before using it even in its
> > embedded form. Now this defeats the idea of location independence of
> > the framework. The application doesn't have to care wheth
On Sat, 29 Nov 2003, Simon Urbanek wrote:
> The current R needs R_HOME to be set before using it even in its
> embedded form. Now this defeats the idea of location independence of
> the framework. The application doesn't have to care whether the
> framework is in /Library/Frameworks, ~/Library/
After the recent discussion about future direction of the Mac OS X
port, I was toying with the idea to make R a proper Mac OS X framework.
There are several advantages: OS X locates frameworks automatically,
therefore any program wishing to link against R has only to specify
"-framework R" at l
