Re: Octave with FLTK backend on Mac OS X?

[Ben Abbott]

On Feb 9, 2010, at 8:28 AM, Matthias Brennwald wrote:

> On Feb 9, 2010, at 2:02 PM, Ben Abbott wrote:
> 
>> On Feb 9, 2010, at 3:12 AM, Matthias Brennwald wrote:
>> 
>>> Dear all
>>> 
>>> I'd like to try the FLTK backend on my Mac OS X box. I currently use
>>> the Octave version from MacPorts, which does not include the FLTK
>>> backend (for reasons I do not really understand). What are my options?
>>> 
>>> Matthias
>> 
>> I build Octave from the sources, but use Fink to satisfy its dependencies. I 
>> expect the MacPorts can also satisfy all dependencies.
>> 
>> If you'd like more info let me know.
>> 
>> Ben
> 
> Ok. How do I figure out which dependencies I need to install? I guess I've 
> got most of them if I installed Octave from MacPorts. But I propably also 
> need FLTK -- and maybe others? Do you know/understand why the MacPorts 
> version of Octave does not have FLTK?
> 
> Matthias

I documented my method for building using Fink's dependencies at the link 
below. I expect building with MacPorts will be similar.

        
http://www-old.cae.wisc.edu/pipermail/octave-maintainers/2010-January/014570.html

Once you're successful with MacPorts, we may want to document the process for 
Fink and MacPorts at Octave Forge.

Regarding what MacPort dependencies are required, they are listed at the link 
below.

        http://www.macports.org/ports.php?by=name&substr=octave

To enable the FLTK backend, you can install FLTK 1.1.10 from MacPorts

        http://www.macports.org/ports.php?by=name&substr=fltk

The developer's sources require additional dependencies since 3.2.x. 

        Automake >= 1.11 
        Libtool >= 2.2.2 
        Autoconf >= 2.6.0 
        flex >= 2.5.30

MacPorts has the following available (for each, you want the 1st port listed)

        http://www.macports.org/ports.php?by=name&substr=automake
        http://www.macports.org/ports.php?by=name&substr=Libtool
        http://www.macports.org/ports.php?by=name&substr=Autoconf
        http://www.macports.org/ports.php?by=name&substr=flex

The MacPort's flex may not play well with Apple's Xcode toolset. So it will 
might be installed in a location the default path does not point to. If the 
MacPorts flex doesn't show up in your shell's path by default, be sure to add 
its path to the beginning of the path when you try to build.

Ben

p.s. I've cc'd the maintainer's list in the event someone else wants to build 
the developer's sources using MacPorts to satisfy the dependencies.