octave-maintainers
[Top][All Lists]
Advanced

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

gui branch merged to default


From: John W. Eaton
Subject: gui branch merged to default
Date: Mon, 13 Aug 2012 11:29:44 -0400

The gui branch has been merged to default and is now closed.

If the configure script detects the necessary Qt tools and libraries,
the GUI will be enabled.  You don't need to do any special qmake
commands yourself or cd to the gui subdirectory to build the
GUI-enabled Octave.  You just need the normal

  autogen.sh
  configure
  make

steps.

If you have trouble building the GUI, you can use --disable-gui when
running configure.

We now build two binaries, octave and octave-cli.  The octave-cli
binary is never linked with the GUI toolkit, so if you don't need the
GUI, you can run octave-cli to avoid wasting memory and startup time.
If you build the GUI, octave is linked with the GUI toolkit libraries
and starts the GUI by default.  Otherwise, octave and octave-cli are
identical.

Octave's new --no-gui option disables the GUI at startup.

If you run a command like

  octave --eval "x = 13"

or

  octave myscript.m

the GUI will not be started unless you also specify --persist or use
the new --force-gui option.

The run-octave script now starts octave with the GUI by default.  If
you don't want that, you can pass -cli to run-octave to run the
octave-cli binary instead, or you can use the --no-gui option and that
will be passed to Octave to disable starting the GUI.

Thanks to Jacob and everyone else who has worked on getting the GUI to
this point.  There is still some work to do before it is ready for
release, but it is looking really good now.

Enjoy,

jwe


reply via email to

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