I believe that was my boneheaded error.. checking now.. Yup
Thanks guys!
On Fri, Aug 17, 2012 at 3:01 AM, Uwe Ligges wrote:
>
>
> On 17.08.2012 07:24, steven mosher wrote:
>
>> " R CMD build is how you preferably should be creating your package tar
>> ball, so you simply add the --resave-data a
Under ?data
package: a character vector giving the package(s) to look in for data
sets, or 'NULL'.
By default, all packages in the search path are used, then
the 'data' subdirectory (if present) of the current working
directory.
which I think is accurate
Thank you, that is very helpful.
On 17 Aug 2012, at 12:58, Prof Brian Ripley wrote:
> What you have not told us is your platform (but it was Mac OS X the other
> day). The answers are different if you are doing source installs or binary
> installs and if the latter, by platform.
Apologies for
Ah I see! Had not thought of that solution.
(This is the first time I have tried to use autoconf and configure)
Many thanks.
Erika
On 17 Aug 2012, at 13:04, Dirk Eddelbuettel wrote:
>
> On 17 August 2012 at 11:44, Cule, Erika wrote:
> | If so, I still don't understand what happens when I comp
On 17 August 2012 at 11:44, Cule, Erika wrote:
| If so, I still don't understand what happens when I compile the package if
GSL is not installed on the computer, as there will still be C code in the src
directory.
That is precisely the use case for autoconf et al.
You test if something (here G
What you have not told us is your platform (but it was Mac OS X the
other day). The answers are different if you are doing source installs
or binary installs and if the latter, by platform.
If you are doing source installs on the machine to be used, configure
should adjust the install accordi
On 17.08.2012 13:49, Cule, Erika wrote:
But will package compilation fail if GSL is not installed?
No, not this way: since the gsl package can be in the Suggests now
(rather than the Depends).
Best,
Uwe Ligges
(There are files in the src directory that are needed for the code to run)
But will package compilation fail if GSL is not installed?
(There are files in the src directory that are needed for the code to run)
On 17 Aug 2012, at 12:47, Uwe Ligges wrote:
>
>
> On 17.08.2012 13:44, Cule, Erika wrote:
>> Thanks Uwe
>>
>> I am not quite sure I understand.
>>
>> To clar
On 17.08.2012 13:44, Cule, Erika wrote:
Thanks Uwe
I am not quite sure I understand.
To clarify, do you mean writing my R functions as something like:
functionRequiringGsl <- function(arg1, arg2)
{
if(require(gsl))
{
## Some functions that use GSL
Thanks Uwe
I am not quite sure I understand.
To clarify, do you mean writing my R functions as something like:
functionRequiringGsl <- function(arg1, arg2)
{
if(require(gsl))
{
## Some functions that use GSL
## called using .C()
} else {
On 17.08.2012 11:11, Cule, Erika wrote:
I have written an R package which contains C source code (in the directory
pkg/src).
Only a subset of the functions in the pkg/R directory contain a .C() call to
the functions in the pkg/src directory. The rest of the package will still work
and be us
I have written an R package which contains C source code (in the directory
pkg/src).
Only a subset of the functions in the pkg/R directory contain a .C() call to
the functions in the pkg/src directory. The rest of the package will still work
and be useful without the functions containing a .C(
On 17.08.2012 07:24, steven mosher wrote:
" R CMD build is how you preferably should be creating your package tar
ball, so you simply add the --resave-data argument to your already existing
R CMD build call which creates the tar ball from your source directory. So
can you elaborate on "doesn't
13 matches
Mail list logo
