 |
 |
Hi, Fabrizio #2: I will put in place a configurable path similar to the other ones. If no directive is given it can try to deduce it from the environment or from a list of common install directories. I also wanted to clean up some of the makefiles to have a more uniform structure. #3 I think the building of the library should be a configure option (default=off) Cheers, Derek On Monday 12 December 2005 17.59, Fabrizio Furano wrote: > Hi all, > > I am about to commit the JNI implementation of the XrdClientAdmin > functions, but I'd like to understand what you guys think that's > preferable to do. > > The JNI impl consists of: > - a new XrdClientAdminJNI.so library (with its sources, of course) > - a java class which wraps this lib. > > Question #1: Are we willing to create a new subdir for that? Right now > it is together with all the XrdClient stuff. > > Question #2: Java path mangling. At this time I put fixed paths for > the JNI include files in the classic makefile and in the Makefile.am. > But we need to find out the java location in the .configure . Any hints > for doing this will be greatly appreciated, since it will save to me > hours of tweaking. > > Question #3: The java class. Generally, do we need to provide it as a > compiled class? In my opinion we could skip and leave the compilation up > to the package that's going to use it. But I have no experience in this, > so I ask. > > Happy answering, thank you. > > Fabrizio