gstep-base Re: [OGo-Developer] OGo Invoice Application
Adam Tauno Williams
developer@opengroupware.org
Thu, 27 Dec 2007 09:37:43 -0500
--=-aA24j1oaLOVBRE5DyfRm
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
> > > DLL hell replaced by CLASSPATH hell.
> > Well, from a deployment perspective it would be just like now ... if =20
> > we get it compiled with GCJ. It produces real binaries and regular =20
> > shared libraries. I think not having those is one of the bigger Linux =20
> > deployment "issues" with Java, pretty similiar to why GNUstep =20
> > deployment roots are annoying for server applications.
> Cool. =20
> I host a number of Java applications, but they are all straight-up
> normal in-the-JVM apps. I've had horrible experiences trying to host
> multiple apps in the same Tomcat instance, for example, which I though
> was the whole bleedin point of an application container - deploy and go.
> (that and figuring out what is going on inside Tomcat's little mind is
> no fun either)
> I've never encountered GCJ and didn't realize it produced "real"
> binaries. Are they "real" in the sense that they can be copied to a
> machine without a JVM and run or are they "real" like Mono AOT libraries
> (which run like binaries but still need the original assembly)?
Never mind. The website provides a beautifully direct answer to my
question:
http://gcc.gnu.org/java/
<cite>
GCJ is a portable, optimizing, ahead-of-time compiler for the Java
Programming Language. It can compile Java source code to Java bytecode
(class files) or directly to native machine code, and Java bytecode to
native machine code.
Compiled applications are linked with the GCJ runtime, libgcj, which
provides the core class libraries, a garbage collector, and a bytecode
interpreter. libgcj can dynamically load and interpret class files,
resulting in mixed compiled/interpreted applications.
</cite>
--=-aA24j1oaLOVBRE5DyfRm
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQBHc7i3LRePpNle04MRAvaMAJwM2myRrlEoBBaCxvy+TNFT6/BtsACcC3+P
t2HwAWS4q9xI4OCeo075miw=
=lnL6
-----END PGP SIGNATURE-----
--=-aA24j1oaLOVBRE5DyfRm--