-
Notifications
You must be signed in to change notification settings - Fork 25
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
Installing on windows #21
Comments
It sounds possible, but I've never tried. You probably need to make a windows version of Makevars containing correct compiler options for windows.. |
Not sure who sent in a winBuilder attempt, but here is the result:
Seems easy to fix. |
Just tried it: a) will need a grpc build with the same compiler as used by Rtools - mingw
c) Created Makevars.win containing:
d) finally rund devtools::install() But I am getting a compilation error:
e) How do I set the compilation flag in the Makevars.win? Full output.
|
See also grpc/grpc#4707 |
Updated Makevars.win to:
And it seems to build. There are now in the src folder :
But now the installation process fails with :
Full output:
|
That's pretty mysterious; you might try asking on R-pkg-devel or the R-windows mailing lists. |
@wolski @nfultz
If there are any additional problems it will be mainly in the grpc.dll file so you will need to generate it yourself as I did but I hope that it will work for you directly. |
Could you explain step 6 - where did that file come from? |
Well, there are many cases that can lead to this error while loading the package on Rstudio (on Windows OS). I tried all of the possible ways to solve this problem but unfortunately none of them worked. However, according to the following issue, it was stated that the dll file should be generated on the system itself (depending of its specs). So, my approach was targeted to build the package files myself relying on my system specs (Windows 10 64-bit). I followed the following steps to build generate the .dll file:
This will generate a new static library
This was the only process that worked for me. I did intensive research and there are other solutions for this type of error but as I stated before none of them worked for me. However, the main two solutions that solved this problem for other users were as follows:
|
I see, quite complicated. The "unblock" thing in particular seems annoying. I guess my thoughts are -
I'm not an expert on windows packaging or autotools, but I would be surprised if we were the first ones to encounter DLL issues. If rprotobuf doesn't have a solution, I'd recommend asking around at either the r-package-devel list or maybe the r-windows list. |
You are definitely right! This approach is quite complicated. The good news is that we are not the first ones to encounter dynamic linking issues. It is actually quite common among Windows users trying to install various R packages. However, regarding your thoughts,
I will try to follow Dirk's lead right now and see how exactly the rprotobuf package handles this DLL issue correctly. |
Is it possible to get the package installed on MS Windows . I did run into the following error:
The text was updated successfully, but these errors were encountered: