-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building with VS2019 and R 3.6.0 Fails #43
Comments
Hi, The message I will see if I can build from the CMD prompt and then see if devtools::build fails. |
Hi Jean-Michel,
At least, double slashes is not a valid construct within a path. I also notice that the search path contains the section .../rClr/libs/x64 while the original src has a similar sequence in the path: rClr/libfiles/x64. Should it be "libfiles" rather than "libs" in the searchpath? |
Hi,
I'll investigate this further to see if I can solve the problem. |
I noticed the build log has if I launch I tried to automagically have the VS msbuild detected but for some reasons the R build process fails to use it; it needs to be set up in the PATH before launching As mentioned in the readme at https://github.com/rdotnet/rClr ,
The strange path with 'Temp' folders and double slashes is not surprising; this is what R pkg build does indeed. Hope this helps |
Hi,
I try to compile and build rClr using VS2019 and R 3.6.0. The compilation works fine, but the build, using devtools::build, fails late in the process. Here are the error messages at the end of the output log from devtools::build:
I have tried to follow the instructions by running setup_vcpp.cmd, and setting the environmentvariables in accordance with the setup on my machine. I'm a little bit surprised that build() complains about missing ".NET Framework" in the temporary directory. ClrFacade is set up to compile with .NET Standard 2.0 - not .NET Framework.
I have been struggling with this problem for hours now, and hope for any ideas or suggestions on how to solve this problem!
Here is info about the setup on my machine:
Below is the full output log FYI.
Best regards,
Tor Vidvei
The text was updated successfully, but these errors were encountered: