From graphics-request at octave dot org Wed Feb 15 16:29:56 2006 Subject: Second time's a charm From: Sebastien Loisel To: David Bateman , octave maintainers mailing list , octave-graphics Date: Wed, 15 Feb 2006 23:28:14 +0100 ------=_Part_11293_31258992.1140042494458 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline David, Ok, now I've autoconfiscated octave-gui and you should be able to build it. If you have QT4.1 problems though, you're going to have to sort those out..= . :-/ Over here, everything compiles and the mainwindow comes up so it's now at the same state as it was pre-autoconfiscation (octave still doesn't init right.) The tarball is here: http://www.math.mcgill.ca/loisel/octave-gui-beta.tar.g= z I strongly advise everyone but David to stay away from this. Building is standard, but it's in maintainer mode. Here's what I do. 1) Fire up an appropriate shell. I've got "shell.bat" and "shell-x64.bat" (for Windows XP x64) in that directory for that purpose. It's basically the setup from your octave.bat, then it starts sh.exe from mingw. 2) cd to the octave-gui-0.4 directory. 3) $ aclocal $ autoconf $ automake $ ./configure $ make 4) ./octave-gui After a 5 second pause (or so), a window will pop up. I haven't tested, but I don't think stdout/stderr work. So if you're going to debug, you have to use some other way. To help you out, I've declared th= e following global variable: string david_output; If you stick anything in there, it'll appear in the mainwindow when the mainwindow first appears. Otherwise I think you can open files and stuff. Right now, as an example, it prints the return code of octave_main, which i= s 1. Cheers, Sebastien Loisel ------=_Part_11293_31258992.1140042494458 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline David,

Ok, now I've autoconfiscated octave-gui and you should be abl= e to build it. If you have QT4.1 problems though, you're going to have to s= ort those out... :-/ Over here, everything compiles and the mainwindow come= s up so it's now at the same state as it was pre-autoconfiscation (octave s= till doesn't init right.)

The tarball is here: http://www.math.mcgill.ca/loisel/octave-gui-beta.tar.= gz

I strongly advise everyone but David to stay away from this.

Building is standard, but it's in maintainer mode. Here's what I do= .

1) Fire up an appropriate shell. I've got "shell.bat" an= d "shell-x64.bat" (for Windows XP x64) in that directory for that= purpose. It's basically the setup from your=20 octave.bat, then it starts sh.exe from mingw.

2) cd to the octave-gu= i-0.4 directory.

3)
$ aclocal
$ autoconf
$ automake
$ .= /configure
$ make

4) ./octave-gui

After a 5 second pause (= or so), a window will pop up.

I haven't tested, but I don't think stdout/stderr work. So if you'r= e going to debug, you have to use some other way. To help you out, I've dec= lared the following global variable:

string david_output;

If you stick anything in there, it'll appear in the mainwindow when the mai= nwindow first appears. Otherwise I think you can open files and stuff. Righ= t now, as an example, it prints the return code of octave_main, which is 1.

Cheers,

Sebastien Loisel

------=_Part_11293_31258992.1140042494458--