Possibly more of a legal question than a technical development question, but
here goes.
In the doc\COPYRIGHTS file it is made clear that the intention is that you can
write R packages and distribute them under licenses not compatible with GPL, by
making the relevant header files available und
nterface and wanting to link to that interface and whether the intention or
the actuality of the license allow that.
Thanks!
-Original Message-
From: r-devel-boun...@r-project.org [mailto:r-devel-boun...@r-project.org] On
Behalf Of Tom Quarendon
Sent: 03 August 2010 13:23
To: r-devel@r
Is there any way to print out the options that where passed to configure when R
was built?
I want to build a later version to the one I have on my machine, and I want to
build it in the same way, with the same configure options.
Thanks.
__
R-devel@r-p
2016 11:37
To: Tom Quarendon
Cc: r-devel@r-project.org
Subject: Re: [Rd] Return options used to configure R
A one liner that should work on most systems:
grep("configure", readLines(file.path(R.home(), "etc", "Makeconf")), value=TRUE)
Gabor
On Thu, Jan 21, 2016 at 5
nstalled that from a pre-built package. Ditto Windows.
-Original Message-
From: Dirk Eddelbuettel [mailto:e...@debian.org]
Sent: 22 January 2016 12:07
To: Tom Quarendon
Cc: Gábor Csárdi ; r-devel@r-project.org
Subject: Re: [Rd] Return options used to configure R
On 22 January 2016 at 11:40
