Generally, exerb seems to work better if you use MinGW-compiled
libraries (I believe you’ll need a MinGW-compiled ruby, and possibly
exerb core, to bind into your application), though that’s not a panacea.
It seems to cure the socket.so library problem on Windows, but I
encountered some other library problem after that, which I don’t recall
at the moment.
Al
···
-----Original Message-----
From: Steve Tuckner [mailto:STUCKNER@MULTITECH.COM]
Sent: Thursday, August 28, 2003 3:12 PM
To: ruby-talk ML
Subject: EXErb
I have an interest in using EXErb to distribute a windows application.
But I have run into a problem right away. The exe created ends up with a
segment fault in ruby. I isolated the problem down to a very simple
example.
hello.rbc -------------------
kcode none
corename cui
script exetest.rb
library socket.so
hello.rb ---------------------
require “socket”
puts “hello”
I run the command (I have copied the ruby 1.8 socket.so into the local
directory)
exerb hello.rbc
hello
generates the output:
exetest.rb:1: [BUG] Segmentation fault
ruby 1.6.8 (2002-12-24) [i586-mswin32]
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application’s support team for more information.
If I comment out the require “socket”, it works fine. The example1 in
the distribution requires Win32api.so and that works fine. Thanks for
any suggestions.
Ruby version 1.8, exerb version 2.6.6
Steve Tuckner