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

update windows FAQ #261

Open
mroth opened this issue Feb 22, 2015 · 8 comments
Open

update windows FAQ #261

mroth opened this issue Feb 22, 2015 · 8 comments

Comments

@mroth
Copy link
Member

mroth commented Feb 22, 2015

The Windows install FAQ is likely very outdated, since it looks like a good portion of it involves installing things necessary for RMagick to build:

https://github.com/mroth/lolcommits/wiki/Installing-on-Windows

Since we got rid of RMagick long ago (years even?) some of these steps are probably unnecessary now.

@matthutchinson
Copy link
Member

I think we do still need ImageMagick. The resize_snapshot! command calls the MiniMagick gem to convert the raw image with options here..

I remember needing to jump through these hoops when I setup a VM machine with Windows for lolcommit testing recently.

... our existing README also lists imagemagick as a requirement (for OSX / Linux / Windows)

@mroth
Copy link
Member Author

mroth commented Feb 22, 2015

Ah yeah, ImageMagick is still definitely needed. The stuff I was thinking could probably go had to do with getting RMagick to compile. I think since MiniMagick just shells out and is pure ruby without C extensions, we may no longer need the Ruby Development Kit or ImageMagick "development headers and libraries" options, and can potentially just use normal installs.

@matthutchinson
Copy link
Member

Since I did this - I think we can close this now?

The guide is as lean as it can be right now for a working lolcommits on windows. We can obviously update it as things change when plugins get moved out and the DevKit dependency isn't needed anymore.

I was thinking of adding info on how to run tests on Windows, but until we have a passing build we can work with, I don't think there is much point.

PR #278 needs release for the Windows post-commit to be fixed. Even tho we don't have many windows users at all, I think its worth releasing that as 0.5.9

@mroth
Copy link
Member Author

mroth commented Apr 23, 2015

I think the one thing I'd like to figure out is if the Ruby Developer Kit is still required. Since we no longer use gems with C extensions (I believe?) I don't think it should be needed, which could simplify things a lot. IIRC this was just for when we were using RMagick.

@matthutchinson
Copy link
Member

I've checked - we DO need it (for the OJ gem to install) which is a requirement from our Yammer plugin. So right now as it stands, it is required. Like I mentioned, if we move plugins out of the main gem, we won't have this dependency anymore.

@mroth
Copy link
Member Author

mroth commented Apr 23, 2015

Ahhh ok. Yet another reason to move out the plugins. CC #99 so this thread shows up there.

@matthutchinson
Copy link
Member

can close?

@mroth
Copy link
Member Author

mroth commented Apr 24, 2015

I think okay to close (as long as we make testing then updating the FAQ again a completion task for #99).

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

No branches or pull requests

2 participants