Thanks Dirk -- my apologies -- I see now that the subject line does kind of
imply the toolchain. That was not my intention -- I think I was just trying
to give people context -- the error happened in the context of an
Rcpp-dependent app with the last useful message mentioning Rcpp, so I guess
I tho
On 14 February 2025 at 15:09, John Clarke wrote:
| Thank you! This didn't directly solve my problem, but it got me looking in
| the right direction. I ended up connecting to a docker container through VS
| Code on my host machine (Windows). I didn't wire up the debugger UI (which is
| really conv
Hi Serguei,
Thank you! This didn't directly solve my problem, but it got me looking in
the right direction. I ended up connecting to a docker container through VS
Code on my host machine (Windows). I didn't wire up the debugger UI (which
is really convenient in VS Code) but was able to identify th
Hi John,
Le 13/02/2025 à 15:17, John Clarke a écrit :
Hey folks,
I've been developing an Rcpp package on my Mac and testing on Mac and
Windows. I also have been testing on linux-latest with the standard
Github action which runs the CMD check. These passed without any problem
until I implemen
Hey folks,
I've been developing an Rcpp package on my Mac and testing on Mac and
Windows. I also have been testing on linux-latest with the standard Github
action which runs the CMD check. These passed without any problem until I
implemented a test suite (testthat) and increased the test coverage
