I''ve just tried to build wxRuby on a debian/unstable (i386) platform. I went to rubyforge.org and downloaded wxruby-0.5-src.tar.gz. <http://rubyforge.org/frs/download.php/1254/wxruby-0.5-src.tar.gz> I have ruby 1.8.2 installed on my system. I needed to install the debian package ruby1.8-dev in order to get mkmf.rb. That solved my first problem. So then i ran "ruby extconf.rb" and got my myself a Makefile. At this point something seems drastically wrong. Either this has never been compiled before on any configuration remoting like mine or i''ve missed something big. I don''t even have a wx directory in src for lines like #include wx/wx.h. I do have a wx.h file in the src directory. So change to #include <wx.h> but then not only don''t i have wx/hash.h, i don''t have hash.h, period (i have /usr/include/linux/hash.h but i would guess this is unrelated because there is no way in the world that i can see how this could be "accidentally" referenced as "wx/hash.h" What gives?
I suspect you haven''t downloaded/built the wxWidgets library. We don''t include wxWidgets in wxRuby because it is much bigger than our wrapper library. You can download it at http://www.wxwidgets.org I''m not the Linux expert, but I think you can use the default configuration without issue to build it. Nick craig duncan wrote:> I''ve just tried to build wxRuby on a debian/unstable (i386) > platform. I went to rubyforge.org and downloaded > wxruby-0.5-src.tar.gz. > <http://rubyforge.org/frs/download.php/1254/wxruby-0.5-src.tar.gz> > I have ruby 1.8.2 installed on my system. I needed to install the > debian package ruby1.8-dev in order to get mkmf.rb. That solved my > first problem. So then i ran "ruby extconf.rb" and got my myself a > Makefile. At this point something seems drastically wrong. Either > this has never been compiled before on any configuration remoting like > mine or i''ve missed something big. I don''t even have a wx directory > in src for lines like #include wx/wx.h. I do have a wx.h file in the > src directory. So change to #include <wx.h> but then not only don''t i > have wx/hash.h, i don''t have hash.h, period (i have > /usr/include/linux/hash.h but i would guess this is unrelated because > there is no way in the world that i can see how this could be > "accidentally" referenced as "wx/hash.h" > > What gives? > > > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > >
Never mind. On debian i needed to install the debian package libwxgtk2.5-dev which depends on the wx2.5-headers package which includes the files i was missing. It still doesn''t compile . . . but in a more "reasonable" way. craig duncan wrote:> I''ve just tried to build wxRuby on a debian/unstable (i386) > platform. I went to rubyforge.org and downloaded > wxruby-0.5-src.tar.gz. > <http://rubyforge.org/frs/download.php/1254/wxruby-0.5-src.tar.gz> > I have ruby 1.8.2 installed on my system. I needed to install the > debian package ruby1.8-dev in order to get mkmf.rb. That solved my > first problem. So then i ran "ruby extconf.rb" and got my myself a > Makefile. At this point something seems drastically wrong. Either > this has never been compiled before on any configuration remoting like > mine or i''ve missed something big. I don''t even have a wx directory > in src for lines like #include wx/wx.h. I do have a wx.h file in the > src directory. So change to #include <wx.h> but then not only don''t i > have wx/hash.h, i don''t have hash.h, period (i have > /usr/include/linux/hash.h but i would guess this is unrelated because > there is no way in the world that i can see how this could be > "accidentally" referenced as "wx/hash.h"
You need wxWidgets-2.4.2. The 2.5 version is still considered unstable. Nick craig duncan wrote:> Never mind. On debian i needed to install the debian package > libwxgtk2.5-dev which depends on the wx2.5-headers package which > includes the files i was missing. It still doesn''t compile . . . but > in a more "reasonable" way. > > craig duncan wrote: > >> I''ve just tried to build wxRuby on a debian/unstable (i386) >> platform. I went to rubyforge.org and downloaded >> wxruby-0.5-src.tar.gz. >> <http://rubyforge.org/frs/download.php/1254/wxruby-0.5-src.tar.gz> >> I have ruby 1.8.2 installed on my system. I needed to install the >> debian package ruby1.8-dev in order to get mkmf.rb. That solved my >> first problem. So then i ran "ruby extconf.rb" and got my myself a >> Makefile. At this point something seems drastically wrong. Either >> this has never been compiled before on any configuration remoting >> like mine or i''ve missed something big. I don''t even have a wx >> directory in src for lines like #include wx/wx.h. I do have a wx.h >> file in the src directory. So change to #include <wx.h> but then not >> only don''t i have wx/hash.h, i don''t have hash.h, period (i have >> /usr/include/linux/hash.h but i would guess this is unrelated because >> there is no way in the world that i can see how this could be >> "accidentally" referenced as "wx/hash.h" > > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > >
Craig, I run Debian unstable. I would like to hear more about why it isn''t compiling for you. Could you post the error/log Thanks, Zach craig duncan wrote:> Never mind. On debian i needed to install the debian package > libwxgtk2.5-dev which depends on the wx2.5-headers package which > includes the files i was missing. It still doesn''t compile . . . but > in a more "reasonable" way. > > craig duncan wrote: > >> I''ve just tried to build wxRuby on a debian/unstable (i386) >> platform. I went to rubyforge.org and downloaded >> wxruby-0.5-src.tar.gz. >> <http://rubyforge.org/frs/download.php/1254/wxruby-0.5-src.tar.gz> >> I have ruby 1.8.2 installed on my system. I needed to install the >> debian package ruby1.8-dev in order to get mkmf.rb. That solved my >> first problem. So then i ran "ruby extconf.rb" and got my myself a >> Makefile. At this point something seems drastically wrong. Either >> this has never been compiled before on any configuration remoting >> like mine or i''ve missed something big. I don''t even have a wx >> directory in src for lines like #include wx/wx.h. I do have a wx.h >> file in the src directory. So change to #include <wx.h> but then not >> only don''t i have wx/hash.h, i don''t have hash.h, period (i have >> /usr/include/linux/hash.h but i would guess this is unrelated because >> there is no way in the world that i can see how this could be >> "accidentally" referenced as "wx/hash.h" > > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > >
Zach Dennis wrote:> Craig, > > I run Debian unstable. I would like to hear more about why it isn''t > compiling for you. Could you post the error/log > Thanks, > > ZachJust for posterity. . . the problems i''ve had were: 1) As i was informed . . .> You need wxWidgets-2.4.2. The 2.5 version is still considered unstable. > > Nickso i uninstalled (and purged) debian packages libwxgtk2.5-dev/wx2.5-headers and installed libwxgtk2.4-dev/wxwin2.4-headers. This helped get me to where i was compiling what i was _supposed_ to be compiling. But there were still problems. Such as: app_cb.h:16: error: parse error before `{'' token But scrutinizing this, something was just plain screwy. So i took a look at what i had installed in the way of gcc/g++ and it turns out i had (over time) managed to install both: gcc-3.2-base / gcc-3.2 / g++-3.2 and gcc-3.3-base / gcc-3.3 / g++-3.3 (apparently the dependencies were specified in a way that deemed there to be nothing wrong with this). In fact, i hadn''t been having any noticeable compilation problems using (almostly) g++-3.3. But i got rid of the 3.2 stuff and that compilation problem went away. (To be honest i also had 2.95 installed and got rid of that at the same time. That wasn''t smart. In looking at what i had installed i decided i didn''t want 2.95 anymore [not having used it in a long time], but (stupidly) got rid of it in the same step as 3.2, and now i can only presume (without looking into it more, which i don''t care to do) that the problem was with the 3.2 stuff. I probably should upgrade to 3.4 . . . but not just yet. :-) Now tons of stuff compiles just fine. So i seem to be mostly set. I did just run into a problem compiling xmlresource.cpp (In file included from xmlresource.cpp:7: xmlresource.h:9:27: wx/xrc/xmlres.h: No such file or directory) but i seem to recall (very vaguely) something about some resources or extensions or xml stuff being separate, so hopefully i just need to install some add-on extension/xml package (haven''t even looked for it yet, which is why i sound like i have no real idea of what i''m talking about). craig
craig duncan wrote:> > Now tons of stuff compiles just fine. So i seem to be mostly set. I > did just run into a problem compiling xmlresource.cpp > (In file included from xmlresource.cpp:7: xmlresource.h:9:27: > wx/xrc/xmlres.h: No such file or directory) > but i seem to recall (very vaguely) something about some resources or > extensions or xml stuff being separate, so hopefully i just need to > install some add-on extension/xml package (haven''t even looked for it > yet, which is why i sound like i have no real idea of what i''m talking > about). > > craigI had this problem a while ago as well. I beleive to fix it open your extconf.rb file, and you''ll see: $use_xrc = true in there. Just set that to false and i think you''ll be good. Zach
> Now tons of stuff compiles just fine. So i seem to be mostly set. I > did just run into a problem compiling xmlresource.cppXRC, while very handy, isn''t part of the default wxWidgets build. To remove it from wxruby, change the variable $use_xrc to false in the extconf file. Then re-run extconf to make the new makefile. Nick craig duncan wrote:> Zach Dennis wrote: > >> Craig, >> >> I run Debian unstable. I would like to hear more about why it isn''t >> compiling for you. Could you post the error/log >> Thanks, >> >> Zach > > > Just for posterity. . . the problems i''ve had were: > > 1) As i was informed . . . > >> You need wxWidgets-2.4.2. The 2.5 version is still considered unstable. >> >> Nick > > > so i uninstalled (and purged) debian packages > libwxgtk2.5-dev/wx2.5-headers and installed > libwxgtk2.4-dev/wxwin2.4-headers. > This helped get me to where i was compiling what i was _supposed_ to > be compiling. But there were still problems. Such as: > app_cb.h:16: error: parse error before `{'' token > But scrutinizing this, something was just plain screwy. So i took a > look at what i had installed in the way of gcc/g++ and it turns out i > had (over time) managed to install both: > gcc-3.2-base / gcc-3.2 / g++-3.2 and gcc-3.3-base / gcc-3.3 / > g++-3.3 (apparently the dependencies were specified in a way that > deemed there to be nothing wrong with this). In fact, i hadn''t been > having any noticeable compilation problems using (almostly) g++-3.3. > But i got rid of the 3.2 stuff and that compilation problem went away. > (To be honest i also had 2.95 installed and got rid of that at the > same time. That wasn''t smart. In looking at what i had installed i > decided i didn''t want 2.95 anymore [not having used it in a long > time], but (stupidly) got rid of it in the same step as 3.2, and now i > can only presume (without looking into it more, which i don''t care to > do) that the problem was with the 3.2 stuff. I probably should > upgrade to 3.4 . . . but not just yet. :-) > > Now tons of stuff compiles just fine. So i seem to be mostly set. I > did just run into a problem compiling xmlresource.cpp > (In file included from xmlresource.cpp:7: xmlresource.h:9:27: > wx/xrc/xmlres.h: No such file or directory) > but i seem to recall (very vaguely) something about some resources or > extensions or xml stuff being separate, so hopefully i just need to > install some add-on extension/xml package (haven''t even looked for it > yet, which is why i sound like i have no real idea of what i''m talking > about). > > craig > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > >