octave-maintainers
[Top][All Lists]
Advanced

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

Re: integrating octave-gui and octave main programs (was: Re: Last commi


From: Michael Goffioul
Subject: Re: integrating octave-gui and octave main programs (was: Re: Last commit may break your builds)
Date: Thu, 9 Aug 2012 21:14:44 +0100

On Sun, Aug 5, 2012 at 10:01 PM, John W. Eaton <address@hidden> wrote:
On  5-Aug-2012, Michael Goffioul wrote:

| With the change 
|
| http://hg.savannah.gnu.org/hgweb/octave/rev/3d7a7ae53bbf
|
| building the GUI should be pretty well integrated with the octave build system.
| It adds support for resource files compilation and for the "dist" target.

Thanks.  I checked in a few more improvements here:

  http://hg.savannah.gnu.org/hgweb/octave/rev/3735a0e783cb

Now we don't try run qmake or look for moc, uic, or rcc unless qmake
is available.  Running make from the top-level directory will also
build the GUI, so you don't have to cd to the gui directory and run
make separately.  I also defined a HAVE_QT flag in config.h, but it's
not used yet.

Note that if you don't have Octave installed, Octave will not know
where to find the core .m files.  It will be searching for them in
the installation directory tree, not the source tree.  To fix that, we
need a "run-octave" script for the GUI.  But before doing that, I
think we should decide how we want to integrate the "octave-gui" main
program and the current "octave" main program.  I started working on
the attached changes to do that, so that if we are building the GUI,
then the "octave-gui" main program can be THE Octave program.  It's
not finished yet, as we need an option for "--disable-gui" and there
are some things I'm not sure about, like what should happen for things
like

  octave --eval "foo"

Without the --persist option, should a command like this start the GUI
and execute the command in the terminal window, then immediately close
the GUI?  Or should it skip starting the GUI?  With --persist, it
seems obvious that it should start the GUI and evaluate the command in
the GUI terminal window.  What if the commands to be evaluated perform
some operation that requires the GUI environment?  Should we have a
--force-gui option for that case?

Here's a slightly altered version, which disables forking on Win32 platform and add the -gui flag for run-octave. At least, this allows to run the octave GUI form sources properly. If there's no objection, I suggest to submit it now and work on extensions afterwards.

Michael.

Attachment: gui-main
Description: Binary data


reply via email to

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