Ok, I get that a company can't always target everything with its software releases. If a codebase is too large and has been very tailored for a specific system (Windows, say), it may require a lot of work just to get it into something resembling compliance so that it will build on other systems. I get that.
But, this kills me: a company releases a Linux build of its software, but ONLY release an x86 build; if you run a pure-64 system, you're out of luck.
But hey, at least they released the source. Too bad I can't get to the game content, since the installer is 32bit also. So I'll poke at the installer with strings(1) and a hex dump and such, determine that the data files are stored in zip format, and write a simple C program to rip the zip structure out into a normal zip file. NO PROBLEM.
Except, HEY, the source code is only for the Windows release. Unless I want to try to parse the vcproj file (yeah, no thanks) out into a normal make file, and then work out all the MS-centric braindamage, and THEN figure out how to strip the Windows-only requirements, then I'm still dead in the water.
This is monstrous failure. Unless you are doing some special ASM magic (and even then maybe not), there is NO excuse for not providing a damned x86_64 executable with the binary release. Especially when the same company HAS provided both 32 and 64 bit binaries for previous products.