|
369 | 369 | \item Both building \R and installing packages use the C compiler |
370 | 370 | in C23 mode. |
371 | 371 |
|
372 | | - \item R on Windows by default uses pkg-config for linking against |
| 372 | + \item R on Windows by default uses \command{pkg-config} for linking against |
373 | 373 | external libraries. This makes it easier to test R and packages with |
374 | 374 | alternative toolchains (such as from \I{Msys2}, e.g., testing with \I{LLVM} |
375 | 375 | and possibly with sanitizers). It also allows more significant \I{Rtools} |
376 | 376 | updates within a single R minor release. |
377 | 377 |
|
378 | 378 | \item The installer scripts for Windows have been tailored to |
379 | | - \I{Rtools45}, an update of the \I{Rtools44} toolchain. It is based on |
380 | | - GCC 14. The experimental support for 64-bit ARM (\code{aarch64}) CPUs is |
381 | | - based on \I{LLVM} 19. R-devel is no longer maintained to be \I{buildable} |
382 | | - using \I{Rtools44} and it is advised to switch to \I{Rtools45}. |
| 379 | + \I{Rtools45}, an update of the \I{Rtools44} toolchain. It is |
| 380 | + based on GCC 14. The experimental support for 64-bit ARM |
| 381 | + (\code{aarch64}) CPUs is based on \I{LLVM} 19. R-devel and \R |
| 382 | + 4.5.x arw no longer maintained to be \I{buildable} using |
| 383 | + \I{Rtools44} and it is advised to switch to \I{Rtools45}. |
383 | 384 | } |
384 | 385 | } |
385 | 386 |
|
|
540 | 541 | embedded API entry points in the rendered versions. This is very |
541 | 542 | preliminary and may be dropped if a better approach emerges. |
542 | 543 |
|
543 | | - Also now for Fortran-callable entry points which are part of the API. |
| 544 | + Also for Fortran-callable entry points which are part of the API. |
544 | 545 |
|
545 | 546 | \item \sQuote{Writing R Extensions} has a new section |
546 | 547 | \sQuote{Moving into C API compliance} to help package authors move |
|
0 commit comments