octave-maintainers
[Top][All Lists]
Advanced

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

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


From: Ben Abbott
Subject: Re: QtHandles: Qt-based toolkit with uicontrol/uipanel support
Date: Wed, 12 Oct 2011 18:24:23 -0400

On Oct 11, 2011, at 3:56 AM, Michael Goffioul wrote:

> On Tue, Oct 11, 2011 at 1:45 AM, Ben Abbott <address@hidden> wrote:
>> On Oct 10, 2011, at 1:15 PM, Michael Goffioul wrote:
>> 
>>> On Mon, Oct 10, 2011 at 4:58 PM, bpabbott <address@hidden> wrote:
>>>> 
>>>> Can this be done from a mercurial development directory? What about the
>>>> include path?
>>> 
>>> I don't think so. You should provide a specific --prefix arguments
>>> when configuring
>>> octave from dev sources, such that you can install it in parallel with 
>>> another
>>> octave install. Then you can do the same as Martin.
>>> 
>>> Michael.
>> 
>> Ok. I installed an octave built from today's sources. Now I'm able to build 
>> octave-qt (without the debug libs).
>> 
>> Unfortunately, it crashes when I try to run it.
> 
> If possible, can you generate a backtrace. Of course, in your case,
> I guess it's gonna be tricky as you didn't compile with debug enabled.
> 
> For other reasons, I also have to compile QtHandles in release mode,
> that is, I need to link it against release versions of Qt libs. However,
> I still want to compile QtHandles itself with debug enabled and that's
> the reason of all the win32-specific tricky things in common.pri
> (use debug flags in release qmake variables)
> 
> If you manage to do something similar for mac, you might be able
> to generate a useful backtrace.
> 
> Michael.

I've found the reason why I didn't have all the debug libs and have corrected 
the problem.

I have attached the crash log reported by MacOS. I can provide a backtrace as 
well. How would I run octave-qt in gdb?

Ben


reply via email to

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