[Top][All Lists]

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

[Octave-bug-tracker] [bug #37541] fltk-related defuns should be built ev

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #37541] fltk-related defuns should be built even without fltk support
Date: Thu, 11 Oct 2012 16:56:07 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0.1

Follow-up Comment #2, bug #37541 (project octave):

Thanks for the feedback Rik.

I don't see any error handling that you are describing at a higher level, for
example here's what I see when I build with no FLTK:

octave:1> available_graphics_toolkits
ans = 
  [1,1] = fltk
  [1,2] = gnuplot
octave:2> graphics_toolkit fltk
error: feval: function '__init_fltk__' not found
error: called from:
error:   /home/mike/src/octave/default/scripts/plot/graphics_toolkit.m at line
66, column 5

Point taken, this could be handled in the graphics_toolkit() function.

Another reason, though, (and this could certainly qualify as nitpicking :)) is
to ensure that the DOCSTRINGS files are identical in every build no matter how
configure was invoked. Currently, these FLTK internal defuns are the only
difference I see when I build with everything enabled and with nothing enabled
(--disable every possible option).

Here are some examples of other internal defuns that are compiled even with
their corresponding optional dependencies disabled:  __delaunayn__, __glpk__,
__magick_read__, __magick_write__ 

If you want to keep the FLTK conditional as is, is there any reason to keep
internal functions in the built DOCSTRINGS files? They are filtered out by
mk_doc_cache, could they be filtered out at an earlier stage?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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