octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Choosing graphics backend for documentation


From: Ben Abbott
Subject: Re: Choosing graphics backend for documentation
Date: Mon, 27 Jul 2015 12:50:21 -0400

> On Jul 27, 2015, at 12:06 PM, Rik <address@hidden> wrote:
> 
> Ben, Mike,
> 
> The scripts that generate the images are m-files in doc/interpreter.  They
> all have a subfunction called set_graphics_toolkit() which is shown below.
> 
> -- Start of Code --
> ## This function no longer sets the graphics toolkit; That is now done
> ## automatically by C++ code which will ordinarily choose 'qt', but might
> ## choose gnuplot on older systems.  Only a complete lack of plotting is a
> ## problem.
> function set_graphics_toolkit ()
>  if (isempty (available_graphics_toolkits ()))
>    error ("no graphics toolkit available for plotting");
>  endif
> endfunction
> -- End of Code --
> 
> This could be modified to check for the presence of OSMESA and attempt to
> use gnuplot if it is not present.
> 
> This check works for me
> 
> if (octave_config_info ().features.OSMESA)
>
> endif

Rik,

It would be nice if a change were made to allow a build to complete when osmesa 
isn’t present.

However, I’d also like to have print() work when the figure isn’t visible (i.e. 
I think the problem is broader than building the docs). What do you think of 
the attached patch?

Ben

Attachment: backup_osmesa_with_gnuplot.patch
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]