Skip to content

Commit

Permalink
doc: update rtools40 to rtools44
Browse files Browse the repository at this point in the history
  • Loading branch information
Bai-Li-NOAA committed May 30, 2024
1 parent 0b90069 commit fa8993f
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 8 deletions.
2 changes: 1 addition & 1 deletion 04-user-guide.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ The following software is required:

### Windows users

- Rtools4 (available from [here](https://cran.r-project.org/bin/windows/Rtools/rtools40.html))
- Rtools4.4 (available from [here](https://cran.r-project.org/bin/windows/Rtools/))
- this likely requires IT support to install it on NOAA computers
(or any without administrative accounts)

Expand Down
14 changes: 7 additions & 7 deletions 06-developer-software-guide.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -164,21 +164,21 @@ If not, you will need to check that the compiler is on the path. The
easiest way to do so is by creating a text file .Renviron in your
Documents folder which contains the following line:
```
PATH="${RTOOLS40_HOME}\usr\bin;${PATH}"
PATH="${RTOOLS44_HOME}\usr\bin;${PATH}"
```

You can do this with a text editor, or from `R` like so (note that in
`R` code you need to escape backslashes):
```{r eval=FALSE}
write('PATH="${RTOOLS40_HOME}\\usr\\bin;${PATH}"', file = "~/.Renviron", append = TRUE)
write('PATH="${RTOOLS44_HOME}\\usr\\bin;${PATH}"', file = "~/.Renviron", append = TRUE)
```

Restart R, and verify that make can be found, which should show the path
to your Rtools installation.

```{r eval=FALSE}
Sys.which("make") ##
"C:\\rtools40\\usr\\bin\\make.exe"
"C:\\rtools44\\usr\\bin\\make.exe"
```

### GoogleTest
Expand All @@ -191,19 +191,19 @@ template](#testing).

Windows users who use GoogleTest may need GDB debugger to see what is
going on inside of the program while it executes, or what the program is
doing at the moment it crashed. rtools40 includes the GDB debugger. The
doing at the moment it crashed. rtools44 includes the GDB debugger. The
steps below help install 64-bit version gdb.exe.

- Open Command Prompt and type `gdb`. If you see details of usage, GDB
debugger is already in your PATH. If not, follow the instructions below
to install GDB debugger and add it to your PATH.
- Install Rtools following the instructions [here](https://noaa-fims.github.io/collaborative_workflow/user-guide.html#windows-users)
- Open ~/rtools40/mingw64.exe to run commands in the mingw64 shell. Run
- Open ~/rtools44/mingw64.exe to run commands in the mingw64 shell. Run
command `pacman -Sy mingw-w64-x86_64-gdb` to install 64-bit version
(more information can be found in [R on Windows FAQ](https://github.com/r-windows/docs/blob/master/faq.md#does-rtools40-include-a-debugger))
- Type `Y` in the mingw64 shell to proceed with installation
- Check whether ~/rtools40/mingw64/bin/gdb.exe exists or not
- Add rtools40 to the PATH and you can check that the path is working
- Check whether ~/rtools44/mingw64/bin/gdb.exe exists or not
- Add rtools44 to the PATH and you can check that the path is working
by running `which gdb` in a command window


Expand Down

0 comments on commit fa8993f

Please sign in to comment.