If the user goes on without checking the "advanced install" mode, the installer would make a per-system installation by default if ran by an user with administrator privileges, or a per-user installation by default if ran by an user without administrator privileges. This option (along with the choice of a different destination folder) should be placed within an "advanced install mode", as many other installers do. In addition to offering the possibility to install the program in a different folder, it would be nice if the installer asks if you want a per-system installation (in the program files folder by default), a per-user installation (in the user's application data folder by default), or a portable installation (which wouldn't create any shortcuts, file associations, etc only copy files). I don't know if I should put this here or as a new ticket (maybe as a feature request), but since this ticket is related to the issue of the installer, I will put it here: If I had realised a bit sooner how much trouble it would cause, I would have used Qt4 for the Windows build too.įuture releases in the medium term will probably revert to Qt4 on Windows as well, so there should be more flexibility in the Windows build packaging. However, as it happened, I made the Windows package before the OS/X or Linux builds - for both of which, it turned out to be simply too complicated to do a Qt5 build and I ended up reverting to Qt4 (the SV code can be compiled with either version). There are many more library dependencies with Qt5, which is why I resorted to a dynamic build with an installer. But I had reckoned without the difficulty of making a static build using Qt5. I would like to have provided an alternative static executable for download, as in versions up to and including 2.0, for those users who didn't want to use the installer. (By the way, if you or any other reader should be proficient with WiX installer logic, patches would be appreciated!)
0 Comments
Leave a Reply. |