Well, but the good thing about deken is that you don't need to know about anything to get confused or not. Whatever runs on your system is highlighted and offered to you. So what is the 'confusion'?
I'm now shipping for all the 8 suppoorted platforms on the same download. Here's what we have for the latest versions of Cyclone and ELSE.
(Darwin-amd64-32)(Darwin-i386-32)(Linux-amd64-32)(Linux-arm64-32)(Linux-armv6-32)(Linux-i386-32)(Windows-amd64-32)(Windows-i386-32)
So yeah, it seems the '32' at the end is about single precision (let's talk about single and double precision to avoid confusion). I offer a "fat" binary for mac that runs on both Pd 32 bits and 64 bits (32 is 'i386' and 64 is 'amd64). Window is just like that but there are separate binaries for each. Linux is also like that with separate binaries but there are also 'arm' versions for linux for raspberry pies: armv6 is for pi zero I think and it's 32 bits.
the binaries are
.d_fat
.l_amd64
.l_arm
.l_arm64
.l_i386
.m_amd64
.m_i386
(Darwin-amd64-32)(Darwin-i386-32)(Linux-amd64-32)(Linux-arm64-32)(Linux-armv6-32)(Linux-i386-32)(Windows-amd64-32)(Windows-i386-32)
- (Darwin-amd64-32)(Darwin-i386-32) => .d_fat - multiple archs for macOS: d_i386/intel 32 bits (for Pd 32 bits) & d_amd64/intel 64 bits (Pd 64 bits)
- (Linux-amd64-32) => .l_amd64 - Linux (Intel/AMD 64bit) for Pd 64 bits
- (Linux-armv6-32) => .l_arm - Linux arm (e.g. RaspberryPi) for Pd 32 bits (?)
- (Linux-arm64-32) => .l_arm64 - Linux arm64 (also for rasp) for Pd 64 bits.
- (Linux-i386-32) => .l_i386 - Linux i386 (Intel/AMD 32bit) for Pdd 32 bits
- (Windows-amd64-32) => .m_amd64 - amd64 (Intel/AMD 64bit) for Windows 64 bits
- (Windows-i386-32) => .m_i386 - i386 (Intel/AMD 32bit) for windows 64 bits