![]() This, however, does mean that you cannot close your source code and reply on the LGPL. This requires you to configure and build a static version of Qt. The other approach, which works across all platforms, is to link Qt statically to your application. Most modern Linux distributions will then offer the user to download and install Qt for them when they try to install your package. By building your application against a prepackaged version of Qt, you can usually put Qt down as something that your application depends on. On most Linux distributions, Qt is already packaged. The trouble of having to package and spread dynamic libraries can be solved in two ways. That package not only contains the needed files, but also instructions on where to place them and what questions the user will have to answer, and so on. When creating an installer, you take these parts and build a package out of them. ![]() Support files, such as graphics, translations, documentation, and so on. Dynamic libraries (dll or so files), usually a couple of Qt modules (QtCore, QtGui and friends) and plug-insģ. The executable, the program that the user runs.Ģ. These can be divided into three groups:ġ. Also I'm using InstallBuilder for Qt 8.5.A Qt application generally consists of a number of files. The installBuilder unzips them in 19 minutes, while a standalone unzip tool unzips them only in 6 minutes.īTW, the installer is created unsing "zip" compression method. I have about 20 zip files in total 8.59GB, 13655 files, 47 folders. ![]() I understand it can be slower than a zip tool, but shouldn't be that slow.Īlso the "unzip" action provided in the InstallBuilder is much slower than an "unzip" tool. The installer created for 3.12GB, 54176 files, 11051 folders takes 19 minutes, while 7z only takes 6 min. The installation is much slower than a 7z unzip. We had our existing installer, installs the same set of files in 28 minutes. The total installation time is over 80 minutes. The total installation size (after installed) is 17.9GB, with 165529 files, 18763 folders. I have a main installer about 1.74GB in size, which also calls some sub-installers and unzips some big zip files. (The data below are collected on Windows platform) I notice the installer created by InstallBuilder installs really slowly for large software especially on Windows platform. Is this a limitation of InstallBuilder, or am I missing something? Using the icacls.exe tool manually, it is possible to add poth "allow" and "deny" permissions. Unfortunately, setting one set of permissions causes the other set of permissions to be removed.įor example, I'm executing following actions: Īfter executing the "allow" action, the file has appropriate "allow" permissions for the administrator group.Īfter executing the "deny" action, the file has appropriate "deny" permissions for the administrator group, but the previously created "allow" permissions entry has vanished. To avoid this problem, you have to test whether the boolean equals "1" or "true": īut I think checkboxes should always return the same type of value. Whereas if you uncheck and then check again the checkbox, you will obtain: If you create a custom page like this one : Īnd go to the next page without unchecking/checking the checkbox, it will display: PPS: When running InstallBuilder twice, the warning/error message is shown the first time only (when the folder specified in is still empty) the second time, InstallBuilder doesn't complain (when overwriting the existing signed installer with the newly created one).ĭefault value of a checkbox is returning "1", even if it has been defined to "true". Why does InstallBuilder give this warning/error message? path/to/MyInstaller.app: satisfies its Designated Requirement Using codesign to verify the signature afterwards gives: $ codesign -vv /path/to/MyInstaller.app path/to/MyInstaller.app: invalid signature (code or signature have been modified) Warning: Error signing /path/to/MyInstaller.app: Error signing installer: /path/to/MyInstaller.app: replacing existing signature I added an appropriate property to my XML project file, now my installer gets signed successfully, even though I see following warning/error message during the build process: $ /path/to/installbuilder.sh build /path/to/project.xml osxĠ% _ 50% _ 100%
0 Comments
Leave a Reply. |