i have not worked with xojo for some years but recently was updating some software i developed and when i would build the application and tried to start it, i got a runtime error.
it said common\plugin.cpp: 1005
failure condition: pluginentrytale.getentry( entrypointname, out )
can’t find pluginmethod _gzipstring.compress(sounce as string, level as integer = defaultcompression) as string
i would greatly appreciate some help. this is way out of my league.
You may not be using any third party plugins, but Xojo has quite a few internal ones. This message in your application means that your application is missing a required dll from the plugins folder. We can tell from the underscore prefix that it’s a Xojo internal function.
The most common cause for this is updating Xojo but not your Inno Setup script.
i started my app in the folder created by xojo during the build. i did not install it, just double clicked it right in the folder that held it and the My Applications Libs folder.
Clearing the plugin cache as Christian suggested is very much worth a try.
I don’t have Xojo installed on Windows, so I couldn’t tell you the exact name and location, but you’re looking for “Preferences” “Settings” or “Options” under either the “Edit” or “Help” menus.
if i restart my program and just build the executable, it works. but i create an installer with inno setup and it shows the same problems i started with.
Well, if the application works nominally when run from the build folder, then the build is fine. But your problem with the installer indicates that at least some of the DLLs are not in your InnoSetup script. The script should be using a wildcard to get the ones in the Libraries folder. Therefore, I am going to guess that the issue is with the ones that are in the top level, alongside the .exe.
The combination of "*" and recursesubdirs captures everything in the app folder, including all DLLs and Resource folders.
The use of Excludes: ".*" filters out any hidden files or folders.
It’s a little simpler than your 3 line solution, but note if there is anything in the Built Exe folder you do not want to include in the InnoSetup installer, my script would include it by default.
Ah.. there is a reason why I had them split over 3 lines, to do with whether or not I install some files based on components which I have set up in my install.
As you say, some things I might not want.
I’m confident your one liner will be better for this situation.
And my app is 64 bit. The ‘Windows 64 bit’ would be part of the PATHTO