Closed nbenn closed 5 years ago
The rtools40 toolchain is still experimental, we do not support it on appveyor yet. Hopefully soon.
Thanks for the quick response. Does a rough eta exist? Is this a question of weeks, months, end of this year, sometime next year? No worries, if in the end stuff takes longer that you anticipated. I'm just trying to get a rough idea of when this could happen if all goes according to plan.
It's not up to me but hopefully before the end of the year.
Ok, thanks a lot for giving an idea of what you're hoping for.
I'm sorry if this is the wrong place for a question like this, but it's the best I could come up with.
Given a standard (
usethis::use_appveyor()
generated) Appveyor configuration```YAML # DO NOT CHANGE the "init" and "install" sections below # Download script file from GitHub init: ps: | $ErrorActionPreference = "Stop" Invoke-WebRequest http://raw.github.com/krlmlr/r-appveyor/master/scripts/appveyor-tool.ps1 -OutFile "..\appveyor-tool.ps1" Import-Module '..\appveyor-tool.ps1' install: ps: Bootstrap cache: - C:\RLibrary # Adapt as necessary starting from here build_script: - travis-tool.sh install_deps test_script: - travis-tool.sh run_tests on_failure: - 7z a failure.zip *.Rcheck\* - appveyor PushArtifact failure.zip artifacts: - path: '*.Rcheck\**\*.log' name: Logs - path: '*.Rcheck\**\*.out' name: Logs - path: '*.Rcheck\**\*.fail' name: Logs - path: '*.Rcheck\**\*.Rout' name: Logs - path: '\*_*.tar.gz' name: Bits - path: '\*_*.zip' name: Bits ```
How would I go about to change this such that builds use the new Rtools40 toolchain? Is there an example for this somewhere?