Hello, I have written my own very simple package. On an Apple, I was able to run through the "R CMD build" and "R CMD check" successfully. I have also installed the package, and successfully loaded the library on my Apple. This package is written entirely in R and requires no compilation. I am trying to move the package to a Windows machine. I (perhaps naively) thought, given that it contains no code requiring compilation, that I should just be able to take the .tar.gz file and directly install it in Windows. This didn't work. Nor did "translating' the contents of the .tar.gz file into a .zip file. I was about to provide the errors, but more googling on this issue suggests that maybe what I'm trying to do is impossible. Do I really have to "build" on a Windows box ... even when the package requires no compilation? Is there no simple translation tool available for this case? thank you, Daryl U. Washington Biostatistics
issue building my own package... moving from Apple OS to Windows
5 messages · ronggui, Uwe Ligges, Daryl Morris
Yeah, you have to build a binary package for windows, unless you just want to simply source all the functions into R. 2009/4/24 Daryl Morris <darylm at u.washington.edu>:
Hello, I have written my own very simple package. ?On an Apple, I was able to run through the "R CMD build" and "R CMD check" successfully. ?I have also installed the package, and successfully loaded the library on my Apple. This package is written entirely in R and requires no compilation. I am trying to move the package to a Windows machine. I (perhaps naively) thought, given that it contains no code requiring compilation, that I should just be able to take the .tar.gz file and directly install it in Windows. ?This didn't work. ?Nor did "translating' the contents of the .tar.gz file into a .zip file. I was about to provide the errors, but more googling on this issue suggests that maybe what I'm trying to do is impossible. Do I really have to "build" on a Windows box ... even when the package requires no compilation? ?Is there no simple translation tool available for this case? thank you, Daryl U. Washington Biostatistics
______________________________________________ R-help at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
HUANG Ronggui, Wincent PhD Candidate Dept of Public and Social Administration City University of Hong Kong Home page: http://asrr.r-forge.r-project.org/rghuang.html
Daryl Morris wrote:
Hello, I have written my own very simple package. On an Apple, I was able to run through the "R CMD build" and "R CMD check" successfully. I have also installed the package, and successfully loaded the library on my Apple. This package is written entirely in R and requires no compilation. I am trying to move the package to a Windows machine. I (perhaps naively) thought, given that it contains no code requiring compilation, that I should just be able to take the .tar.gz file and directly install it in Windows. This didn't work. Nor did "translating' the contents of the .tar.gz file into a .zip file. I was about to provide the errors, but more googling on this issue suggests that maybe what I'm trying to do is impossible. Do I really have to "build" on a Windows box ... even when the package requires no compilation? Is there no simple translation tool available for this case?
You need to INSTALL a source package (that has been build) as on any other platform. How to colect the tools in order to make R CMD INSTALL work under Windows (and other OSs) is described in the R Installation and Administration manual. Best, Uwe Ligges
thank you, Daryl U. Washington Biostatistics
______________________________________________ R-help at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Thanks for the various responses. It was easier than I thought to get all the tools together and setup Windows paths for the build process. I've been successful now on Windows. BUT... how do I make a package which DOES NOT require R CMD INSTALL to install? Obviously, it should not be required for everyone to have Perl on their Windows box to install a package. When I tried to install the .tar.gz file from the GUI, I got the same errors as I did when I used the version I had built on my Apple. Error in gzfile(file,"r") : cannot open the connection In addition: Warning messages: 1: In unzip(zipname, exdir=dest) :error 1 in extracting from zip file 2: In gzfile(file,"r"): cannot open compressed file 'multgeneriskpredperf_1.0.tar.gz/DESCRIPTION', probable reason 'No such file or directory' Thanks, Daryl
Uwe Ligges wrote:
You need to INSTALL a source package (that has been build) as on any other platform. How to colect the tools in order to make R CMD INSTALL work under Windows (and other OSs) is described in the R Installation and Administration manual. Best, Uwe Ligges
1 day later
Daryl Morris wrote:
Thanks for the various responses. It was easier than I thought to get all the tools together and setup Windows paths for the build process. I've been successful now on Windows. BUT... how do I make a package which DOES NOT require R CMD INSTALL to install? Obviously, it should not be required for everyone to have Perl on their Windows box to install a package.
Well, you can build a binary bundle for Windows (as it happens on CRAN), then just you (but not your users) need the tools installed. Best, Uwe
When I tried to install the .tar.gz file from the GUI, I got the same errors as I did when I used the version I had built on my Apple. Error in gzfile(file,"r") : cannot open the connection In addition: Warning messages: 1: In unzip(zipname, exdir=dest) :error 1 in extracting from zip file 2: In gzfile(file,"r"): cannot open compressed file 'multgeneriskpredperf_1.0.tar.gz/DESCRIPTION', probable reason 'No such file or directory' Thanks, Daryl Uwe Ligges wrote:
You need to INSTALL a source package (that has been build) as on any other platform. How to colect the tools in order to make R CMD INSTALL work under Windows (and other OSs) is described in the R Installation and Administration manual. Best, Uwe Ligges