Hi, > > Am I widdling into the wind by submitting this or is libgcj just that > > bit too far from classpath-0.92? > > libgcj will not work if what you want is a runtime for IKVM or similar. That's what I thought when I was speaking with the ikvm guys > That being said, I'm not sure it makes sense to build and install GNU > Classpath independently from another JVM project. I think we want JRE > projects and related technology to get installed using the JPackage > alternatives system. Can you describe your GNU Classpath use-cases a > little more? For instance... you're building Limewire with what? And > to run on what JRE? I'm building limewire against classpath. It should run on the same JVM that OOo runs on (gcj IIRC). ikvm needs classpath to build happily As it stands, ikvm is my top priority as it's currently breaking the FE packaging rules of being a binary only package (it was accepted in like this). Limewire would be nice, but it's a big package and I doubt will be that simple to build. TTFN Paul -- "Der einzige Weg, Leute zu kontrollieren ist sie anzulügen" - L. Ron "Ich kann kein Science-Fiction schreiben" Hubbard; Lügner, Betrüger, Fixer und Wohltäter zu niemandem
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-java-list mailing list fedora-devel-java-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-java-list
