-
Notifications
You must be signed in to change notification settings - Fork 35
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
add note about GDAL building issues on Windows #238
Conversation
and how to fix
@ranjanan please merge if it looks okay -- just a simple addition to the readme. |
My suggestion is that we just wait for GDAL.jl folks to tag a new version and update our dependencies. |
Okay -- We don't have a compat entry for GDAL since we depend on ArchGDAL (which of course itself depends on GDAL), but I think this is solved with ArchGDAL v0.4.0 which was just released. See yeesian/ArchGDAL.jl#125 I added v0.4 to the compat, but we could also remove ArchGDAL of 0.3.1 to prevent this issue altogether. |
Let's keep moving forward on versions. |
I'll close this. I can do direct commit to master to update the ArchGDAL compat if that works? |
I think we just need to change the compat to v0.4.0 for ArchGDAL. |
I just realized my comment was wrong and deleted it. Yes, we should do that - so that we are able to use artifacts. |
Okay I'll make that commit now! |
Ha! You beat me to it 🙂 |
:-) I also updated IterativeSolvers.jl. Seems to pass things for me - but can you give it a try? I think these old versions were holding back many dependencies to old versions. This should resolve more dependent packages to use newer versions. |
Just bumped AlgebraicMultigrid too. |
Install working fine on my Linux machine 👍 |
Let's give it a few days on master and then tag a new version. Do the omniscape tests pass with this? |
I'll test it out now! |
Ah, we changed RasterMeta internally in Circuitscape so I just need to make a slight update. I'm going to update the Circuitscape dep to 5.6.0 soon,too, and switch to the CS versions of |
Some Omniscape users had this problem. Just thought I'd add text to provide some guidance. See Circuitscape/Omniscape.jl/issues/47