I mean as part of the arch-dep process. THe arch-dep process requires a complete build, simply excluding everything else from the package.
Of course the jars are still required. They have things in them other than .class files. On Sat, 2005-04-30 at 08:49 +0200, Michael Koch wrote: > On Fri, Apr 29, 2005 at 10:42:08PM -0500, Jerry Haltom wrote: > > > I'm not in favour of compiling on the user machine. Also, don't forget > > > if the package is well done, only the native part will be compiled, the > > > jars are arch-indep so they'll not be re-compiled by the buildd's. > > > > How so? > > > > GCJ needs the .jar to compile the .so. That means the jars have to be > > built, but they don't have to be packaged. Am I right? > > We have to package the jars. At least for all non-gcj-like runtimes which are > all except gcj itself currently. > > > Michael > -- > Escape the Java Trap with GNU Classpath! > http://www.gnu.org/philosophy/java-trap.html > > Join the community at http://planet.classpath.org/ > > -- Jerry Haltom <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
