Re: QtHandles: Qt-based toolkit with uicontrol/uipanel support

[Michael Goffioul]

On Mon, Oct 10, 2011 at 3:54 PM, Ben Abbott <address@hidden> wrote:
>> This is a simple post-build step that I used to copy all targets into
>> the top-level directory, so you can directly run everything from there
>> without playing with PATH and octave path. This is of course not
>> mandatory. What do you have in octave-qt.app/Contents/MacOS/ ?
>
> Nothing.
>
> $ ls tool/octave-qt.app/Contents/MacOS/
> octave-qt
>
> Should I put something there?

Oh, I see. I think the problem is that I haven't a clue about how Mac
OS X is working. The simply post-build copy rule I added is based on
the assumption that an executable can be a regular file in the current
directory, but it looks like in Mac OS X, things are different. For
the time being, I suggest you create the required directory at
top-level manually. This little copy rule is just a trick to simplify
testing and by no mean a mandatory thing in production.

>>> In file included from __init_qt__.cpp:30:
>>> Backend.h:58: error: conflicting return type specified for ‘virtual bool 
>>> QtHandles::Backend::initialize(const graphics_object&)’
>>> /opt/local/include/octave-3.5.0+/octave/../octave/graphics.h:2033: error:   
>>> overriding ‘virtual void base_graphics_toolkit::initialize(const 
>>> graphics_object&)’
[snip]
> My tip is ...
>
> $ hg tip
> changeset:   13308:9a83ec29aec9
> tag:         tip
> user:        Ben Abbott  <address@hidden>
> date:        Mon Oct 10 08:22:25 2011 -0400
> summary:     Fix regression introduced by e9f6a6edec42.
>
> Perhaps the problem is that I'm clueless? ;-)
>
> How can I have this link to my development build as opposed to the installed 
> version of Octave?

What I usually do under Linux is:

PATH=/where/octave/is/installed/bin:$PATH qmake -recursive
make
LD_LIBRARY_PATH=/where/octave/is/installed/lib/octave-3.5.0+:$LD_LIBRARY_PATH
./octave-qt

Michael.