so the questions as in the title, I need to run my server application in Tomcat on a System which is 32 bit Windows XP, I am working and compiling on my 64 bit Windows 7 in Eclipse. How do I compile it to 32 bit, what do I need to do? I assume it won't work on the 32 bit Windows when I'm compiling it on a 64 bit machine?
Java doesn't build 32-bit or 64-bit applications - bytecode is portable across different bit architectures.
The only exception is native libraries that you might be using in your code. If there are any then you will have to manually compile those for the respective platform. Otherwise the java code is totally portable across 32-bit and 64-bit platforms.
The problem is your JNI DLL, which needs to be compiled for 32-bit to match the 32-bit JRE.
Java is independent of the OS.
You can compile with your 64bit machine and run this on a 32bit computer as long as this computer has a 32bit VM.
If you're still searching for some "simple" solution, one would be to install a 32 bit os in a virtual machine and run eclipse from there.. Very ugly I know, but it works.
Another approach is mentioned here. How to launch java swing app which used precompled DLL from cmd?
You could install a 32bits jdk on a 64bits machine. point the JAVA_HOME to this jdk and use it. It
Related
Here are some details about my system:
Windows 7 (64-Bit)
JDK 1.8.0_05 (64-Bit)
JDK 1.7.0_51 (32-Bit)
Eclipse - Luna 4.4.0 (64-Bit)
Although my eclipse uses the 64-bit version of Java, I want to compile a Java program using the 32-bit version through the terminal.
Any suggestions how I can do that?
If you find that the Windows or Linux or Mac or 32-bit or 64-bit compiler produces a different output, this is most likely a bug (unless the compiler runs out of memory) Note: Eclipse has it's own compilers and it might generate different .class files. Usually this doesn't matter however when it does it can lead to subtle inconsistencies. I would make sure you always use the Oracle or IBM compiler if you can to avoid these issues.
However, you can specify the bit-ness in the same way you specify the version by setting the PATH or using the whole path when you run it. If you use an IDE, this is what it does for you, and many, many other things.
My java programs are stored in my flash drive.
I just want to know if it is possible to store the JDK in the flash drive so that I can compile and run my programs at any computer (i.e., portable).
Thanks in advance.
The JDK itself is a compiled application. You can define JAVA_HOME to point to your JDK wherever you want, to force compilation. However, you can't take a 64 bit JDK and run it on a 32 bit Windows machine, and likewise you can't take the Windows version and run it on Mac or Linux, so no it's not portable.
I am developing a windows application.
I need to create an installer(a common installer for both 32 bit and 64 bit windows OS) for that, for that I am using Install4J software.
I developed in Windows 32 bit, jdk 1.7.
Installer working fine in 32 bit windows os, but when I try to create installer in win 64 bit os, it is throwing me an error like java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM
Please help to sort out this..
The problem is that there are separate "swt.jar" files for 32bit and 64bit Windows JVMs, and they are not interchangeable. You can't use the 32bit Windows JAR on a 64bit Windows JVM ... or the other way around. (AFAIK, the fundamental impediment is in Windows and the JVM rather than SWT.)
One possibility is to do some classloader tricks, and dynamically choose between different JARs depending on the platform that your app detects at runtime. The installer would need incorporate both flavours of the SWT JAR ... with different names.
This answer goes into more detail: Supporting SWT on Windows/Mac & 32bit/64bit
Well that is just because when u install program into the Program files that will install only 32-but and will load 32-bit libraries so u can do one thing very simple solution of that just install your program in the the Program files x86 if u have 64 bit system.
that work for me and might work for u too.
I got eclipse RCP juno 64 bit crashes on Mac OS X, and I posted this question in StackExchange Mac - https://apple.stackexchange.com/questions/67104/eclipse-rcp-juno-64-bit-crashes-on-mac-os-x. And, I guess I have no choice but to use 32 bit version now.
Is it just OK to use 32 bit eclipse on 64 bit OS (Lion), and 64 bit java (java 1.7 sdk)?
How about the code compatibility? Can I open the workspace with 64 bit eclipse created from 32 bit eclipse?
What's the difference between 32bit and 64bit eclipse? Or, what are cons and pros between them? Why do they keep 32bit eclipse in 64 bit world?
You need to 32-bit JVM to use 32-bit Eclipse, and you need 64-bit JVM to use 64-bit Eclipse.
Note that a 32-bit JVM can run on 64-bit OS. I have Windows 7 64-bit with both 32-bit and 64-bit JVMs installed. I do have to sometimes edit eclipse.ini file to make sure that the correct JVM is selected.
There are no workspace compatibility differences between 32-bit/64-bit variants of the same version. The native bits that are 32-bit/64-bit specific are for native UI and file system integration.
If you are running 64-bit OS, you should favor using 64-bit JVM/Eclipse. Doing so will avoid a lot of memory issues that plague 32-bit installs. For instance, it isn't uncommon for a 32-bit JVM/Eclipse to fail to start with -Xmx1024m due to address space fragmentation.
The 32-bit Eclipse builds are still produced because there are still quite a few 32-bit OS installs out there.
I am working on a project where I have to capture images from webcam.I thought of using LTI-CIVIL api for this purpose. But it does not work on 64-bit os(I tried to run demo programs on windows 7(64-bit), it didn't work).
Please let me know how to make LTI-CIVIL api work with 64-bit os.Or If you know any other API(Open source or at least free) which will work with 64-bit os.Thanks in advance.
Not versed on LTI-CIVIL, but has native implementations (swt and capture dll) for Linux and Mac 64bit but only Windows 32 x86, so try to use a 32bit JRE in Windows x64 in order to link the 32bit dll of LTI-CIVIL. this kind of problems are related to the JRE, not the Windows architecture (32 vs 64).
I had the same problem, after i change from Jar 7 to Jar 6 the problem is gone