similar to: Avoid re-building a vignette

Context: R2.15-0 on Ubuntu. 1. I get a WARNING from CMD check for "Package vignette(s) without corresponding PDF: In this case the vignettes directory had both the pdf and Rnw; do I need to move the pdf to inst/doc? I'm reluctant to add the pdf to the svn source on Rforge, per the usual rule that a code management system should not have both a primary source and a object

I'm having a problem rebuilding a package, new to me in R 2.15.0 (Linux) It hits all that contain the line \usepackage[pdftex]{graphics} and leads to the following when running R CMD check on the directory. (I do this often; a final run on the tar.gz file will happen before submission.) Since I float and resize my figures, removing the line is fatal in other ways.

Dear colleagues, I am having issues trying to build a R package I recently wrote. I am using R 2.14.0 and my package depends on another package called aod. Running: R CMD Sweave vignette.Rnw is perfectly fine and the vignette compiles properly. but when I use R CMD build mypackage to build the tar.gz I get the following error: * installing the package to re-build vignettes * creating

I'm putting together an R package. I would like to show example code in the vignette, where example data files (included in the package) are used to generate an (example) output file. I read about using example data in Hadley Wickham's post ( http://r-pkgs.had.co.nz/data.html), and believe I should keep my example data as raw data, as it must be parsed to generate the output. So, I

Dear R-devel, Question: How can I get Sweave to recognize that the \thebibliography section is already created and generate the vignette pdf with a single pass? Or is there a way to let R CMD build know that Sweave needs to be run twice? If (1) is not possible, any suggestions how to auto-generate a crude generic bibtex .bib file from my existing document? Background: I maintain

Hi, in Section 'Writing package vignettes' of 'Writing R Extensions' it says: "Whenever a Makefile is found, then R CMD build will try to run make after the Sweave runs, so PDF manuals can be created from arbitrary source formats (plain LaTeX files, ...). [...] Note that the make step is executed even if there are no files in Sweave format, [...]". In my package,

Dear Duncan, The UTF-8 characters aren't properly rendered in the pdf version of the vignette. $?? ????? ?????? ?????? ????? ?? ?? is rendered as $????? ?????????? ???????????? ????? ?????? ? ???????? ???????? The same problem occurs when I use render("vignette.md", output_format = "mypackage::mystyle"), instead of render("vignette.md", output_format =

Dear R-helpers, www.statistik.lmu.de/~*leisch*/*Sweave*/*Sweave*-Rnews-2003-2.pdf says that R CMD build creates the pdf from a .Rnw file. But when I do R CMD build followed by R CMD check it gives me a warning that there is a vignette without a PDF. My query is : when R CMD build works it creates a pdf in the doc subdirectory of the directory returned by system.file(package = mypackage) and not

A few things to clarify: 1. You do not necessarily have to keep the \usepackage{} line if you use %\VignetteEncoding{UTF-8}, because Pandoc will use UTF-8 anyway in its LaTeX template. 2. Perhaps the vignette engine in R has done something clever to convert utf8 to UTF-8, but I'd recommend %\VignetteEncoding{UTF-8} instead of %\VignetteEncoding{utf8} to make sure it is a valid encoding name,

[Env: Win Xp / StatET 2.0 / R 2.15.0] In my heplots package I extended the HE-examples.Rnw vignette under inst/doc. The package passes R CMD check on my machine: * using log directory 'C:/eclipse-3.7/heplots.Rcheck' * using R version 2.15.0 (2012-03-30) * using platform: i386-pc-mingw32 (32-bit) ... * checking sizes of PDF files under 'inst/doc' ... OK * checking installed files

hi all - i'm trying to 'R CMD build' a package, but i have what appears to be a bootstrapping problem: i've included a vignette in my package, with R code interwoven (and built using Sweave), but in this documentation i have a code line: > library(MyPackage) now, when trying to build a .tar.gz install-able version of my package in a clean state, i remove the original

In a package 'vig' R CMD build vig (or tools::buildVignettes(dir="vig") with $ cat vig/vignettes/vig1.Rnw \documentclass{article} \begin{document} <<>>= x <- 1 @ \end{document} $ cat vig/vignettes/vig2.Rnw \documentclass{article} \begin{document} <<>>= x @ \end{document} produces vig2.pdf where x is defined with value 1 -- the vignettes share a build

I haven't figured it out entirely, but it looks like there are a couple of small glitches with knitr-based vignettes and SweaveParseOptions. I posted the tarball of a package with a knitr vignette with (as far as I can tell) everything properly coded in the DESCRIPTION file (VignetteBuilder: knitr, Suggests: knitr) and the vignette itself (%\VignetteEngine{knitr::knitr}). When Windows

Dear all, I'm trying to use a Markdown vignette with UTF-8 encoding. It compiles well when knitting the vignette in RStudio, but it fails to recognize the UTF-8 settings when building the source package. Can someone point out what I'm doing wrong? I tried to put the relevant information below. Best regards, Thierry Details: Using 64-bit R 3.1.2 with encoding = "native.enc"

Is there a way to include the compiled version of a vignette in the doc directory but mark it to NOT be rerun by CRAN??? I think I remember that this is possible, but have forgotton how.?? (It might even be a false memory.) Terry T. Background:? Beth Atkinson and I are splitting out many of the vignettes from the survival package into a separate package survivalVignettes.? There are a few

Dear list, we have a markdown vignette for our package in vignette/vignette.md This is not visible from within R with the vignette(package = "mypackage") command. I assume the reason is that the vignette function only shows PDF vignettes. Is there any way to circumvent this and display markdown vignettes directly from within R? I tried to seek the answer from R archives and search

I have packages where I know CRAN and other test platforms do not have all the resources to build the vignettes, for example, access to databases. Previously I think putting BuildVignettes: false in the DESCRIPTION file resolved this, by preventing CRAN checks from attempting to run the vignette code. (If it was not this, then there was some other magic I don't understand.) Now, when

Some questions motivated by this discussion. From the CRAN policy page: "Checking the package should take as little CPU time as possible, as the CRAN check farm is a very limited resource and there are thousands of packages. Long-running tests and vignette code can be made optional for checking, but do ensure that the checks that are left do exercise all the features of the

I want to include a vignette with a package I wrote. I did follow the "Writting R extentions" document step by step, but went I run "Rcmd build", an error occurs. It goes like this: " * creating vignettes ... ERROR . . . . :7: Emergency stop L7L ==> Fatal error occurred, no output PDF file produced!texify: pdflatex failed for some reason <see log file>.

I apologize that these questions are stupid and literal. I write to ask for clarification of comments in the R extensions manual about vignettes. I'm not great at LaTeX, but I'm not a complete novice either, and some of the comments are puzzling to me. 1. I'm stumbling over this line: "Make sure all files needed to run the R code in the vignette (data sets, ...) are accessible