ok, i finally parsed all the other emails and figured out what
was happening.
first, my mistake in that i was convinced that i was, in fact,
working with a downloaded binary distribution, which the docs
assured me already had JAI support compiled in, so i was baffled
why FOP couldn't find the JAI libs.
silly me.
i'd forgotten (duh) that i'd actually downloaded a recent
CVS maintenance branch and, yes, i had built it. i went back,
built it again, and noticed that, at the JAI step, there was
no confirmation of JAI support.
once i copied both jai_code.jar and jai_codec.jar into
{fop}/lib, the build then confirmed that, yes, JAI support
was being built in since the build found the JAI libs.
mystery solved. and yes, a more informative error message
would have been handy. :-)
just to confirm, once the build is done, i can copy fop.jar
and the two jai jar files to wherever i want, and things will
work fine. which i seem to have just confirmed.
and also to confirm, there is no need for the other two
JAI files? that is, libmlib_jai.so or mlibwrapper_jai.jar?
and, finally, does one do the same process for Jimi?
or is that more straightforward?
thanks for everyone's patience. argh.
rday
p.s. and, look ma! no fop.sh. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
