-
Notifications
You must be signed in to change notification settings - Fork 47
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
Possible Windows builds #81
Comments
+1, would be awesome. Was thinking of a script to build windows binaries on an EC2 windows machine. |
Ah, so you just volunteered. That was fast. Awesome. :) |
I'll see what I can do
|
+100, this would be fantastic. I haven't owned a Windows machine since ~2003, so I'm gonna need help testing this. |
I did some experiments with running R in Wine (in my wine branch), but this currently fails because of an incompatible References: http://bugs.winehq.org/show_bug.cgi?id=34865 |
@krlmlr Any progress on that Wine error? Also, where would builds using Wine be done? Just install Wine on each Travis build, or send elsewhere? |
@schamberlain: The former, details are in my branch. I haven't found the time to play with Wine again. |
@krlmlr thanks. I did try, but to no avail. I don't think I'll have time to work on this, sorry :( |
no sweat -- thanks @schamberlain, at least now we have a lead. |
What about Appveyor? I asked them about support for R http://help.appveyor.com/discussions/questions/211-r-support - we'll see what happens. |
There is now some support for AppVeyor-hosted Windows builds in krlmlr/r-appveyor. Very similar to Travis-CI -- needs a The project is working, but in an early stage. Currently, only tests on R-devel are supported (nightly build, loaded from a custom ISO image); Rtools is included, but no LaTeX yet. Self-tests pass. The good news: Artifacts (e.g., binary packages) can be hosted effortlessly on AppVeyor. |
The Julia folks use a thing called WinRPM along with the openSUSE Build Service to provide Windows binaries.
Could we have Travis hook into this?
The text was updated successfully, but these errors were encountered: