Displaying 20 results from an estimated 30000 matches similar to: "build packages with vignettes in Windows"
2006 Feb 08
2
Compiling errors for Matrix_0.995-5.tar.gz under XP
I installed the MinGW-5.0.0 compilers today (gcc-3.4.2 is now contained in the 'Current' distribution. When the current compilers failed to compile the referenced Matrix update and not knowing how to check the exact version numbers for individual files, I applied the Id.exe and f771.exe fixes from the 'Building R for Windows' page (http://www.murdoch-sutherland.com/Rtools/#ldbug).
2007 Sep 07
1
Rcmd install on Vista
Has anyone successfully used Rcmd install or Rcmd check on
Windows Vista? I have been successfully been running R itself,
just not Rcmd install and Rcmd check.
Rcmd check fails, the Ryacas.Rcheck it creates is
read-only, I don't have permission to delete it and I have
to reset the permissions on it just to delete it.
With Rcmd install I am getting the following which looks like I
am running
2007 May 11
1
Compilation of source package.
I have a samll package that works well and complies nicly on WinXP,
using R-2.4.1
Now I want to add a document so i make a folder inst\doc and put the
.tex and .pdf in there.
But the complation then crashes. Is this because the installin expects
some file to be present in inst if an inst folder is there?
This is how the thing progress is on my command promp:
2013 Apr 21
2
vignettes: problems with PDF compaction
[Env: OS: Win Xp; R 2.15.2; IDE: eclipse/StatET]
Each time I update my heplots package, I get warnings from R CMD check
on R-Forge,
* checking sizes of PDF files under ?inst/doc? ... WARNING
?gs+qpdf? made some significant size reductions:
compacted ?HE-examples.pdf? from 739Kb to 366Kb
and upon submission to CRAN, a message from maintainers:
On CRAN now: but again there were warnings
2007 Oct 09
2
Package compile under Windows on 2.6.0
Dear all,
We are experiencing some trouble when compiling R packages using R
2.6.0 and the new Rtools installer under Windows XP.
(1) First, compiling any package using the new setup stops with an
errorrelated to some "/" issue on the inst folder. This folder only
contains a CITATION file
---------- Making package FLCore ------------
adding build stamp to DESCRIPTION
installing
2008 Dec 07
1
Compile Packages on vista
Hi
I''m trying to compile R packages on my vista (I''m very new on vista...). I
installed Rtools, RExcel on a specific folder: c:\Rtools and gave full
access. Unfortunately, I am still unable to compile any packages (may be
still because of the security properties of vista). I checked several
mailing list/forums/website but I did not found any solution. Does anybody
have the
2008 Sep 16
2
odesolve dynload example
Hello R Developers,
This is my first foray into using c-code with R, so please forgive my
foolishness.
I had a look at the archives and did not find anything on this, so
hopefully I am not doubling up.
I have tried to use R cmd to create an object file from the odesolve
dynload example.
I am using windows and have just installed rtools, and have the latest
version of stable R (2..7.2).
This is
2004 Nov 11
2
inst/CITATION produced error during Rcmd check <package>
Dear list member,
by running Rcmd check on a package where a customised 'CITATION' file should
be included instead of the automatically produced one, the following error
occurs:
adding build stamp to DESCRIPTION
installing NAMESPACE file and metadata
installing R files
installing inst files
FIND: Parameter format not correct
make[2]: *** [c:/R/packages/urca/inst] Error 2
make[1]:
2004 Dec 22
2
Creating packages in windoze: *** [indices] Error 1
Dear R community,
I am running R 2.0.1 on a Windoze XP OS. I recently upgraded from R 1.9x to
2.0.1 and I am currently
upgrading a my personal function packages. My other packages compiled
without
a hitch but I am having a difficult time with my largest package.
Can someone please help me with the following error message
"Error in parse(file, n, text, prompt) : syntax error on line
2011 Mar 30
1
R CMD build processes inst/doc/Makefile only if there are vignette files?
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,
2010 Sep 15
1
running 'make' failed during vignette creation ('R CMD build') on Windows
Hi,
This is a follow-up to the problem reported here:
https://stat.ethz.ch/pipermail/r-devel/2010-September/058460.html
After I updated R-2.12 to 2010-09-13 r52905 on the Bioc build system,
some of the packages that have a Makefile in <pkg>/inst/doc still
don't build on Windows. For example, 'R\bin\R.exe CMD build adSplit'
gives:
* checking for file
2003 Jun 02
6
Building an R package under Windows NT
I am trying to build a R 1.7 package under Windows NT. I created the
DESCRIPTION file, the RD file and added the code to the R folder. I also
downloaded and installed the Rtools package and have Perl 5.0. I know that
Perl, Miktex, and gcc are working. I also have my PATH variable set
correctly. I can fake install my package by removing the *.R from the code
file, using Rcmd Rdconv to create
2004 Jun 15
1
building R libraries (windows) - R CMD check problems
Hi everyone,
I am trying to build a R library called nnNorm but I have some troubles
checking and installing it.
Here is the setup:
If I don't use a inst\doc directory(with the vignettes files) in my source,
the install step is working fine:
C:\test>RCMD INSTALL nnNorm
---------- Making package nnNorm ------------
adding build stamp to DESCRIPTION
installing R files
installing
2011 Feb 25
1
R CMD build error (RProtoBuf on windows)
Hello all,
I am trying to port the package RProtoBuf to windows. The developers of RProtoBuf have given me some helpful pointers so far, but now I am stuck.
After having made what I think are the necessary changes to the package to compile on windows, "R CMD build RProtoBuf" outputs a somewhat cryptic error ("This application has requested the Runtime to terminate it in an unusual
2008 Jan 21
1
Adding an Sweave Vignette to a package
I'm finalizing development of a package that will include a vignette.
Without the vignette, the package builds fine with no warnings and is
ready for distribution. Now, I am following the directions for
developing vignettes "Sweave, Part II: Package Vignettes" by Friedrich
Leisch.
I am using a windows XP machine (other session info below). Here is what
I have done.
1) I add the
2008 May 06
2
gfortran: Command not found
Hi, All:
How do I get information about the "R CMD check / build / install"
process, especially regarding what software to install and how to
configure it under Windows XP?
I ask, because "R CMD check" complained, "gfortran: Command not
found". I found 'gfortran-sjlj.exe' in 'C:\Program
Files\R\Rtools\MinGW\bin', which is in the
2011 Jun 06
1
Log file of building vignette in RCMD check
Hello,
I am trying to run "RCMD check" on a package. It performs OK, with the exception of a single warning:
* checking package vignettes in 'inst/doc' ... WARNING
Package vignette(s) without corresponding PDF:
AnnotationFuncsUserguide.Rnw
As I understand the problem, the vignette is not built. However, I have no problems in doing so manually.
How do I fix this problem? I
2007 Nov 30
1
Puzzling message: "no man files in this package"
Dear R developers,
When building/checking my package (in R 2.6.1 under windows) I run into
some messages that I do not completely understand and that do not give
me precise enough leads to pinpoint where the error in my package is. I
would be very grateful for any suggestions. Did anyone else encounter
the same problem before?
When building or installing the package, I get the message (no error
2013 Sep 17
2
processing of /vignettes and /inst/doc
It is stated in R-exts that Sweave files (.Rnw) are either processed in
/vignettes or /inst/doc, not both. Furthermore, it is stated that external
manuals and other files in /inst/doc will be installed.
This behaviour has been used to deal with the situation where a package has
two "vignettes", one that is easily processed and one that has a long
running time. This could be done by
2018 Sep 20
3
future time stamps warning
Time stamps are correct and my system time is correct.
I am now tried to use Sys.setFileTime() to update time stamps as proposed.
This does not help.
The windows and debian builds give different reports on the time stamp
issue.
https://win-builder.r-project.org/incoming_pretest/eurostat_3.2.8_20180920_122655/Windows/00check.log