inky icon indicating copy to clipboard operation
inky copied to clipboard

MacOS Catalina: Unity plugin cannot compile .ink because 32-bit

Open DavidYork opened this issue 5 years ago • 2 comments

There is a file inklecate_mac that ships with the Unity plugin. Unfortunately this file was compiled as 32-bit and Catalina only runs 64-bit apps now. Thus the "compile" and "compile all" features of the plugin silently fail (appear to do nothing).

Observe InkCompiler.cs has in the OnCompileProcessComplete function the output of the process is blank:

string allOutput = process.StandardOutput.ReadToEnd(); < variable allOutput is the empty string.

Also when you run inklecate_mac from the command-line you get the following error output:

Last login: Thu Jul  2 22:42:38 on ttys001
/Users/david/Documents/Creative/Ink/the-intercept/Assets/Plugins/Ink/DLLs/inklecate_mac ; exit;
➜  ~ /Users/david/Documents/Creative/Ink/the-intercept/Assets/Plugins/Ink/DLLs/inklecate_mac ; exit;
zsh: bad CPU type in executable: /Users/david/Documents/Creative/Ink/the-intercept/Assets/Plugins/Ink/DLLs/inklecate_mac

[Process completed]

Recommended solution: recompile the inklecate_mac binary as 64-bit and replace the old 32-bit one.

DavidYork avatar Jul 08 '20 01:07 DavidYork

One small note, the Unity plugin on the asset store doesn't have this problem. I'm not personally blocked, just trying to be a good citizen here. Normally I'd create a PR, but it's a binary and I'm a complete stranger so obviously I cannot do that :)

DavidYork avatar Jul 09 '20 04:07 DavidYork

This belongs in https://github.com/inkle/ink-unity-integration and not the inky editor. Please close this and check to see if anyone's talking about this issue (if it's not already solved) over there.

lunarcloud avatar Jan 12 '22 13:01 lunarcloud