From ggrothendieck at gmail.com  Sun Sep 16 15:33:15 2007
From: ggrothendieck at gmail.com (Gabor Grothendieck)
Date: Sun, 16 Sep 2007 09:33:15 -0400
Subject: [Rd] r cmd build
In-Reply-To: <46ED27B7.2090804@stats.uwo.ca>
References: <971536df0709151927n494600bdx4c36b12c11cfc315@mail.gmail.com>
	<46ED27B7.2090804@stats.uwo.ca>
Message-ID: <971536df0709160633ybf2064y3c7b9e736c9561c5@mail.gmail.com>

The Writing Extensions manual says to do an R CMD build for releases
to CRAN.  That's what I have been doing and that does produce a .tar.gz
file even though I get a message about hhc.exe.  Is that what I should continue
to do and ignore the message or should I be using one of the alternatives
you mention to create a .tar.gz release file on Vista?

On 9/16/07, Duncan Murdoch <murdoch at stats.uwo.ca> wrote:
> On 15/09/2007 10:27 PM, Gabor Grothendieck wrote:
> > On Windows Vista hhc.exe is not available.  One can do this on an
> > install:
> >
> > rcmd install --docs=normal myPackage
> >
> > to avoid the message about hhc.exe; however,
> > "rcmd build" does not appear to support --docs=normal so one cannot
> > do a build without getting a message about hhc.exe (although the build
> > still proceeds).
>
> Are you talking about "build --binary"?  I recommend using "install
> --build" instead.  AFAIK a non-binary build doesn't make any use of hhc.
>
> Another way to do an install or build without getting that message is to
> indicate in src/gnuwin32/MkRules that you don't want to build CHM help.
>
> Duncan Murdoch
>



[Rd] r cmd build
Gabor Grothendieck