From bbolker at gmail.com  Thu Jun  2 16:13:59 2011
From: bbolker at gmail.com (Ben Bolker)
Date: Thu, 02 Jun 2011 10:13:59 -0400
Subject: [Rd] [R-SIG-Mac] check leads to .o files and to packagename-Ex.R
In-Reply-To: <4DE78C37.2080101@gmail.com>
References: <4A83757C-12EB-4F53-8C26-D23BC7C256D8@web.de>	<BANLkTinvZG=LCadGAienYSRpZu+4BvwV8w@mail.gmail.com>
	<4DE78AC9.7000809@gmail.com> <4DE78C37.2080101@gmail.com>
Message-ID: <4DE79AA7.9040706@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/02/2011 09:12 AM, Duncan Murdoch wrote:
> On 11-06-02 9:06 AM, Ben Bolker wrote:
>> On 06/02/2011 06:47 AM, Benilton Carvalho wrote:
>>> 'R CMD check' should be applied on the .tar.gz, not on the source
>>> directory.
>>
>>    Why?
> 
> Because that is what you will send to others.  The reason to check a
> directory instead of a tar file is to save time:  you don't need to
> recompile all the files, as a normal check does.
> 
>   The help says: "Check R packages from package sources, which can
>> be directories or package 'tar' archives with extension '.tar.gz',
>> '.tar.bz2' or '.tgz'."  I just skimmed through the relevant section
>> (1.3.1) in the R Extensions manual, and it doesn't say anything about
>> running on tarballs being preferred.
>>
>>    Add my vote to the wishlist that the src directory should get cleaned
>> after R CMD check.
> 
> Then the advantage of checking a directory would be lost.
> 
> Duncan Murdoch

  OK, that makes sense.  The logic was not clear to me.
  Do you know offhand if R CMD check uses "make"-like logic to determine
whether the sources should be recompiled even if there are existing
.o/.so files, or is that up to the user ... ?

  Ben
> 
>>
>>    Ben Bolker
>>
>>>
>>> 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
>>>>
>>>>
>>>
>>>
>>>
>>
>> ______________________________________________
>> R-devel at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3nmqcACgkQc5UpGjwzenOP7wCeJ/qoUed60giuBeBrJm3jiHhm
DRUAoIXl8cZE9f3TMpJ909puSgSgE8ZJ
=9zaZ
-----END PGP SIGNATURE-----



[Rd] [R-SIG-Mac] check leads to .o files and to packagename-Ex.R
Ben Bolker