ruby-fltk-devel

[ruby-fltk-devel] cygwin version (without X)

[Takaaki T. <tt...@ja...>]

Now I've successfully compiled the Ruby/FLTK on Windows2000
with Cygwin-1.1, Ruby-1.6 and FLTK-1.0.11 and released it.
But a few changes were needed.

I checked that most of samples could work well.
But when I ran the othello.rb, it caused the segmentation
fault at Fl::draw. So I replaced it with Box and Box#label.

Cygwin 1.1: http://sources.redhat.com/cygwin/
-- 
Takaaki Tateishi <tt...@ja...>

Re: [ruby-fltk-devel] cygwin version (without X)

[Kevin S. <kev...@ya...>]

--- Takaaki Tateishi <tt...@ja...> wrote:
> Now I've successfully compiled the Ruby/FLTK on
> Windows2000 with Cygwin-1.1, Ruby-1.6 and FLTK-1.0.11 and

> released it. But a few changes were needed.

How easy or hard would it be to release a Windows binary
dll that is statically linked with Fltk? I could really use
it, to distribute my Fltk version of Space Monkeys to some
people running Windows. (It would have to be compatible
with the PragProg one-step Windows Ruby package).

Kevin

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com

Re: [ruby-fltk-devel] cygwin version (without X)

[Takaaki T. <tt...@kt...>]

At Mon, 24 Sep 2001 08:37:21 -0700 (PDT),
> How easy or hard would it be to release a Windows binary
> dll that is statically linked with Fltk?

We would merely run extconf.rb and do make on the cygwin now.

I fixed the code since a few *bugs* are found when compiling
on the cygwin. We could call the abstract virtual function,
but this was detected by gcc-2.95.3(cygwin).
Also, I saw some of mismatch functions about its prototype.
I had no time for thinking about those, so I removed those
functions.
-- 
Takaaki Tateishi <tt...@kt...>