How to package plugin to avoid 64-bit IDE trying to load 32-bit plugins?

MBS plugins have both 32 and 64bit code.
The IDE always tries to load 32-bit first, than checks 64-bit part.

We have “Mac x86-64” folder, but that is not the one Xojo tries first.

Feedback case: <https://xojo.com/issue/50882> (not yet public)

Deprecated 32 bit macOS builds means they are going away at some point in the future.

Here’s the link to that:

http://documentation.xojo.com/resources/deprecations.html#2018_Release_2

You guys seem to not get it.

The IDE is 64-bit, the plugins are 64-bit, but the package still includes 32-bit plugins.

And the IDE is trying to load the 32-bit ones, which it should not need to.

I just would like less errors running Xojo IDE from Terminal and I wonder if it could start quicker when it loads the 64-bit without touching the 32-bit ones.

Sorry if I’m misunderstanding here, but what happens if I’m using the IDE to specifically build 32bit versions of my project? Won’t the 32bit plugin segments be needed?

[quote=416741:@Jason Parsley]Deprecated 32 bit macOS builds means they are going away at some point in the future.

Here’s the link to that:

http://documentation.xojo.com/resources/deprecations.html#2018_Release_2[/quote]
Not everyone is jumping on the latest and greatest (maybe) bandwagon. MBS (and others’) plugins are still compatible with older RS/Xojo versions where 32bit support is still possible and my customer base is still running a lot of legacy systems that require older and/or 32bit builds for proper support.

MBS Plugin includes 32 and 64bit parts.
The IDE picks the right part for the app build.

It’s just that when the IDE wants to read the plugins on startup it first tries to read 32-bit file, fails and than tries 64-bit one.
I am annoyed by that extra work and the resulting error messages.

It’s just a little change in the IDE source code as the first folder to check in the plugin should be “Mac x86-64”.

[quote=416838:@Christian Schmitz]MBS Plugin includes 32 and 64bit parts.
The IDE picks the right part for the app build.

It’s just that when the IDE wants to read the plugins on startup it first tries to read 32-bit file, fails and than tries 64-bit one.
I am annoyed by that extra work and the resulting error messages.

It’s just a little change in the IDE source code as the first folder to check in the plugin should be “Mac x86-64”.[/quote]

Changing may help the ide get back to speed. Hopefully

The effect is small and only while loading plugins on startup.

I can get on board with getting through the plugins loading as quickly as possible. You have my vote :slight_smile:

Seeing how long it takes to initialize the full palette of plugins under 64 Bit, I appreciate every second that could be saved.