As far as specifying X11 location; if this is a need – and I have found it sometimes useful – the usual way this is done is via an X server running on your desktop system and ssh. The specifics depend on the details of the desktop system. If it is a Windows system, the inexpensive solution is the Xming X server and the PuTTY application. This page gives a summary of the setup procedure: http://www.geo.mtu.edu/geoschem/docs/putty_install.html. On a Mac, one uses XQuartz and the usual Mac terminal application. Unix-like systems run X11 natively, and one can simply use ssh from a window. For all of these, you may have to turn X Windows ssh access on on your Amazon LInux instance.
-- Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com On Sun, Apr 8, 2018 at 11:47 AM, Lars O. Grobe <gr...@gmx.net> wrote: > Hi Philip, > > don't worry about the "healthy state" of the executables. Make sure that > you have oconv ("pre-sorting" your geometry), vwrays (generating rays for > given projections), rtrace (the fundamental ray-tracer), rpict (a > ray-tracer for images), rcalc (a calculator for tabular data), and the > various generators (especially gensky). As long as they build, they will > do, and you may simply ignore build errors as long as you get what you need. > > From the lib directory, you will at least need rayinit.cal. If you are > aiming at CBDM, you also need the directional basis definitions according > to Klems, Reinhart et al. These are somewhat scattered over directorys, > best is to check your particular commands and collect them from the source > tree in one central lib-directory which you would include in your RAYPATH. > The various .cal-files have descriptions of their intended use included as > comment lines, they are useful (e.g. for interpolation, mapping, color > conversions) and definitely worth browsing, but not critical for plain > ray-tracing. > > Cheers, Lars. > >> Do you just mean that we could have ignored the X11-related compilation >> errors? (we bothered to include X11 libraries at build time to get as >> clean >> a compilation as possible, to be sure that the binaries we get out of the >> build are in a healthy state). Or do you mean this implies certain >> auxiliary files can be excluded? >> >> > _______________________________________________ > Radiance-dev mailing list > Radiance-dev@radiance-online.org > https://www.radiance-online.org/mailman/listinfo/radiance-dev >
_______________________________________________ Radiance-dev mailing list Radiance-dev@radiance-online.org https://www.radiance-online.org/mailman/listinfo/radiance-dev