search for: shlib_intern

...ail? > > I basically get no output from the two commands, apart from a new > blank R prompt. So starting a new Rcmd.exe process fails for some reason. If you take the same R session where the environment variables are right and Sys.which() resolves Make and GCC and try to run tools:::.shlib_internal(c('-n', 'hello.c')) or tools:::.shlib_internal('hello.c'), does it do something useful? (I'm still debugging from first principles. Duncan Murdoch is likely right that adding the environment variables, either RTOOLS43_HOME=c:/rtools43 or adjusting PATH as described ab...

> So starting a new Rcmd.exe process fails for some reason. > > If you take the same R session where the environment variables are > right and Sys.which() resolves Make and GCC and try to run > tools:::.shlib_internal(c('-n', 'hello.c')) or > tools:::.shlib_internal('hello.c'), does it do something useful? I think I tried the commands in the right R session. Here are all the output related to the environment variables for R as well as Sys.which(): ``` > Sys.getenv("RTOOLS42...

...I= B /var/folders/bU/bUB3Gk1uHBuDXq1G72Xc+++++TI/-Tmp-/RtmpGzn3kA/file60b7acd9= .cpp") Error in sub(p0(base, "."), "", a) :=20 invalid regular expression '/var/folders/bU/bUB3Gk1uHBuDXq1G72Xc+++++TI/-= Tmp-/RtmpGzn3kA/file60b7acd9.' Calls: <Anonymous> -> .shlib_internal -> sub In addition: Warning message: In sub(p0(base, "."), "", a) : regcomp error: 'Invalid use of repetition operators' Execution halted Browse[2]> system("R CMD SHLIB /var/folders/bU/bUB3Gk1uHBuDXq1G72Xc+++++TI/= -Tmp-/RtmpGzn3kA/file60b7acd9.cpp")...

> When installing packages containing code to compile, R eventually calls > R CMD SHLIB. Same thing happens with inline C++: it gets stored in a > temporary file, compiled into a *.dll using R CMD SHLIB and then loaded > using dyn.load(). > > Write the following into a file named hello.c: > > #include <R.h> > #include <Rinternals.h> > SEXP hello(void) {

? Thu, 31 Aug 2023 14:01:54 +0000 Christophe Bousquet <chr_bousquet at protonmail.com> ?????: > So when I run the commands, I get this output. I honestly have no > clue whether this can be considered as something useful or not :-/ > > ``` > > tools:::.shlib_internal(c('-n', 'hello.c')) > make cmd is > make -f "C:/PROGRA~1/R/R-43~1.1/etc/x64/Makeconf" -f > "C:/PROGRA~1/R/R-43~1.1/share/make/winshlib.mk" SHLIB="hello.dll" > WIN=64 TCLBIN= OBJECTS="hello.o" This can be considered good news...

C++ support across different platforms is now very heterogeneous. The standard is evolving rapidly but there are also platforms in current use that do not support the recent iterations of the standard. Our goal for R 3.4.0 is to give as much flexibility as possible. The default compiler is whatever you get "out of the box" without setting the "-std=" flag. This means different