Thu 16 May 2013 08:31:35 PM UTC, comment #10:
Not that it makes any difference to the issues that were seen, but I was running it in a fedora core 18 live install to a VirtualBox VM, with the only additional installed packages being the ones called out in the mxe build requirements.
I think there are a few other dependancies still missing. I'll let you know if I find them.
|
Thu 16 May 2013 06:35:25 PM UTC, comment #9:
I checked in the following changes:
http://hg.savannah.gnu.org/hgweb/octave/rev/c7d4146c570d
http://hg.octave.org/mxe-octave/rev/aca8511e7751
There will be another snapshot on alpha.gnu.org before too long, I'm sure.
|
Thu 16 May 2013 05:42:24 PM UTC, comment #8:
Philip:
Yes, of course. It's fairly easy these days to set up a VM with a system that doesn't have any development tools installed other than the bare minimum required for bootstrapping MXE. So people who want to test this and make sure that it works properly are welcome to do that. I don't have infinite time available for all these things...
|
Thu 16 May 2013 05:40:29 PM UTC, comment #7:
I'd rather avoid the use of pkg-config scripts in Octave's configure file if possible. I'm creating patch that uses AC_CHECK_TOOLS and fixes the incorrect links for the $(TARGET)-tool programs in MXE's qt.mk file.
|
Thu 16 May 2013 05:37:13 PM UTC, comment #6:
Reply to comment #3:
Bingo:
To solve these issues I guess it may help to make MXE builds on otherwise bare Linux systems that in particular, aren't used for Linux builds of Octave.
Probably rare systems I'd say :-)
|
Thu 16 May 2013 03:08:47 PM UTC, comment #5:
This attached patch seems to work for me, both with mxe and linux build for detecting Qt GUI build.
It changes from using AC_CHECK_PROGS for uic etc, to AC_PATH_PROG, and includes the pkg-config QtCore exe prefix in the search path.
(file #28097)
|
Wed 15 May 2013 11:24:47 PM UTC, comment #4:
I am thinking it pulls in the native moc, uic etc - which I do not have installed on the machine that I am compiling with.
Its the same issue with moc, uic and lrelease - all get installed, but are not found by configure.
|
Wed 15 May 2013 09:37:36 PM UTC, comment #3:
Phililp, do you have moc, qmake, etc. installed somewhere in your PATH on the system where you are running the MXE build? If so, Octave is probably using those instead of the tools built as part of the MXE build. So that could be the reason it works. I think that's why it works for me.
|
Wed 15 May 2013 09:31:43 PM UTC, comment #2:
I see one problem is that the qt.mk script makes symbolic links to bin/qt files that don't exist. I guess Octave's configure script also needs to look for $host-moc, etc.? Or, as a temporary fix, we need to set MOC='$(PREFIX)/bin/$(TARGET)-moc in the octave.mk file when calling configure?
|
Wed 15 May 2013 09:26:33 PM UTC, comment #1:
I do not understand your problem exactly. You can't build the GUI with MXE?
This evening I've built 3.7.5 with a fresh clone of MXE and installed it on my WinXP box. Works complete with GUI.
The only thing I noted is that the of-windows package is missing (it wasn't included in the dist zip).
|
Wed 15 May 2013 09:07:30 PM UTC, original submission:
On running ./mk-dist, octave fails to detect uic, moc and so will not build with the GUI enabled.
Looking at the qt install during the make, the tools are built and installed as
usr/i686-pc-mingw32/bin/moc and as usr/bin/i686-pc-mingw32-moc.
The configure for octave looks only for moc,moc-qt4,moc-qt5 with a path set to PATH=$TOPDIR/usr/bin:$PATH.
|