Platform, compiler & JRE requirements

Platforms

We're constantly adding new platforms to the mix but most of our platform ports were initiated by customer demand. Contact us if you need JunC++ion on a yet unsupported platform and we can discuss what's involved in doing a port for you.

Platform	Comment
Windows 98 and later on IA32.	This list currently excludes Vista as we have not yet verified correct operations on that version of Windows.
Linux on IA32	We're building on SuSE 9.3 and our customers are running successfully on RHEL 3 and 4. We don't make any warranties for other distros but there's no reason it shouldn't work. As far as we can tell, our build creates a dependency on GLIBC_2_3 but that could probably be "fixed" if someone needed it on a distro that does not have GLIBC_2_3.
HP-UX 11.11i PA-RISC	Freshly completed port (as of 8/2/06)
AIX 5.2
Solaris on Sparc
MacOS-X 10.4	Still in progress.

Please check the runtime FAQs for information about running mixed-language on specific platforms.

Compilers

We always strive to support at least the "platform native" compiler. While there has been occasional demand for other compilers, it never amounted to much. Just as with platform ports, we're always willing to entertain compiler ports if you're seriously interested and willing to commit yourself.

Compiler	Comment
Microsoft Visual C++ 6 Microsoft Visual C++ .NET Microsoft Visual C++ 2002 Microsoft Visual C++ 2003 Microsoft Visual C++ 2005	We imply the Windows platform here. By default, we generate project files for VC++6 but you can change that default to different versions. We cannot yet generate VC++2005 project files.
g++ 3.2, (3.3), 3.4, 4.0.1+	On Linux we support all relatively modern versions of the GNU C++ compiler with the exception of 3.3 and 4.0.0. Applications compiled with g++ 3.3 could have some runtime issues and g++ 4.0.0 simply does not work whereas 4.0.1 works fine.
VisualAge C++ 6	On AIX.
Sun Workshop 6u1 or higher	On Solaris Sparc.
aCC 3.50	On HP-UX.

 

Java Runtime Environments

In theory, JunC++ion should work with just about any Java Runtime Environment. In practice, we require a fairly complete and correct implementation of the Java Native Interface (JNI). Such implementations have become fairly commonplace since Sun JRE 1.2.1 and you can probably use any fairly modern Java2 or later JVM in in-process mode.

Sometimes a later version (particularly a point zero version) might introduce some regressions that could impact an integration solution like JunC++ion. In all likelihood, this is not going to be an issue, but to be certain, we only qualify JunC++ion with JREs we have tested with in the past.

A JRE is required both at development and at runtime. The code generator relies on at least a JRE version 1.4. This version requirement is independent of the runtime requirements. Even if you're going to deploy your C++ application with a JRE 1.2.2, the code generator still needs a JRE 1.4. On most platforms we bundle such a JRE as part of the code generator download, so you don't have to worry about this requirement.

At runtime, you need a JRE on the host on which your C++ application is deployed—if you're using in-process mode. If you're deploying in out-of-process mode, you need the JRE only on the machine that hosts the Shared JVM server.

In-process JRE	Comment
Sun JRE 1.2.2 - 1.5.x	There are no known limitations for any Sun JREs.
IBM JRE 1.4	There are no known limitations for the IBM JRE but we have only tested with the 1.4 version.
BEA (JRockit) 1.5	There are no known limitations for the BEA JRE but we have only tested with the 1.5 version.

Shared JVM mode

In out-of-process (Shared JVM) mode, the JunC++ion shared JVM server requires at least a JRE 1.4, otherwise the in-process constraints apply.

Java Development Kits

At development time, on some platforms, you might need a JDK if you're using callbacks.