Dear R developers, I am using R under Linux, but I would like to share an extension package with some Windows users. The package contains only data and .R scripts. There is no src directory. So, I think I do not need a Windows machine with C compiler, "make", "sh" and "perl". If I am wrong, please tell me. I tried the following approaches (after verifying the package using R CMD check - 1 warning concerning the missing documentation for some of the R-functions.) 1. Installing the source package (with no C, C++ or F files) directly on Windows XP. Installation complains that "make" command is mising. OK, it is a source package. 2. Building binary package using R CMD build --binary --use-zip on Linux and try to install it under Windows XP. Installation complains that "make" command is missing. (Why, if it is a binary package?). 3. Build the package from source on Windows XP using R CMD build <package>. Installation complains that "sh" is missing. (Why is it looking for "sh", if it is a properly working R installation under Windows?) 4. Install the package under Linux and zip the directory library/<package> and unzip it in the library directory on Windows machine. This works. The package behaves correctly. However, I do not think that this is a suggested method. Could you help me? Thank you in advance. Petr Savicky.
On Sat, 28 Apr 2007, Petr Savicky wrote:> Dear R developers, > > I am using R under Linux, but I would like to share > an extension package with some Windows users. The package > contains only data and .R scripts. There is no src directory. > > So, I think I do not need a Windows machine with C compiler, > "make", "sh" and "perl". If I am wrong, please tell me. > > I tried the following approaches (after verifying the package > using R CMD check - 1 warning concerning the missing documentation > for some of the R-functions.) > > 1. Installing the source package (with no C, C++ or F files) > directly on Windows XP. Installation complains that > "make" command is mising. OK, it is a source package. > > 2. Building binary package using R CMD build --binary --use-zip > on Linux and try to install it under Windows XP. Installation > complains that "make" command is missing. (Why, if it is > a binary package?).How did you try to install it? It is not a Windows binary package, but a Linux binary package.> 3. Build the package from source on Windows XP using > R CMD build <package>. Installation complains that "sh" > is missing. (Why is it looking for "sh", if it is a properly > working R installation under Windows?)Because you need more than R to install source packages on any platform. See the R-admin manual.> 4. Install the package under Linux and zip the directory > library/<package> and unzip it in the library directory > on Windows machine. This works. The package behaves > correctly. However, I do not think that this is a suggested > method.Well, it _is_ a suggested method: see README.packages. Another method open to you is to cross-build on Linux, also described in that document and in R-admin.html. You would need to do that is there is anything Windows-specific about the package. Note that none of these methods produce Windows-specific forms of help (and one of those is the default). The only way to do that is under Windows (including using Windows tools under emulations such as Wine on other OSes). -- Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595
On 4/28/2007 7:50 AM, Petr Savicky wrote:> Dear R developers, > > I am using R under Linux, but I would like to share > an extension package with some Windows users. The package > contains only data and .R scripts. There is no src directory. > > So, I think I do not need a Windows machine with C compiler, > "make", "sh" and "perl". If I am wrong, please tell me.Yes, you need the R tools and Perl. See the R Admin manual; it describes the necessary tools in the "Windows Toolset" appendix. Duncan Murdoch
If you want to build it on Windows (rather than do a cross build) there are links to HowTo's in the Links section of this page regarding various Windows tasks: http://code.google.com/p/batchfiles/ On 4/28/07, Petr Savicky <savicky at cs.cas.cz> wrote:> Dear R developers, > > I am using R under Linux, but I would like to share > an extension package with some Windows users. The package > contains only data and .R scripts. There is no src directory. > > So, I think I do not need a Windows machine with C compiler, > "make", "sh" and "perl". If I am wrong, please tell me. > > I tried the following approaches (after verifying the package > using R CMD check - 1 warning concerning the missing documentation > for some of the R-functions.) > > 1. Installing the source package (with no C, C++ or F files) > directly on Windows XP. Installation complains that > "make" command is mising. OK, it is a source package. > > 2. Building binary package using R CMD build --binary --use-zip > on Linux and try to install it under Windows XP. Installation > complains that "make" command is missing. (Why, if it is > a binary package?). > > 3. Build the package from source on Windows XP using > R CMD build <package>. Installation complains that "sh" > is missing. (Why is it looking for "sh", if it is a properly > working R installation under Windows?) > > 4. Install the package under Linux and zip the directory > library/<package> and unzip it in the library directory > on Windows machine. This works. The package behaves > correctly. However, I do not think that this is a suggested > method. > > Could you help me? > > Thank you in advance. Petr Savicky. > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel >
You can also use the Windows binary build and check service at http://129.217.207.166 after reading its disclaimer... Uwe Ligges Petr Savicky wrote:> Dear R developers, > > I am using R under Linux, but I would like to share > an extension package with some Windows users. The package > contains only data and .R scripts. There is no src directory. > > So, I think I do not need a Windows machine with C compiler, > "make", "sh" and "perl". If I am wrong, please tell me. > > I tried the following approaches (after verifying the package > using R CMD check - 1 warning concerning the missing documentation > for some of the R-functions.) > > 1. Installing the source package (with no C, C++ or F files) > directly on Windows XP. Installation complains that > "make" command is mising. OK, it is a source package. > > 2. Building binary package using R CMD build --binary --use-zip > on Linux and try to install it under Windows XP. Installation > complains that "make" command is missing. (Why, if it is > a binary package?). > > 3. Build the package from source on Windows XP using > R CMD build <package>. Installation complains that "sh" > is missing. (Why is it looking for "sh", if it is a properly > working R installation under Windows?) > > 4. Install the package under Linux and zip the directory > library/<package> and unzip it in the library directory > on Windows machine. This works. The package behaves > correctly. However, I do not think that this is a suggested > method. > > Could you help me? > > Thank you in advance. Petr Savicky. > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel