[R-pkg-devel] Making adjustments to the R CMD check/install commands
erinm@hodge@@ @ending from gm@il@com
Tue Aug 28 01:00:05 CEST 2018
Yay! I got it to work! I used the ~/.R/Makevars, and all is well.
Erin Hodgess, PhD
mailto: erinm.hodgess using gmail.com
On Mon, Aug 27, 2018 at 2:29 PM Kevin Ushey <kevinushey using gmail.com> wrote:
> Hi Erin,
> The R extensions manual should be helpful here -- in particular, see the
> sections on the 'src/Makevars' file and configuration of the Fortran
> In particular, in your 'src/Makevars' file, you'll likely want to set the
> FC variable to choose the Fortran compiler, and FCFLAGS to choose the
> appropriate compilation flags. As an example, you can see how one might set
> these flags to compile code with the address sanitizer active:
> (Note that this example uses the user-level '~/.R/Makevars' file rather
> than the package-level 'src/Makevars' file, but the crux is the same)
> Hope this gets you on the right track,
> On Mon, Aug 27, 2018 at 1:15 PM Erin Hodgess <erinm.hodgess using gmail.com>
>> I'm building a package on Windows 10 which uses the PGI Fortran compiler.
>> I have a Makefile set up in the src directory, and when I run "make all",
>> the subroutines compile beautifully.
>> Now I want to create my package. When I run R CMD check, naturally,
>> gfortran is called. Is there a way that I can direct the check function
>> just use the make/Makefile, please?
>> Or am I out of luck, please? (highly probable)
>> Erin Hodgess, PhD
>> mailto: erinm.hodgess using gmail.com
>> [[alternative HTML version deleted]]
>> R-package-devel using r-project.org mailing list
[[alternative HTML version deleted]]
More information about the R-package-devel