Hi!
I''ve been trying to get fxruby 1.4.2 up and running, but unfortunately
with no succes so far.
My linux knowledge is still pretty basic (background in windows/c++/mfc
programming for a living... and further back on Amiga... but using linux
at home and for some none work-related projects) so I just hope I
didn''t
screw up something obvious.
I''m running fedora core 3, ruby 1.8.3 (2005-09-21) [i386-linux].
I installed from gems (after installing/compiling FOX itself) and get
the following:
irb(main):001:0> require ''rubygems''
=> true
irb(main):002:0> require ''fox14''
=> false
fox14.so is
at:/usr/lib/ruby/gems/1.8/gems/fxruby-1.4.2/ext/fox14/fox14.so
/usr/local/lib contains (amongst others):
libCHART-1.4.so libFOX-1.4.a libFOX-1.4.so.0
libCHART-1.4.a libCHART-1.4.so.0 libFOX-1.4.la
libFOX-1.4.so.0.0.17
libCHART-1.4.la libCHART-1.4.so.0.0.17 libFOX-1.4.so
gem check --alien gives me the following:
Performing the ''alien'' operation
ERROR: While executing gem ... (Errno::ENOENT)
No such file or directory
- /usr/lib/ruby/gems/1.8/gems/fxruby-1.4.2/ext/fox14/scintilla_wrap.cpp
--> Does this mean I have to install scintilla (or fxscintilla ???)
I figured, since there''s a fox14.so and a libFOX-1.4.so,
compiling/installing went ok, ar am I wrong here ?
Any help is mucho appreciated, thanks in advance!
Piet.
Hi!
After installing scintilla/fxscintilla I still have the same issue.
But... ''gem check --alien'' now returns the following:
fxruby-1.4.2 has 1 problems
/usr/lib/ruby/gems/1.8/cache/fxruby-1.4.2.gem:
Unmanaged files in gem: ["ext/fox14/gem_make.out",
"ext/fox14/fox14.so", "ext/fox14/unregisterOwnedObjects.o",
"ext/fox14/ui_wrap.o", "ext/fox14/treelist_wrap.o",
"ext/fox14/text_wrap.o", "ext/fox14/table_wrap.o",
"ext/fox14/scintilla_wrap.o", "ext/fox14/menu_wrap.o",
"ext/fox14/mdi_wrap.o", "ext/fox14/markfuncs.o",
"ext/fox14/list_wrap.o", "ext/fox14/layout_wrap.o",
"ext/fox14/label_wrap.o", "ext/fox14/impl.o",
"ext/fox14/image_wrap.o",
"ext/fox14/icons_wrap.o", "ext/fox14/iconlist_wrap.o",
"ext/fox14/FXRuby.o", "ext/fox14/FXRbGLViewer.o",
"ext/fox14/FXRbDataTarget.o", "ext/fox14/FXRbApp.o",
"ext/fox14/fx3d_wrap.o", "ext/fox14/frames_wrap.o",
"ext/fox14/dialogs_wrap.o", "ext/fox14/dc_wrap.o",
"ext/fox14/core_wrap.o", "ext/fox14/librb.o",
"ext/fox14/Makefile",
"ext/fox14/mkmf.log"]
At the moment I''ve got no clue however what this means, and if
it''s the
cause of the problem.
Any help is really appreciated.
Piet.
Hi! Me again (is anyone reading this except me ? Is this group abandoned ???). I found the problem: irb(main):001:0> require ''rubygems'' => true irb(main):002:0> require_gem ''fxruby'' => true Obviously I needed "require_gem ''fxruby''" instead of "require ''fox14''". Duh. How was I supposed to know this ? Is the fxruby site info wrong/outdated (http://www.fxruby.org/doc/gems.html) or is there something wrong with my ruby or gems installation ??? Or should this be some kind of common sense that isn''t really that common to me ? Well, for the moment the problem is solved but I''d still like to be enlightened about the how/why. Thanks in advance! Piet.
On Oct 16, 2005, at 2:02 PM, Piet Hadermann wrote:> Hi! > > Me again (is anyone reading this except me ? Is this group > abandoned ???).Piet, I apologize for the delay in responding to your questions. I''ve been out of town this weekend at the Ruby Conference in San Diego, and I know that several of our "regulars" from this mailing list were out there as well. Looking back over your last three e-mails, I wanted to address some of the main points. First, you found that after building and installing the FXRuby gem, the call to require ''fox14'' in irb returned false. This is a known problem with RubyGems; see for example this bug report: http://rubyforge.org/tracker/index.php? func=detail&aid=1942&group_id=126&atid=575 A better way to check for a successful FXRuby installation is to just try one of the example programs (like hello.rb). I should probably change the documentation to reflect this. You also reported several troubling messages from the "gem check --alien" command. I wasn''t familiar with this option (--alien) but it looks like it''s complaining about some of the files created as a side effect of compiling this extension module (e.g. all of the "*.o" files). I will research this to see if there''s some way to tell RubyGems that those files are, in fact, supposed to be there! Thanks for pointing this out to me. On your last point, as to whether you should use this: require ''fox14'' or this: require ''rubygems'' require_gem ''fxruby'' The preferred method (for me) is to set the RUBYOPT environment variable to "ubygems", as described in the RubyGems documentation. If you do this, the ''rubygems'' library will be automatically loaded by the Ruby interpreter on startup and then it will be able to find the library as ''fox14''. This has been discussed on the mailing list before, but it may not be in the FXRuby User''s Guide because it''s something that most RubyGems users already know about. I will see about adding this to the FXRuby documentation as well. Thanks, Lyle