> Stability classification Uncommitted for all exported interfaces. Man > pages are included in the case materials directory.
Please send me those man pages, and I will put them in the case directory. > Exported Interfaces > ------------------- > > /usr/lib/swt/swt.jar > /usr/lib/swt/swt-debug.jar I believe that Public jar files on Solaris tend to go into /usr/share/lib, or a subdirectory thereof, though if this is where most other systems place the jar files, they should be made available here, even if only via a symlink. Though I'll note that at least on ubuntu, it's in /usr/lib/java. > /usr/lib/swt/libswt-pi-gtk-3349.so > /usr/lib/swt/libswt-gtk-3349.so > /usr/lib/swt/libswt-gnome-gtk-3349.so > /usr/lib/swt/libswt-cde-gtk-3349.so > /usr/lib/swt/libswt-cairo-gtk-3349.so > /usr/lib/swt/libswt-awt-gtk-3349.so > /usr/lib/swt/libswt-atk-gtk-3349.so > > Since this is a shared lib, the numbers before .so don't matter. This isn't even remotely true. Those numbers are baked into every executable that links against them, so if the library names change, anything linked against them will break. However, if these libraries are intended only to be dlopen()ed by the Java code in the SWT jar files, then as long as those classes are changed whenever these libraries are, there's no issue. But then the libraries are Project Private, and not any form of Public. > Imported Interfaces (Following are the dependacies while compiling the SWT, > they are not require to use SWT, one can install pre-compiled SWT without > these packages) > ------------------- > SUNWcairomm > SUNWpng > SUNWxwinc > SUNWgnome-common-devel The build-time dependencies are (mostly) uninteresting here. We do care about the libraries that you're linking against. I would expect that libswt-atk-gtk-3349.so likely links against one or more gtk libraries and the atk library, and will require all of those to be present on the system at run-time. The others probably have similar dependencies. Danek
