Dear expeRts, I work on the R package "nacopula" (https://r-forge.r-project.org/projects/nacopula/) under Mac OS X 10.6.7 (MacBook Pro). The session info is: R version 2.14.0 Under development (unstable) (2011-05-02 r55730) Platform: x86_64-apple-darwin9.8.0/x86_64 (64-bit) When I apply "R CMD check nacopula" my source directory is filled with .o files (which leads to a warning for the next check). Further, if I use R 2.14.0, the check produces a file "nacopula-Ex.R" on the top level, i.e., where folders like R, src, tests, man, inst, and demo reside. Shouldn't the source directory stay nice-and-clean, without being filled with .o files and example files? Cheers, Marius Attachment: screen shot -------------- next part -------------- A non-text attachment was scrubbed... Name: screenshot.PNG Type: image/png Size: 44473 bytes Desc: not available URL: <https://stat.ethz.ch/pipermail/r-sig-mac/attachments/20110602/0ed30a8c/attachment-0001.png>
check leads to .o files and to packagename-Ex.R
3 messages · Benilton Carvalho, Marius Hofert
'R CMD check' should be applied on the .tar.gz, not on the source directory. So, it'd be something like: R CMD build pkg R CMD check pkg_version.tar.gz b
On 2 June 2011 06:54, Marius Hofert <m_hofert at web.de> wrote:
Dear expeRts, I work on the R package "nacopula" (https://r-forge.r-project.org/projects/nacopula/) under Mac OS X 10.6.7 (MacBook Pro). The session info is: R version 2.14.0 Under development (unstable) (2011-05-02 r55730) Platform: x86_64-apple-darwin9.8.0/x86_64 (64-bit) When I apply "R CMD check nacopula" my source directory is filled with .o files (which leads to a warning for the next check). Further, if I use R 2.14.0, the check produces a file "nacopula-Ex.R" on the top level, i.e., where folders like R, src, tests, man, inst, and demo reside. Shouldn't the source directory stay nice-and-clean, without being filled with .o files and example files? Cheers, Marius Attachment: screen shot
_______________________________________________ R-SIG-Mac mailing list R-SIG-Mac at r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-mac
Successful people ask better questions, and as a result, they get better answers. (Tony Robbins)
Dear Benilton, thanks, that solved all issues. Cheers, Marius
On 2011-06-02, at 12:47 , Benilton Carvalho wrote:
'R CMD check' should be applied on the .tar.gz, not on the source directory. So, it'd be something like: R CMD build pkg R CMD check pkg_version.tar.gz b On 2 June 2011 06:54, Marius Hofert <m_hofert at web.de> wrote:
Dear expeRts, I work on the R package "nacopula" (https://r-forge.r-project.org/projects/nacopula/) under Mac OS X 10.6.7 (MacBook Pro). The session info is: R version 2.14.0 Under development (unstable) (2011-05-02 r55730) Platform: x86_64-apple-darwin9.8.0/x86_64 (64-bit) When I apply "R CMD check nacopula" my source directory is filled with .o files (which leads to a warning for the next check). Further, if I use R 2.14.0, the check produces a file "nacopula-Ex.R" on the top level, i.e., where folders like R, src, tests, man, inst, and demo reside. Shouldn't the source directory stay nice-and-clean, without being filled with .o files and example files? Cheers, Marius Attachment: screen shot
_______________________________________________ R-SIG-Mac mailing list R-SIG-Mac at r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-mac
-- Successful people ask better questions, and as a result, they get better answers. (Tony Robbins)