Hi I''d like to offer a Linux AMD-64 gem again for 1.9.4. Sean - I think you posted a way to do this using an emulator on OS X but I can''t find your instructions. Perhaps you could point me in the right direction please? thanks alex
I found the old email, I wrote:> I am using VMware fusion on my MacBook Pro which has a Core 2 Duo. As > long as you have a Core 2 Duo or newer VMware fusion will allow you to > run 32 and 64 bit hosts. Previously I ran Parallels which was ok but > VMware is much more stable and I don''t think Parallels can do both 32 > and 64 bit.I build wxWidgets according to the Linux instructions at: http://wxruby.rubyforge.org/wiki/wiki.pl?HowToBuildWxWidgets and added CFLAGS=-fPIC CXXFLAGS=-fPIC LDFLAGS=-fPIC And that was all I did Sean On Feb 7, 2008 3:47 AM, Alex Fenton <alex at pressure.to> wrote:> Hi > > I''d like to offer a Linux AMD-64 gem again for 1.9.4. Sean - I think you > posted a way to do this using an emulator on OS X but I can''t find your > instructions. Perhaps you could point me in the right direction please? > > thanks > alex > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development >
Sean Long wrote:>> I am using VMware fusion on my MacBook Pro which has a Core 2 Duo.Thanks, that worked. Setting up all the packages is a bit of a grind, and I couldn''t get it to recognise MediaCtrl, but apart from that flaw, we''ve got a AMD-64 gem. alex
Hey Alex, I''m working on a SourceMage setup with Dale, and for some reason I''m getting an Unresolved Symbol error comming from the wxruby2.so file, even though I have wxGTK compiled with the flags needed to initialize the WxMediaCtrl class within it. I have gstreamer0.10 installed, so it''s not having a problem finding that. And as far as I can tell, wxGTK compiles just fine with MediaCtrl enabled. Don''t know of the symbol yet, I''ll have to find out when I get home tonight. And it does it no matter what, just from a simple ruby - rwxruby2.so, will cause the undefined symbol error to popup. I''ve been trying to re-compile wxGTK to recognize the MediaCtrl, as well as wxRuby, both 1.9.4, and SVN Head. Are you having the same problem on the AMD-64 Bit version of the gem? Also, you said a while back, that you was successfully able to split one control off, into it''s own shared library, in which to use. Can you send me that, so I can study it, and see how we can progress it to include the various other classes in wxRuby? Might as well start somewhere, right? L8ers, On 2/7/08, Alex Fenton <alex at pressure.to> wrote:> > Sean Long wrote: > >> I am using VMware fusion on my MacBook Pro which has a Core 2 Duo. > > Thanks, that worked. Setting up all the packages is a bit of a grind, > and I couldn''t get it to recognise MediaCtrl, but apart from that flaw, > we''ve got a AMD-64 gem. > > alex > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development >-- Mario Steele http://www.trilake.net http://www.ruby-im.net http://rubyforge.org/projects/wxruby/ http://rubyforge.org/projects/wxride/ http://rubyforge.org/projects/vwmc/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20080208/be7aed24/attachment.html
Mario Steele wrote:> I''m working on a SourceMage setup with Dale, and for some reason I''m > getting an Unresolved Symbol error comming from the wxruby2.so file, > even though I have wxGTK compiled with the flags needed to initialize > the WxMediaCtrl class within it. I have gstreamer0.10 installed, so > it''s not having a problem finding that. And as far as I can tell, > wxGTK compiles just fine with MediaCtrl enabled.It may be worth double-checking config.log in your wxWidgets build directory to see that configure found all the elements it requires to compile wxMediaCtrl. Search for ''gst'' in that file to find the checks it does, and any that fail.> Don''t know of the symbol yet, I''ll have to find out when I get home > tonight. And it does it no matter what, just from a simple ruby > -rwxruby2.so, will cause the undefined symbol error to popup. I''ve > been trying to re-compile wxGTK to recognize the MediaCtrl, as well as > wxRuby, both 1.9.4, and SVN Head. Are you having the same problem on > the AMD-64 Bit version of the gem?The problem I had was that configure said it couldn''t find ''gstreamer-0.10-plugins-base'', but I couldn''t find a package in Ubuntu repository with exactly that name. Everything similar was installed, but it still didn''t work. I''m thinking that if it is a painful dependency, we should consider shipping the default binary gem for Linux without MediaCtrl. The primary requirement for the binary gems is that they are easy to get started with.> Also, you said a while back, that you was successfully able to split > one control off, into it''s own shared library, in which to use. Can > you send me that, so I can study it, and see how we can progress it to > include the various other classes in wxRuby? Might as well start > somewhere, right?I''ll post this separately. cheers alex
On 2/8/08, Alex Fenton <alex at pressure.to> wrote:> > Mario Steele wrote: > > I''m working on a SourceMage setup with Dale, and for some reason I''m > > getting an Unresolved Symbol error comming from the wxruby2.so file, > > even though I have wxGTK compiled with the flags needed to initialize > > the WxMediaCtrl class within it. I have gstreamer0.10 installed, so > > it''s not having a problem finding that. And as far as I can tell, > > wxGTK compiles just fine with MediaCtrl enabled. > It may be worth double-checking config.log in your wxWidgets build > directory to see that configure found all the elements it requires to > compile wxMediaCtrl. Search for ''gst'' in that file to find the checks it > does, and any that fail.Checked wxGTK compile log, and it shows that it found GStreamer, and enabled wxMediaCtrl, here''s the relevant parts of the configure log that pertain to wxMediaCtrl: <check for -- flags> checking for --enable-sound... yes checking for --enable-mediactrl... yes checking for --enable-gstreamer8... no checking for --enable-printfposparam... yes <Detection of components needed for wxGTK> checking for linux/joystick.h... yes configure: WARNING: wxMetafile is not available on this system... disabled checking for CAIRO... yes checking for GST... yes checking for gcc precompiled header bug... no As you can see, it is detecting gstreamer just fine.> Don''t know of the symbol yet, I''ll have to find out when I get home > > tonight. And it does it no matter what, just from a simple ruby > > -rwxruby2.so, will cause the undefined symbol error to popup. I''ve > > been trying to re-compile wxGTK to recognize the MediaCtrl, as well as > > wxRuby, both 1.9.4, and SVN Head. Are you having the same problem on > > the AMD-64 Bit version of the gem? > The problem I had was that configure said it couldn''t find > ''gstreamer-0.10-plugins-base'', but I couldn''t find a package in Ubuntu > repository with exactly that name. Everything similar was installed, but > it still didn''t work.The unresolved symbol, which is a weird one, is _ZNK11wxMediaCtrl12GetClassInfoEv, I''ve never seen that one before, and I know wxGTK is compiled properly. I am going to test and see if the wxGTK Sample for media ctrl compiles just fine or what happens. I''m thinking that if it is a painful dependency, we should consider> shipping the default binary gem for Linux without MediaCtrl. The primary > requirement for the binary gems is that they are easy to get started with.As I have said, in the other thread, I am in agreement with you about this. But due to the fact of till we get a stable modularization setup for it, we''ll have to persue a setup of two binary gems, one with out the extra stuff such as GraphicsContext, MediaCtrl, OpenGL, etc, etc, till we get modularization working properly, in which we can separate these dependency required parts of wxGTK. L8ers, -- Mario Steele http://www.trilake.net http://www.ruby-im.net http://rubyforge.org/projects/wxruby/ http://rubyforge.org/projects/wxride/ http://rubyforge.org/projects/vwmc/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20080210/1eee5707/attachment.html
Mario Steele wrote:> The unresolved symbol, which is a weird one, is > _ZNK11wxMediaCtrl12GetClassInfoEv, I''ve never seen that one before, > and I know wxGTK is compiled properly. I am going to test and see if > the wxGTK Sample for media ctrl compiles just fine or what happens.That error is strange. Let us know how you get on.> > I''m thinking that if it is a painful dependency, we should consider > shipping the default binary gem for Linux without MediaCtrl. The > primary > requirement for the binary gems is that they are easy to get > started with. > > > > As I have said, in the other thread, I am in agreement with you about > this. But due to the fact of till we get a stable modularization > setup for it, we''ll have to persue a setup of two binary gems, one > with out the extra stuff such as GraphicsContext, MediaCtrl, OpenGL, > etc, etc,I was meaning a cruder solution - we still have a single set of binary gems, but the Linux one just doesn''t come with Wx::MediaCtrl. If people on Linux want to use that class, they have to build their own wxRuby. We should be able to use your recent patch to do that. Not ideal, but the set of people that are both on Linux and have to use this pretty specialist class should be quite small, and able to deal with it if it''s documented clearly. alex