ANN: wxRuby 0.1.0 Alpha has been released!

ruby-talk
1

http://rubyforge.org/project/showfiles.php?group_id=35&release_id=46

The code itself has been quite stable for several weeks. This release
includes Gour’s excellent MinGW README notes, along with various updates
to the README, and clarification of the LICENSE.

Thanks to everyone for your help in putting this together. It was
definitely a team project. I look forward to getting lots of feedback so
we can have a much improved 0.2.0 release. The most pressing needs, I
think, are better README files, cleaner samples, and binary packages.

Kevin Smith

···

wxruby-users mailing list
wxruby-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/wxruby-users

2

Curt Hibbs wrote:

http://rubyforge.org/project/showfiles.php?group_id=35&release_id=46

The code itself has been quite stable for several weeks. This release
includes Gour’s excellent MinGW README notes, along with various updates
to the README, and clarification of the LICENSE.

Thanks to everyone for your help in putting this together. It was
definitely a team project. I look forward to getting lots of feedback so
we can have a much improved 0.2.0 release. The most pressing needs, I
think, are better README files, cleaner samples, and binary packages.

Kevin Smith

wxruby-users mailing list
wxruby-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/wxruby-users

great!

but I have a problem compiling it.

c++ -shared wx-config --libs -Wl,–version-script,./version-script
-L"/usr/local/lib" -o wxruby.so wx.o app.o bitmap.o button.o calendar.o
checkbox.o choice.o colour.o colourdata.o colourdialog.o combobox.o const.o
date.o dialog.o dirdialog.o event.o evthandler.o filedialog.o font.o
fontdata.o fontdialog.o frame.o gauge.o layout.o listbox.o menu.o menubar.o
messagedialog.o point.o radio.o rect.o size.o sizer.o slider.o spin.o
statictext.o textctrl.o timer.o validator.o window.o icon.o artprovider.o
log.o listctrl.o list.o panel.o scrolledwindow.o dc.o brush.o pen.o caret.o
statusbar.o ownerdrawn.o config.o region.o cursor.o notebook.o tooltip.o
mask.o socket.o url.o stream.o toolbar.o image.o palette.o treectrl.o
classinfo.o splitterwindow.o methods.o staticbitmap.o control.o
togglebutton.o grid.o menuitem.o textattr.o -ldl -lcrypt -lm -lc

I /usr/i486-suse-linux/bin/ld: wxruby.so: undefined versioned symbol name
wxBitmapButtonBase::OnSetBitmap(void)@@WXGTK2_2.4
/usr/i486-suse-linux/bin/ld: failed to set dynamic section sizes: Bad value
collect2: ld returned 1 exit status

I have wxwindows 2.4.1 with GTk2 and Ruby 1.8.0

any ideas what is wrong here ?

Markus

3

I’m not a Linux user. I suggest you subscribe to the wxRuby ML and get
advice there from other Linux users. For the time being, I’ll cross-post
this message to the wxRuby ML.

Curt

Markus Jais wrote:

···

Curt Hibbs wrote:

http://rubyforge.org/project/showfiles.php?group_id=35&release_id=46

The code itself has been quite stable for several weeks. This release
includes Gour’s excellent MinGW README notes, along with various updates
to the README, and clarification of the LICENSE.

Thanks to everyone for your help in putting this together. It was
definitely a team project. I look forward to getting lots of feedback so
we can have a much improved 0.2.0 release. The most pressing needs, I
think, are better README files, cleaner samples, and binary packages.

Kevin Smith

wxruby-users mailing list
wxruby-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/wxruby-users

great!

but I have a problem compiling it.

c++ -shared wx-config --libs -Wl,–version-script,./version-script
-L"/usr/local/lib" -o wxruby.so wx.o app.o bitmap.o button.o calendar.o
checkbox.o choice.o colour.o colourdata.o colourdialog.o
combobox.o const.o
date.o dialog.o dirdialog.o event.o evthandler.o filedialog.o font.o
fontdata.o fontdialog.o frame.o gauge.o layout.o listbox.o menu.o
menubar.o
messagedialog.o point.o radio.o rect.o size.o sizer.o slider.o spin.o
statictext.o textctrl.o timer.o validator.o window.o icon.o artprovider.o
log.o listctrl.o list.o panel.o scrolledwindow.o dc.o brush.o
pen.o caret.o
statusbar.o ownerdrawn.o config.o region.o cursor.o notebook.o tooltip.o
mask.o socket.o url.o stream.o toolbar.o image.o palette.o treectrl.o
classinfo.o splitterwindow.o methods.o staticbitmap.o control.o
togglebutton.o grid.o menuitem.o textattr.o -ldl -lcrypt -lm -lc

I /usr/i486-suse-linux/bin/ld: wxruby.so: undefined versioned symbol name
wxBitmapButtonBase::OnSetBitmap(void)@@WXGTK2_2.4
/usr/i486-suse-linux/bin/ld: failed to set dynamic section sizes:
Bad value
collect2: ld returned 1 exit status

I have wxwindows 2.4.1 with GTk2 and Ruby 1.8.0

any ideas what is wrong here ?

Markus

4

Have you enabled the support for GTK2 in wxWindows?

Just an idea,
Sascha

···

Markus Jais mjais@web.de wrote:

I have wxwindows 2.4.1 with GTk2 and Ruby 1.8.0

5

Markus Jais wrote:
> > _______________________________________________
> > wxruby-users mailing list
> > wxruby-users@rubyforge.org
> > http://rubyforge.org/mailman/listinfo/wxruby-users
>
> great!
>
> but I have a problem compiling it.
>
> c++ -shared `wx-config --libs` -Wl,--version-script,./version-script
> -L"/usr/local/lib" -o wxruby.so wx.o app.o bitmap.o button.o calendar.o

(snip)

>
> I /usr/i486-suse-linux/bin/ld: wxruby.so: undefined versioned symbol name
> wxBitmapButtonBase::OnSetBitmap(void)@@WXGTK2_2.4
> /usr/i486-suse-linux/bin/ld: failed to set dynamic section sizes:
> Bad value
> collect2: ld returned 1 exit status
>
>
> I have wxwindows 2.4.1 with GTk2 and Ruby 1.8.0

I'm using wxwindows 2.4.0 with GTK2 and Ruby 1.8.0.

My best guess is that wxRuby was compiled with a different version of
the C++ toolchain than your wxWindows library. Unfortunately, C++
binaries have traditionally been incompatible between versions of g++.
So you may need to compile wxWindows from source on your box, or you may
need to compile wxRuby with the same compiler that was used for your
copy of wxWindows (by manually modifying Makefile, I suppose).

In my case, I use g++ 3.3 because that is the Debian Sarge default.

We need to add this to the README and/or a FAQ.

Thanks,

Kevin