Skip to content
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

Interested in adding windows builds with Appveyor? #88

Closed
sckott opened this issue Aug 21, 2014 · 8 comments
Closed

Interested in adding windows builds with Appveyor? #88

sckott opened this issue Aug 21, 2014 · 8 comments

Comments

@sckott
Copy link
Contributor

sckott commented Aug 21, 2014

If so, i can do, let me know

@cboettig
Copy link
Member

Yup, let's give it a go. at least CRAN seems to be managing to build the windows binaries, so should be a good test.

@sckott
Copy link
Contributor Author

sckott commented Aug 21, 2014

ok

sckott added a commit that referenced this issue Aug 21, 2014
sckott added a commit that referenced this issue Aug 21, 2014
@sckott
Copy link
Contributor Author

sckott commented Aug 21, 2014

@cboettig I added appveyor file, badge to readme, and turned on daily builds for the package, that run around 730-930 am each day

The basic appveyor.yml file may not have everything it needs to build correctly, we'll see how it goes with this first build https://ci.appveyor.com/project/sckott/rnexml

@sckott
Copy link
Contributor Author

sckott commented Aug 21, 2014

Hmm not sure what the equivalent of sudo apt-get will be for Windows in the appveyor file 0a56c8f - Appveyor obviously doesn't like those commands since it's windows, anyone know

@rvosa
Copy link
Contributor

rvosa commented Aug 22, 2014

Unless the universe has drastically changed over the last few years there is nothing even remotely like apt-get under Windows. Seeing that this is for libxslt I suspect there would have to be some very dodgy maneuver to download the equivalent *.dll and place it somewhere in the %PATH%. Likewise, shell scripts won't work either and would have to be converted to *.bat scripts.

Maybe I'm misunderstanding what we're trying to accomplish here but this seems more trouble than it's worth? Who uses Windows anyway? ;-)

@sckott
Copy link
Contributor Author

sckott commented Aug 22, 2014

I wouldn't be surprised if more than 50% of our users across our pkgs are windows users. Maybe phylogenetics community is an especially non-Windows community though.

Anyway, the point is to know quickly when a change is breaking on Windows.

@cboettig
Copy link
Member

CRAN is already supplying windows builds and daily windows checks for
RNeXML, so even though we may have a lot of Windows users I don't think we
need to worry about this. See
http://cran.r-project.org/web/checks/check_results_RNeXML.html

On Fri, Aug 22, 2014 at 6:36 AM, Scott Chamberlain <notifications@github.com

wrote:

I wouldn't be surprised if more than 50% of our users across our pkgs are
windows users. Maybe phylogenetics community is an especially non-Windows
community though.

Anyway, the point is to know quickly when a change is breaking on Windows.


Reply to this email directly or view it on GitHub
#88 (comment).

Carl Boettiger
UC Santa Cruz
http://carlboettiger.info/

@sckott
Copy link
Contributor Author

sckott commented Aug 22, 2014

Definitely do remove, but CRAN is only testing the CRAN version. i guess this package doesn't primarily work with a web API that can change, so less important here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants