Re: building docs

[Daniel J Sebald]

On 12/01/2013 10:43 AM, John W. Eaton wrote:
> On 12/01/2013 11:29 AM, Rik wrote:
>
> > I think the best fix is to make sure that Octave calls the CLI version
> > whenever a non-interactive invocation of octave is used (--eval without
> > persist or the name of an m-file to run in batch mode).
>
> The --eval code or the m-file could call functions that display graphics
> or UI objects. It might work to run octave-cli, but in the future when
> we are using Qt widgets for graphics and UI objects you'll need to have
> the version of Octave linked with the GUI libraries.

Good point, generally speaking.  But the first lines of the script that 
generates EPS files for the documentation is

function plotimages (nm, typ)
  graphics_toolkit ("gnuplot");
  set_print_size ();
  hide_output ();
  if (strcmp (typ, "png"))
    set (0, "defaulttextfontname", "*");
  endif
  if (strcmp (typ, "eps"))
    d_typ = "-depsc2";
  else
    d_typ = ["-d", typ];
  endif

That is, the script changes the toolkit.  The Qt widgets graphics 
wouldn't support the creation of EPS files.

Making the build process not depend upon a functioning GUI is the main 
point, e.g., login remotely via ssh where Qt won't necessarily run, even 
though for others using the system locally the GUI runs fine.

Dan