[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Qt/gui on MacOSX (was: 4.0 release goals)
From: |
Ben Abbott |
Subject: |
Re: Qt/gui on MacOSX (was: 4.0 release goals) |
Date: |
Sun, 04 Nov 2012 18:40:37 -0500 |
On Nov 4, 2012, at 6:23 PM, Michael Goffioul wrote:
> On Sun, Nov 4, 2012 at 5:43 PM, Ben Abbott <address@hidden> wrote:
>
> On Nov 1, 2012, at 12:59 PM, Jordi Gutiérrez Hermoso wrote:
>
> > I would like to propose some rather ambitious goals for 4.0, and I
> > think we should be bold enough to use a major version number.
> >
> > In case you missed it in the help list, there's an interesting thread
> > about the GUI. Israel Herraiz forked it and stabilised it:
> >
> >
> > http://octave.1599824.n4.nabble.com/When-will-the-new-GUI-be-ready-tp4645798p4645846.html
> >
> > I would like to prioritise getting the GUI stabilised so we can start
> > contemplating making a release. I think our 4.0 release goals should
> > be:
> >
> > - fltk enabled by default
> > - Stable GUI
> > - JIT compiling working
> > - Windows and Mac OS X binaries
> >
> > We're already made many inroads into many of these goals. What do you
> > guys think, can we do it?
> >
> > - Jordi G. H.
>
> Since the gui build process was integrated into the CLI build process, the
> gui has not run under MacOS X. I'm not certain, but I think gnuplot had a
> similar problem.
>
> http://www.digipedia.pl/usenet/thread/12789/10528/#post10548
>
> When I try to run the gui, I get the error below (repeated 16 times). Which
> is the same error encountered by the gnuplot developers.
>
> The process has forked and you cannot use this CoreFoundation functionality
> safely. You MUST exec().
> Break on
> __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__()
> to debug.
>
> Fixing this is beyond my abilities. but I can test patches.
>
>
> I've had a quick look and my understanding is that somewhere we use a
> CoreFoundation API before forking, which is not allowed by Mac OS X (God
> knows why...), if you also want to use CF API after forking.
>
> AFAIK there aren't many places in octave where there's a direct access to the
> underlying graphics system, one of them is display_info class. Indeed, this
> class is used before forking, in octave_starting_gui (libinterp/octave.cc).
> So as first try, you could edit src/main.cc and replace the call to
> octave_start_gui() with true to see whether it makes any difference.
>
> Michael.
Definitely made a difference, but I can't tell if it is an improvement or not.
The error no longer shows up, but neither Octave nor the gui starts either.
There is just a short delay and the shell prompt returns.
Ben
- Re: 4.0 release goals, (continued)
- Re: 4.0 release goals, Ben Abbott, 2012/11/01
- Re: 4.0 release goals, Philip Nienhuis, 2012/11/01
- Re: 4.0 release goals, Michael D. Godfrey, 2012/11/01
- Re: 4.0 release goals, tom yengst, 2012/11/03
- Re: 4.0 release goals, Ben Abbott, 2012/11/04
- Re: 4.0 release goals, Michael Goffioul, 2012/11/04
- Re: Qt/gui on MacOSX (was: 4.0 release goals),
Ben Abbott <=
- Re: Qt/gui on MacOSX (was: 4.0 release goals), Michael Goffioul, 2012/11/04
- Re: Qt/gui on MacOSX (was: 4.0 release goals), Ben Abbott, 2012/11/05
- Re: Qt/gui on MacOSX (was: 4.0 release goals), Michael Goffioul, 2012/11/05
- Re: Qt/gui on MacOSX (was: 4.0 release goals), Ben Abbott, 2012/11/05
- Re: Qt/gui on MacOSX (was: 4.0 release goals), Michael Goffioul, 2012/11/05
- Re: Qt/gui on MacOSX (was: 4.0 release goals), Ben Abbott, 2012/11/05
- Re: Qt/gui on MacOSX (was: 4.0 release goals), Michael Goffioul, 2012/11/05
- Re: Qt/gui on MacOSX (was: 4.0 release goals), Ben Abbott, 2012/11/05
- Re: Qt/gui on MacOSX (was: 4.0 release goals), Ethan A Merritt, 2012/11/05
- Re: Qt/gui on MacOSX (was: 4.0 release goals), Michael Goffioul, 2012/11/05