David, If you allow me a 3 weeks time I would put libtools scripts which would work on Unices and Windows both. The main problem I notice with libtools, the way it is implimented in LessTif, NetCDF, and ImgeMagic, is that libtools tries to create *.so files also on Windows. On Windows a DLL is always an executable and can never have an internally defined symbols. All symbols must be exported from DLL. The *.lib or *.a works only as a place holder.
If you try to build NetCDF or Lesstif on Windows using --enable-shared=yes, libtools will barf at you, "undefined symbols are not supported at the plateform i686-cygwin32" and will create rubish libxxx.a and libxxx.la. A while ago I rewrote the configure scripts for LessTif for Cygwin so creates DLLs on Windows and *.so on Linux. I never got a chance to send them to Rick, then in a disk crash I lost the copy. The point is if you simply adopted libtools using conventional Unices styles, you would break the libraries for Windows. Suhaib > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of David L. > Thompson > Sent: Thursday, January 13, 2000 6:22 PM > To: opendx2-dev@lists.berlios.de > Subject: Re: [opendx-dev] javadx shareable libraries > > > This is some of the stuff that libtool takes care of. It can take and > put the appropriate information into the header of the library and > binaries for linkages. In fact, this is how I noticed that the netcdf > and other libraries need to have shareable versions installed when > using javadx (libtool told me so.). If nothing else, I may add the > libtool functionality just for the javadx branch of the tree. But I'd > rather add full functionality right off the bat. > > One of the things that I'd like to have available while adding this > functionality is a test set that I could build for checking validity > of libs and executables. Do we have a module that would test a fair > amount of the dxlibs when linked in as an inboard, outboard, and > loadable and executed from a script? I already have the autoconf > stuff set up for most platforms for a loadable and to add the > functionality for outboard and inboard shouldn't take too much. > Something that would require DXlite and libDX might be good. (On that > thread, is there a chance that libDX could be broken into two > libraries? DXlite and OtherDX? If they were shareable, then libDX > wouldn't have to be so big.) > > Can someone send me a good dx-link program that could test the DXL > library? (Why does the shareable code with javadx only link to a > subset of DXL?) > > Opinions, suggestions? > > David > > >Well, thanks, but again, LD_LIBRARY_PATH isn't working for me on > aix 4.3.2. > >When it seems to work it is only a coincidence, the load > succeeds when the > >libMagick.so shared lib is fortuitously in one of the > directories in dxexec's > >header. > >Pete > > .................................................................. > ........... > David L. Thompson The University of Montana > mailto:[EMAIL PROTECTED] Computer Science Department > http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812 > Work Phone : (406)257-8530 >
