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 compiler:
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Using-Makevars 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: https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Using-Address-Sanitizer (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, Kevin On Mon, Aug 27, 2018 at 1:15 PM Erin Hodgess <erinm.hodg...@gmail.com> wrote: > Hello! > > 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 to > just use the make/Makefile, please? > > Or am I out of luck, please? (highly probable) > > Thanks, > Erin > > Erin Hodgess, PhD > mailto: erinm.hodg...@gmail.com > > [[alternative HTML version deleted]] > > ______________________________________________ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
