From: Richard Dale <Richard_Dale@...>
Date: 2004-07-15T18:57:19+09:00
Subject: Re: qtruby and ms windows

Hans Fugal wrote:
> Would y'all please report back if someone gets qtruby working in windows?

Richard Dale wrote:
> Yes ok - it's definately possible because some PerlQt guys recently got
> the Smoke library working on Windows. I seem to remember them saying
> something about 'removing certain headers'. Hmm. But maybe ruby-talk might
> want to be spared from a 'blow by blow' account of how exactly to get
> there..
> 
> I just need to have a look at the recent kde-perl@kde.org posts to see
> what they said and did. The ruby QtRuby extension part should be easy
> enough to compile I would have thought. It builds on Mac OS X so there
> can't be any X11 dependencies in there.

Here's the post from the kde-perl mailing list about building the Smoke
library on Windows. Other people tried the instructions and confirmed it
worked ok. I'm not sure if this works with cygwin though:

"Although there are bindings for using PerlQt on windows with cygwin-x11 and
qt-x11, I didn't want my target computer to have those installed. So I
coerced PerlQt into compiling and linking under MSVC6"

On Tuesday 22 June 2004 14:50, ryan@vbijl.net wrote:
> Hello,
>
> Thought you all might be interested.  I managed to coerce
> MSVC++ 6 into compiling PerlQt. Then I managed to convince
> it to link.   And, amazingly, it worked[1]!
>
> I used ActiveState 5.8.4, Qt/Windows 3.2.0, MSVC++6, and PerlQt 3.008.
>
> I've put together a document describing how I got it to work:
>    http://www.vbijl.net/~ryan/software/perlqt/
>
> [1] There are a few issues. For example, timers seem to be broken.
> Also a few headers that didn't want to be used.
>
> Anyways.  I was hoping someone on this list might be able to
> try this out before I post to the qt-interest list.
>
> Ryan

-- Richard