-
Notifications
You must be signed in to change notification settings - Fork 25
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
Latest release v0.3.0 is over 200mb in size #36
Comments
nope nothing wrong... include nvidia support from 3.0 to 6.1 |
have no idea how to include checksum https://www.microsoft.com/en-us/download/details.aspx?id=11533 As for the size (problem), could the (rather thin, I'd hope) different CUDA wrappers be linked into different DLL's? Unless CUDA API changed massively, that could even allow for runtime selection of DLL/version to use, automatically and/or with command-line (override) option. Additionally, if the binaries are linked to the static CRT (libc), it is possible to create binaries using directory-local msvcrt*.dll & co. to prevent messing with the system (SxS and so on). |
The idea was (and still is) a static build which can run almost anywhere and doesn't present any difficulty for new comers (and lazy people lol) to the altcoin/mining scene. I'll have a look for the checksum. thanks |
The idea was (and still is) a static build which can run almost anywhere Gotcha. That settles that (and I agree 100%). |
I also agree. I just kinda freaked out when the size exploded without explanation. Maybe an update to the release notes are in order? The whole checksum request was so that when things like this happen we can at least validate that it was intended. |
Seems like something is terribly wrong with the build. Can you verify that the size is supposed to be this big?
Also, it would be nice if md5/sha sums were included in releases.
The text was updated successfully, but these errors were encountered: