2015-11-17 NOTE: This year we made R packages before we used Make. The hope is, therefore, that the Make that ships with Rtools is all we need. So hopefully we can ignore this?
back to All the automation things
make on Microsoft WindowsWe are still working out the best way to install make on Windows. Our current best recommendation is to install msysGit, which includes make as well as git and bash.
Download and install msysGit. The two software packages msysGit and Git for Windows are related. Both install git and bash, but only msysGit installs make. The programs installed by msysGit are found by default in C:\msysGit\bin. Here is the complete list of programs included with msysGit. For this activity, RStudio needs to be able to find in your PATH environment variable the program make, the shell bash, other utilities like rm and cp, and Rscript.
Here is another alternative for installing make alone:
C:\Program Files (x86)\GnuWin32\make installed, but you need to tell Windows where to find the program. This is called updating your PATH. You will want to update the PATH to include the bin directory of the newly installed program.PATHIf you installed Make for Windows (as opposed to the make that comes with Git for Windows), you still need to update your PATH.
These are the steps on Windows 7 (we don’t have such a write-up yet for Windows 8 – feel free to send one!):
PATH variable. You may have to scroll down to find it;, followed by the path where the program was installed, followed by \bin.
;C:\Program Files (x86)\GnuWin32\binmake from RStudio and the command lineSee issue 58 for what seems to be the most comprehensive statement of the Windows situation.
What are the tricky bits?
Makefile to “work” via RStudio’s Build buttons/menus and in the shell. And, for that matter, which shell? Git Bash or ???make, Rscript, pandoc, rm, etc. can be found = updating PATH.make to use the correct shell.
back to All the automation things