[Rd] Installing ROracle in windows.. Pls help
I have installed R 2.7.2 in windows, now i am trying to install R oracle... I am using Oracle 10g. i have downloaded the Roracle 0.5-9 sources, and i am trying to compile it using Vc++, i found from readme files and forum that, we need to use the makefile.win in the \src folder and nmake utility of vc++, since i have not worked with vc++, i don't have any idea , how to use the nmake utility, can anybody help me with the steps required in compiling the R oracle sources please.. ? Many thanks. -- View this message in context: http://www.nabble.com/Installing-ROracle-in-windows..-Pls-help-tp19916116p19916116.html Sent from the R devel mailing list archive at Nabble.com. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Installing ROracle in windows.. Pls help
You have already sent this to R-help, and neither that list nor this is the place to ask for help on VC++. Why do you need ROracle? Most Windows users find it much easier to access Oracle via RODBC, which builds out of the box and has a pre-compiled version on CRAN. On Fri, 10 Oct 2008, Rita. A wrote: I have installed R 2.7.2 in windows, now i am trying to install R oracle... I am using Oracle 10g. i have downloaded the Roracle 0.5-9 sources, and i am trying to compile it using Vc++, i found from readme files and forum that, we need to use the makefile.win in the \src folder and nmake utility of vc++, since i have not worked with vc++, i don't have any idea , how to use the nmake utility, can anybody help me with the steps required in compiling the R oracle sources please.. ? Many thanks. Well, the sources say this is documented in ROracle/src/Makefile.win (two versions, in fact). If that is over your head, I can only suggest that your company employs someone else to do this for you. -- Brian D. Ripley, [EMAIL PROTECTED] Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UKFax: +44 1865 272595 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] relative path to source files in vignette
Hi, this may be slightly off-topic, but as you are the experts: we have written a small vignette, in which we want to refer to .R, .Rd source files by means of relative paths. More specifically, we want to use TeX package "listings" to include source code, [which btw in the mean time works pretty well together with "fancyvrb" so can be used with Sweave without problems...] To avoid redundancy we would like to use \lstinputlisting[firstline=,lastline=]{} and to do so we somehow need path information. This is /not/ a "listings" issue, as we might also have used \input{}, only is \lstinputlisting a bit more flexible... Using relative paths, i.e. as the vignette resides in subfolder "inst/doc" something like ../../..//R/or ../../..//man/ does the job for both R CMD build and R CMD check , --- in standard configurations. However, as you may change the location of the check folder with the -o option of R CMD check, (and possibly other things, we have not yet thought of ...), our solution is not quite satisfactory, so we have been wondering whether there is a (platform-independent) way to access the package source folder (under check) from within TeX. --- or if you prefer to solve it from R-side: We would appreciate an Sweave-chunk to do the following: +have three arguments firstline, lastline, filename [where filename is relative to the package source folder] +read out the information about the path to the package source folder [from the env-variable?] +with this information read in the part of the source file between and and places this content ---without wrapping it to \begin{Schunk} ... \end{Schunk}--- into the .tex file ---preferrably already into a \begin{listing}\end{listing} environment... Any suggestions how to resolve this? Thank you already, Peter __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] relative path to source files in vignette
See ?system.file with the package= argument. On Fri, Oct 10, 2008 at 2:19 PM, Peter Ruckdeschel <[EMAIL PROTECTED]> wrote: > Hi, > > this may be slightly off-topic, but as you are the experts: > > we have written a small vignette, in which we want to refer to > .R, .Rd source files by means of relative paths. > > More specifically, we want to use TeX package "listings" to include > source code, > > [which btw in the mean time works pretty well together with "fancyvrb" > so can be used > with Sweave without problems...] > > To avoid redundancy we would like to use > > \lstinputlisting[firstline=,lastline=]{} > > and to do so we somehow need path information. > > This is /not/ a "listings" issue, as we might also have used > \input{}, only is \lstinputlisting a bit more > flexible... > > Using relative paths, i.e. as the vignette resides in subfolder "inst/doc" > something like > > ../../..//R/or ../../..//man/ > > does the job for both R CMD build and R CMD check , > --- in standard configurations. > > However, as you may change the location of the check folder with > the -o option of R CMD check, (and possibly other things, we have > not yet thought of ...), our solution is not quite satisfactory, > so we have been wondering whether there is a (platform-independent) > way to access the package source folder (under check) from within > TeX. > > --- or if you prefer to solve it from R-side: > > We would appreciate an Sweave-chunk to do the following: > +have three arguments firstline, lastline, filename > [where filename is relative to the package source folder] > +read out the information about the path to the package > source folder [from the env-variable?] > +with this information read in the part of the source file > between and > and places this content ---without wrapping it to > \begin{Schunk} ... \end{Schunk}--- into the .tex file > ---preferrably already into a \begin{listing}\end{listing} > environment... > > Any suggestions how to resolve this? > > Thank you already, > Peter > > __ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] relative path to source files in vignette
Gabor Grothendieck schrieb: > See ?system.file with the package= argument. > Thank you Gabor, but this refers to the /installed/ package, while we are needing path information about the not-yet-built source code of the package during R CMD check / build. Peter __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] relative path to source files in vignette
Try placing a copy of the files in the inst directory and then accessing them via system.files("myfile.R", package = "mypackage") or place them in the same directory as the Sweave file and then access them without a directory path at all: readLines("myfile.R") On Fri, Oct 10, 2008 at 2:48 PM, Peter Ruckdeschel <[EMAIL PROTECTED]> wrote: > Gabor Grothendieck schrieb: >> See ?system.file with the package= argument. >> > > Thank you Gabor, > > but this refers to the /installed/ package, while we are needing > path information about the not-yet-built source code of the > package during R CMD check / build. > > Peter > __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] relative path to source files in vignette
Thanks again Gabor, for your quick reply, > Try placing a copy of the files in the inst directory and then > accessing them via system.files("myfile.R", package = "mypackage") > you mean I should do this in an S-chunk in the .Rnw file? I.e., running Sweave on it would then produce the copy into my Sweave file I need? This could indeed be an opition, but as noted in my reply to Robert, my guess is that in the library where you install your packages to and which is found with system.file(), you will no longer find the R source files but rather some .rdb or .rdx file. At least this is what I found --- or is there some magic trick to get back the source files from this? > or place them in the same directory as the Sweave file > and then access them without a directory path at all: > readLines("myfile.R") > If I put the sources statically into the same directory as the Sweave file (i.e. in [...]/myRsources/myPkg/inst/doc), of course everything works fine; The issue is that I want to "dynamically" include parts of the source R code itself (without unnecessary static copying the source R code due to consistency traps, when changing the R code but not the copy) from the R directory of the package into the Sweave file by something like \input{[Path]/myRfile.R} so that once I change the R code, I do not have to change the .Rnw file. [I do not include the whole .R file but only certain lines of it, of course] As already said, in a standard configuration something like \input{../../../myPkg/R/myRfile.R} % goes from [...]/myRSources/myPkg/inst/src to [...]/myRSources/myPkg/R % in R CMD build % resp. from [...]/myRSources/myPkg.Rcheck/inst/src to [...]/myRSources/myPkg/R % in R CMD check does the job. Now if I am in [...]/myRSources and say something like R CMD build myPkg ### still works R CMD check myPkg -o /yetAnotherPath/myCheck ## does not work as /yetAnotherPath/myPkg/R need not be [...]/myPkg/R So what I was looking for was something like defining an environment variable $myRSources (in a platform-independent way) which may be accessed (in a platform-independent way) from the TeX command \input{...} --- perhaps with something like \input{$myRSources/myPkg/R/myRfile.R} but I cannot figure out how to do this... Thank you once again Peter __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] relative path to source files in vignette
On Fri, Oct 10, 2008 at 7:06 PM, Peter Ruckdeschel <[EMAIL PROTECTED]> wrote: > Thanks again Gabor, for your quick reply, >> Try placing a copy of the files in the inst directory and then >> accessing them via system.files("myfile.R", package = "mypackage") >> > you mean I should do this in an S-chunk in the .Rnw file? > I.e., running Sweave on it would then produce the copy into my Sweave file > I need? > > This could indeed be an opition, but as noted in my reply to Robert, my > guess > is that in the library where you install your packages to and which is > found with > system.file(), you will no longer find the R source files but rather > some .rdb > or .rdx file. At least this is what I found --- or is there some magic trick > to get back the source files from this? Yes, that is what occurs. That's why it was suggested to copy it. > >> or place them in the same directory as the Sweave file >> and then access them without a directory path at all: >> readLines("myfile.R") >> > If I put the sources statically into the same directory as the Sweave file > (i.e. in [...]/myRsources/myPkg/inst/doc), > of course everything works fine; > > The issue is that I want to "dynamically" include parts of the source > R code itself (without unnecessary static copying the source R code > due to consistency traps, when changing the R code but not > the copy) from the R directory of the package into the Sweave > file by something like > > \input{[Path]/myRfile.R} > > so that once I change the R code, I do not have to change > the .Rnw file. > > [I do not include the whole .R file but only certain lines of it, of course] > > As already said, in a standard configuration something like > \input{../../../myPkg/R/myRfile.R} > % goes from [...]/myRSources/myPkg/inst/src to [...]/myRSources/myPkg/R > % in R CMD build > % resp. from [...]/myRSources/myPkg.Rcheck/inst/src to > [...]/myRSources/myPkg/R > % in R CMD check > does the job. > > Now if I am in [...]/myRSources and say something like > > R CMD build myPkg ### still works > R CMD check myPkg -o /yetAnotherPath/myCheck > ## does not work as /yetAnotherPath/myPkg/R need not be [...]/myPkg/R > > So what I was looking for was something like defining an environment > variable > $myRSources (in a platform-independent way) > which may be accessed (in a platform-independent way) from > the TeX command \input{...} --- perhaps with something like > > \input{$myRSources/myPkg/R/myRfile.R} > > but I cannot figure out how to do this... > > Thank you once again > Peter > > Perhaps you should just preprocess your Sweave files prior to the build. The brew package could be used, for example. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel