On Mon, 19 Dec 2005, Mark Taylor wrote:
> I have now checked in a version of JNIHDS which uses only the C interface.
Excellent!
> Apart from a couple of facilities dropped because they're not in
> the new interface, as far as I can see everything seems to work OK,
Which ones? The CMP routines or the datGetNx/datPutNx routines?
> The build still links against libcnf because that's what star/bin/hds_link
> andn star/bin/err_link do.
>
CNF isn't really a problem but could be restricted to just the Fortran
wrappers (and have a libhdsf like there is a libemsf). It's ems not err
that is used and that can't be removed (it's buried deep) unless you do
the obvious thing and replace the error handling library with something
Java-like that throws exceptions (was an ems replacement written for the
Java "A-Task" stuff?).
The real problem is CHR that is linked in for the CMP routines and that
brings in fortran libraries.
If it makes life easier I can make "hds_link Conly" (cf ems_link) only
link in the C routines and separate the fortran interface into a separate
library. (I was goiong to do that when I had finished the Nx routines but
this seems to be higher priority).
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|