QT for Win32?

ruby-talk
1

Thanks for the reply. That explains why Ruby/Qt wouldn't compile for me. My
fault for not reading the documentation a little more carefully as to the Qt
version supported.

As for QtRuby, I think the problem I'm having is my compiler environment. I
have Borland's C Compiler v5.5 on my development notebook as well as some
GNU tools (both under mswin32 and under cygwin). But the fact I don't have
Microsoft's Visual C Compiler on my system is likely the problem. I can
either pay for the Microsoft Visual Studio version or else download the .NET
SDK for the free version. But I really dread downloading dozens of megs of
Microsoft bloatware to my system just to be able to compile Qt in this one
occasion.

I really want to experiment with Qt some, since I have used the GTK and Tk
Ruby bindings and want to compare them all before choosing one for most of
my GUI work. I guess I can hop over to my FreeBSD or Red Hat boxes to try
things over there, but my client workstations are mostly Win32 and they
would be the end users :frowning:

ยทยทยท

-----Original Message-----
From: Richard Dale [mailto:Richard_Dale@tipitina.demon.co.uk]
Sent: Monday, April 04, 2005 2:00 PM
To: ruby-talk@ruby-lang.org
Subject: Re: QT for Win32?

Kujawa, Greg wrote:

I have read several threads regarding QT running on a Windows
platform. I have compiled and installed the qt-free-win package
(version 3) on my Win32 box and have tried several Ruby QT binding
installs to no avail. Both the QTRuby and the Ruby/QT variety. One of
them couldn't find the qt libraries when I tried to compile it,
although I set the QTDIR environmental variable and passed along the
--with-qt-dir= specification. The other binding package errored out
along the way pulling in one of the QT include files. Perhaps it was
qstring (IIRC).

Is there a particular Ruby QT binding package that works with QT
version 3 on the Windows platform and doesn't require compiling in
order to bring it in?

Ruby/Qt doesn't work with Qt 3 on any platform, it was based on Qt 1.x or
2.x, and never ported to Qt 3.

It shouldn't be too difficult to get QtRuby working on Windows, but I don't
personally have a Windows development environment to do the port. Also I
don't understand the license issues involved - when the GPL'd Qt 4 windows
is released it will be clearer. QtRuby works fine on Mac OS X, although the
build process is a bit fiddly - so it certainly isn't X11 specific and will
run on anything Qt runs on.

-- Richard

2

Kujawa, Greg wrote:

I really want to experiment with Qt some, since I have used the GTK and Tk
Ruby bindings and want to compare them all before choosing one for most of
my GUI work. I guess I can hop over to my FreeBSD or Red Hat boxes to try
things over there, but my client workstations are mostly Win32 and they
would be the end users :frowning:

Yes, that sounds the best plan. The nice thing about Qt is that you can
develop on Linux, and deploy on Win32 - with ruby you wouldn't even need to
recompile.

If you have a look at the instructions for building QtRuby on Mac OS X,
using qmake and extconf.rb instead of automake/autoconf it should be very
similar. The Smoke library generation is driven by a list of headers in
smoke/qt/header_list, which are fed into a perl tool called 'kalyptus'. The
code to do that works fine on Mac OS X, but I don't think it would on
Windows.

So one way to get a port working, would be to generate the Smoke sources on
FreeBSD or Red Hat, and build them on Windows using qmake. If you have
errors from a specific header in the 'header_list' file, then either fix
the compile error by hand, or remove the header and retry. I would expect
that using extconf.rb on Windows to work ok, and build a .DLL instead of a
shared lib or Mac OS X bundle.

-- Richard