headers
Shawn Rutledge | 2 Nov 2008 07:14
Picon

Re: Qt egg

On Sat, Nov 1, 2008 at 5:32 PM, Vincent Manis <vmanis <at> telus.net> wrote:
> On 2008-Nov-1, at 01:39, Shawn Rutledge wrote:
>> Did you succeed yet?  I just got around to trying this.  qt.setup only
>> uses QTDIR to find qmake, so you can set QTDIR to "/usr".  But the
>> next problem is that qmake generates an XCode project rather than a
>> Makefile.
>
> Actually, I made no progress with it, as I put that project on the back
> burner, and
> if I do go back to it, I'm likely to do it on Linux rather than OSX.
> However, it would
> still be nice to have a recipe to give to everyone :-)

I just got it to build:

1) export QTDIR=/usr
2) export QMAKESPEC=macx-g++
       (to get a Makefile rather than XCode project)
3) tar zxvf qt.egg and modify the last line of qt.pro like this:
       QT+=opengl xml
4) chicken-setup

Felix - I think maybe you don't need to depend on QTDIR at all; it's
probably OK to require that qmake be in the user's path.  For anyone
who's doing Qt development, it would tend to be.  There is not always
a top level Qt directory - in fact I consider that to be poor system
integration, which the Qt install process gives you by default when
you build it from source (installing _everything_ to
/usr/local/Trolltech does not conform to any system standard...
besides what are they going to do, change it to /usr/local/Nokia now?
(Continue reading)

Permalink | Reply |
headers
felix winkelmann | 3 Nov 2008 00:47
Picon

Re: Qt egg

On Sun, Nov 2, 2008 at 7:14 AM, Shawn Rutledge
<shawn.t.rutledge <at> gmail.com> wrote:
>
> 1) export QTDIR=/usr
> 2) export QMAKESPEC=macx-g++
>       (to get a Makefile rather than XCode project)
> 3) tar zxvf qt.egg and modify the last line of qt.pro like this:
>       QT+=opengl xml
> 4) chicken-setup
>
> Felix - I think maybe you don't need to depend on QTDIR at all; it's
> probably OK to require that qmake be in the user's path.  For anyone
> who's doing Qt development, it would tend to be.  There is not always
> a top level Qt directory - in fact I consider that to be poor system
> integration, which the Qt install process gives you by default when
> you build it from source (installing _everything_ to
> /usr/local/Trolltech does not conform to any system standard...
> besides what are they going to do, change it to /usr/local/Nokia now?
> But at least you can change it when you run configure.)  When
> installed via the gentoo ebuild, or when you install the Qt binary
> package on MacOS, qmake is in /usr/bin, as it should be IMO.
>

Thanks, Shawn. I'll check this as soon as possible (which may take a while),
perhaps I can improve the setup script to work better on mac. There is indeed
some problem on OS X (as you note in your next mail), but I can't recall
right now. I'll check that, too.

cheers,
felix
(Continue reading)

Permalink | Reply |
headers
Shawn Rutledge | 2 Nov 2008 08:08
Picon

Re: Qt egg

As for running it, there are some problems too:

[mini][11:48:58 PM] ChickenQt.app/Contents/MacOS/ChickenQt
Error: unbound variable: qt

The hello world app has (use qt utils), and asking for qt isn't
necessary... so by taking it out I can get it to run.  But if I try to
run the egg-browser demo, after changing the (use... ) line to
(require 'posix 'regex 'utils)
I get this:

[mini][11:54:43 PM] ChickenQt.app/Contents/MacOS/ChickenQt
Error: unbound variable: <>

	Call history:

	<eval>		[refresh] (map pathname-file (glob (make-pathname
(repository-path) "*.setup-info")))
	<eval>		[refresh] (glob (make-pathname (repository-path) "*.setup-info"))
	<eval>		[refresh] (make-pathname (repository-path) "*.setup-info")
	<eval>		[refresh] (repository-path)
	<eval>		[refresh] (qt:clear *list*)
	<eval>		[refresh] (qt:clear *props*)
	<eval>		[refresh] (for-each (cut qt:add *list* <>) eggs)
	<eval>		[refresh] (cut qt:add *list* <>)	<--

I assume you had some difficulty getting the qt egg to work like
usual, i.e. be able to load it as a shared object?  The app bundle
approach could have its uses, but being able to mess around on the csi
prompt would also be useful.
(Continue reading)

Permalink | Reply |
headers
Shawn Rutledge | 2 Nov 2008 08:16
Picon

Re: Qt egg

On Sun, Nov 2, 2008 at 12:08 AM, Shawn Rutledge
<shawn.t.rutledge <at> gmail.com> wrote:
> As for running it, there are some problems too

I forgot to mention the default init.scm gives me this error:

[mini][11:26:10 PM] ChickenQt.app/Contents/MacOS/ChickenQt
QWidget: Must construct a QApplication before a QPaintDevice
Abort trap
Permalink | Reply |

Gmane