Brian,

I've checked some changes into the Kissme CVS that should solve
your problem.  There is now a --with-gnu-classpath-build option
for specifying the GNU Classpath build dir when it is different
from the GNU Classpath build dir.

> > cd "${KISSME_CVS}" && ./configure --prefix=${KISSME_PREFIX}
> > --enable-use-zips --with-gnu-classpath=${CLASSPATH_CVS}/build
> > --with-classpath-install-dir=${CLASSPATH_PREFIX} >> ${LOG} 2>&1

You can now do this:

  cd "${KISSME_CVS}" && ./configure --prefix=${KISSME_PREFIX} \
    --enable-use-zips --with-gnu-classpath=${CLASSPATH_CVS} \
    --with-gnu-classpath-build=${CLASSPATH_CVS}/build \
    --with-classpath-install-dir=${CLASSPATH_PREFIX} >> ${LOG} 2>&1

or simply

  cd "${KISSME_CVS}" && ./configure --prefix=${KISSME_PREFIX} \
    --enable-use-zips --with-gnu-classpath=${CLASSPATH_CVS} \
    --with-classpath-install-dir=${CLASSPATH_PREFIX} >> ${LOG} 2>&1

[Aside: I should probably remove the dependencies on the GNU classpath
source/build directories entirely.  But that means de-supporting the
old "kissme-classpath" way of building the runtime classes for kissme.]

-- Steve



_______________________________________________
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath

Reply via email to