We can't do that. Some of our libraries are designed for 32 architecture and can't be compiled for 64-bit easily.
There are plenty of people who would be willing to help. Perhaps you could explain exactly how your libraries are so tightly coupled to the architecture.
BTW. I tried both 64-bit version and 32-bit jvm + compatibility libraries on 64-bit linux. Second variant rocks (less memory consumption).
I'm not sure what you mean. I've tried running the IDE using a 32bit JVM and ia32-libs. It doesn't work; at least not on Debian Pure64. Besides, you don't tell Windows users to run their IntelliJ in an OSX PowerPC chroot. Our enterprise upgraded to x86_64 for a reason and we are required to develop on it. Incidentally, we write Java apps largely for platform independance.
We can't do that. Some of our libraries are designed for 32 architecture
and can't be compiled for 64-bit easily.
BTW. I tried both 64-bit version and 32-bit jvm + compatibility
libraries on 64-bit linux. Second variant rocks (less memory consumption).
IK
Dave Whitla wrote:
There are plenty of people who would be willing to help.
Perhaps you could explain exactly how your libraries are so tightly coupled to the architecture.
I'm not sure what you mean. I've tried running the IDE using a 32bit JVM and ia32-libs. It doesn't work; at least not on Debian Pure64. Besides, you don't tell Windows users to run their IntelliJ in an OSX PowerPC chroot. Our enterprise upgraded to x86_64 for a reason and we are required to develop on it.
Incidentally, we write Java apps largely for platform independance.