Run time errors

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.

@Carl_Mize

How were you updating? With a newer version of Xojo?

Have any Plugins (3rd party) in use?

32Bit App going to 64Bit App?

You may need to clear caches.
See button in preferences dialog.

Then try again.

brand new version of xojo, no plug ins. 32bit, i think.

thanks

where is the preferences dialog button?

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.

2 Likes

thanks

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.

Maybe you can upload a zip of project here and we can take a look?

1 Like

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.

Hold on and I will check location:

Edit → Options ->Building → Button Clear Caches

1 Like

before Edit → where were you?

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.

Your post was flagged by the community.
Thank you.

I don’t think so; I’d rather assume Brian’s answer wasn’t explicit about the fact that “Edit” referred to a menu (it could have been anything).

@Arnaud_N
How explicit does it have to be?
I think @Tim_Parnell reply and mine was fine enough to push anyone to the IDE main menu’s.

Let’s try to be helpful, and not make this look like an Arch Linux forum. :slight_smile:

Your Inno setup script should look like this, more or less, to pick up all dlls and subdirectories

[Files]
Source: “PathToBuild\YourApp\*”; DestDir: “{app}”; Flags: ignoreversion signonce
Source: “PathToBuild\YourApp\YourApp Resources\*”; DestDir: “{app}\YourApp Resources” ; Flags: ignoreversion recursesubdirs createallsubdirs ;
Source: “
PathToBuild\YourApp\YourApp Libs\*”; DestDir: “{app}\YourApp Libs”; Flags: ignoreversion recursesubdirs createallsubdirs signonce;

@Jeff_Tullin is yours a 32 or 64 bit app?

For my 64-bit Windows Xojo app, I use this one-liner for the Source: command, which seems to work well:

Source: "..\MyAppName\Builds - MyAppName.rbvcp\Windows 64 bit\MyAppName\*"; Excludes: ".*"; DestDir: "{app}"; Flags: ignoreversion

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

1 Like