32bit Console Applications are still looking for Carbon plugin segments even if developers have limited ways of compiling and maintaining Carbon nowdays.
Why would 32 bit console app want to use Carbon when 64 bit uses Cocoa ?
Filed also bug report at:
58861
Tricking Cocoa segment into it seems to work by Putting Cocoa segment in the Carbon folder in the Plugin. So it seems Xojo is only looking for the plugin in wrong directory in the plugin file.
32 bit apps aren’t that useful going forward (helpers or otherwise)
they will have uses on older macOS versions as 10.15+ wont support 32 bit at all
Still annoying to see Xojo trying to load 32-bit plugin first and then load 64-bit plugin.
If you run Xojo.app from Terminal or watch console.app, you can see a ton of errors messages due to wrong architecture.
And yes, it would be more simply if Xojo would use the regular plugin for Console.
Its just plain bug, since putting the Cocoa segment where the Carbon one should be works fine.