-
Notifications
You must be signed in to change notification settings - Fork 39
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
Windows binaries not statically built #85
Comments
Dang, I thought I had fixed this! I will fix. Been stuck working on a project for a client with a super tight deadline since the end of November, but It is nearing completion. I will try to knock out the release this weekend. It is super close anyway. |
No problem, take your time. I'm just reporting it so you can fix it for 2.0. |
So, I'm finally able to continue working on things. This is my next priority. Just wanted to let you know. |
@FormerLurker How is work going for now? |
Well, poorly. I spent the several weeks out of town helping my mom and dad take care of my grandmother, who passed away during that time + funeral. I'm totally OK, but this left me unable to finish this up. I promise I've been working on this though, and will get it done. I have some other projects I'd like to start as well, but need to get ArcWelder (priority 1 for arachne support) and Octolapse (priority 2) squared away before that. |
Glad to hear that. This may sound presumptuous, but take the time you need, there are more important things than code. |
The Windows builds of version 1.1.1 and 1.2.0 are statically built (ie: it depends on the visual c++ runtime). This causes the binaries to fail with a returncode 3221225781 on systems where the right version of the visual c++ runtime is not installed.
The 1.1.0 build was statically built, so it runs regardless of whether the visual c++ runtime is installed.
The text was updated successfully, but these errors were encountered: