wxruby users - Oct 2006 - Compiling on Ubuntu

I see several shortcomings in our current method of compiling on linux.  
Some things I ran in to which might need to be documented on the wiki:

1)  Compiling wx properly.  A little discussion of the proper flags 
would be helpful.
2)  The use of system libraries for jpeg, tiff and png.  The rake file 
assumes you''ll need these, even if you''re using the builtins
from wx.
We should modify the rakefile to test wx-config to see if you''re using 
them and to -not- include them if so.  My machine didn''t have those 
libraries and it caused the rake to fail.

3)  Once I got a library compiled, I couldn''t use it.  Not sure why but
it says it can''t find wxruby2.  I am wondering if it needs a different 
extension than .so or if I need to mark it executable or some other 
thing.  I don''t know.  Does anyone have some pointers on what
I''m
supposed to do with it to make ruby recognize it?

Roy

Roy Sutton wrote:
> I see several shortcomings in our current method of compiling on linux.  
> Some things I ran in to which might need to be documented on the wiki:
> 
> 1)  Compiling wx properly.  A little discussion of the proper flags 
> would be helpful.
Here is the script I ran to compile wx for the gem I built earlier:

kevins at aria:/usr/local/src/wxWidgets-2.6.3/buildgtk-static-release$ cat 
doconfigure.sh
../configure --disable-shared --with-gtk --enable-monolithic 
--with-libpng --with-libjpeg --with-libtiff --with-libxpm --with-zlib 
--enable-debug --enable-catch_segvs --enable-xrc --enable-mdi 
--enable-gif --enable-pcx --enable-iff --enable-pnm --enable-xpm 
--enable-gui --enable-unicode --disable-debug

kevins at aria:/usr/local/src/wxWidgets-2.6.3/buildgtk-static-release$


The configure options for wx are not well documented, so I really don''t
know how many of those are optimal, how many are poor choices, and how 
many are simply extraneous.
> 2)  The use of system libraries for jpeg, tiff and png.  The rake file 
> assumes you''ll need these, even if you''re using the
builtins from wx.
> We should modify the rakefile to test wx-config to see if you''re
using
> them and to -not- include them if so.  My machine didn''t have
those
> libraries and it caused the rake to fail.
I was thinking using the common libraries would be better, but 
apparently not. Should be easy to modify the above script to use the 
internal versions.
> 
> 3)  Once I got a library compiled, I couldn''t use it.  Not sure
why but
> it says it can''t find wxruby2.  I am wondering if it needs a
different
> extension than .so or if I need to mark it executable or some other 
> thing.  I don''t know.  Does anyone have some pointers on what
I''m
> supposed to do with it to make ruby recognize it?
After compling wxruby, I either install the raw .so (rake install) or 
build and install the gem. Personally, I don''t like to use rake install
any more, because a) there is no uninstall, and b) if you later install 
the gem it won''t work because the earlier copy that was rake installed 
takes precedence.

I''m not sure if any of that has anything to do with the problems you
are
having, but figured I should mention them.

I hope to be able to do an Ubuntu Linux build within the next few days. 
Sunday at the latest.

Kevin

Kevin Smith wrote:
> Here is the script I ran to compile wx for the gem I built earlier:
>
> kevins at aria:/usr/local/src/wxWidgets-2.6.3/buildgtk-static-release$ cat 
> doconfigure.sh
> ../configure --disable-shared --with-gtk --enable-monolithic 
> --with-libpng --with-libjpeg --with-libtiff --with-libxpm --with-zlib 
> --enable-debug --enable-catch_segvs --enable-xrc --enable-mdi 
> --enable-gif --enable-pcx --enable-iff --enable-pnm --enable-xpm 
> --enable-gui --enable-unicode --disable-debug
>   
Thanks, Kevin.  I''ll try those options.  I would say that having both 
--enable-debug and --disable-debug might be extraneous.
> After compling wxruby, I either install the raw .so (rake install) or 
> build and install the gem. Personally, I don''t like to use rake
install
> any more, because a) there is no uninstall, and b) if you later install 
> the gem it won''t work because the earlier copy that was rake
installed
> takes precedence.
>   
Hmm, I never did a ''rake install'' (didn''t know it
existed!).  On Windows
I just set RUBYLIB to point to my wxruby2/lib directory.  I''ll try 
remaking the gem with the commands you gave and see if that fixes anything.

Roy