-
Notifications
You must be signed in to change notification settings - Fork 446
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
Move installer from InstallShield to NSIS #3194
Comments
@AenBleidd, do you have a WIP version? |
Yes |
Upload it please, if I have time, I'll try to contribute or at least give my 2 cents. :) |
Ok, I need to polish it then because currently it's not ready to be shown to anyone😜 |
NSIS might not be the best choice for BOINC. |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently BOINC uses InstallShield to create a installer. It is not free and rather expensive.
I suggest to move away from it and use NSIS instead ( https://nsis.sourceforge.io/Main_Page ).
It is free and easy to use.
I played a little bit with it and found it very easy. I can create test installer next week or so.
If we consider to use it we should also rewrite boinccas dll that is built with VS2010 now and I found no way to build it with newer versions of VS because of OLE dll usage that is used to communicate with InstallShield installer. So we will need either to rewrite this library on NSIS script language or just clean up existing library from all InstalShield references.
Also moving to NSIS will give us an opportunity to extend existing functionality of installer that is requested by users.
Any thoughts?
I'd like to discuss this on the upcoming Contributions call 6/27/19.
The text was updated successfully, but these errors were encountered: