R-alpha: Re: R-beta: R FAQ v0.60

Kurt Hornik Kurt.Hornik@ci.tuwien.ac.at
Thu, 11 Dec 1997 09:31:51 +0100

>>>>> Paul Gilbert writes:

> I've been reviewing how the make process for my library should be set
> up and I noticed that the "How Can I Create an R Package?" part of the
> FAQ gives instructions to put a Makefile in pkg/src but the "How Can
> Add-on Packages Be Installed?" part of the FAQ does not seem to give
> any indication that a make may be necessary, unless
>      $ R INSTALL pkg lib
> does a make, which I don't think it does.

> Also, this Makefile has to be passed config information, so it must be
> called some way from the main R Makefile I think, but I don't see
> exactly how this is suppose to work, especially if the library is not
> under R/library. Can someone explain this?

Thomas already answered the above.

> A related question is that I am looking for a general strategy for
> distributing code which may get installed under R or S. To date, I
> have been working with one Makefile, which has different targets for R
> or for S. Obviously, the procedure for installing this is not quite as
> simple as suggested for add on packages in the FAQ. Does anyone have
> suggestions for a good way to organize this?

Under R, you need to organize everything as detailed in the FAQ.  There
is no need for a top-level Makefile, so you could use this for taking
care of the R- (S) part [having hinstall and qinstall or whatever they
are called targets].

However, keep in mind that in the long run, all R SOURCE files will need
to have a `.R' extension (as of 0.60, this is already a must for data).

r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch