dx -builder and dx -edit now write *.make files (for user modules and javadx creations) that work on a bunch of platforms (I've tested linux, aix, sgi, and solaris). If you set DXARCH, dx -builder will even build and run your module interactively.
One of the "design" changes is that the dx-generated makefiles try to be architecture-independent. Architecture specifics are now supposed to be sequestered in lib_$(DXARCH)/arch.mak (created by dx's configure). Over time this should mean less maintenance and more reuse. Also, components (e.g. java DXServer and your javafied network) should build, install, and run together without a lot of fuss. Some of the *make files for various dxsample sample code (e.g. user interactors ) work. Truthfully at this instant I am more than a little confused about which ones do work on which platforms. If my changes to the dx tree pass muster, it will make more and more sense to whip these laggards into shape. I have left the old Makefile_$(DXARCH) files intact (which mostly do not work in the OpenDX structure) in the meantime. regards, Pete
