While at it: 'Makevars' is an R invention (i.e. documentation of it is only available through the R docs), correct? /Henrik
On Wed, May 13, 2015 at 10:10 AM, Kevin Ushey <kevinus...@gmail.com> wrote: > One other solution that's only a little crazy: you could have a R > function within your package that generates the appropriate (portable) > Makevars, and within the package `configure` script call that > function. For example" > > R --vanilla --slave -e "source('R/makevars.R'); makevars()" > > And that 'makevars()' function could generate portable > 'Makevars(.win)' files for your package. > > Kevin > > On Wed, May 13, 2015 at 9:08 AM, Gábor Csárdi <csardi.ga...@gmail.com> wrote: >> On Wed, May 13, 2015 at 12:05 PM, Jan van der Laan <rh...@eoos.dds.nl> >> wrote: >> [...] >> >>> Too bad. Since it is only a handful of files, I will probably move them >>> directly into the src directory and prefix them. It would have been nice to >>> have been able to keep them separate. >>> >> >> If it is a couple of files, then you can also just list them in SOURCES (or >> even just OBJECTS, with a .o suffix), and leave them where they are. >> >> Gabor >> >> [...] >> >> [[alternative HTML version deleted]] >> >> ______________________________________________ >> 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 ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel