Just to say that I''ve tagged 1.9.3 in the repository, but havent'' yet had time to create the release. Please do upload the binary builds as they become available. I''ll do the source package and linux-intel build tomorrow once I''be got some sleep! a
Alex Fenton wrote:> Just to say that I''ve tagged 1.9.3 in the repository, but havent'' yet > had time to create the release. Please do upload the binary builds as > they become available.Fast work Sean, thanks! I came across a tiny error in the rake tar.gz task. I''ve tested and I''m pretty sure it only affects making the source tarball. So I''ve cheated and tweaked the checkout to make the tarball and uploaded it. I''ll build the Linux intel binary this evening and do the doc packages, and announce. I''ll also get some feedback on whether people strongly feel they want arch-specific OS X builds. If it looks like there''s a lot of demand for it, I''m happy to turn those out. We can follow up with a 1.9.4 release in the next couple of weeks to get over my guilt of cheating! cheers alex
I built 1.9.3 on OS X 10.5 where it works fine. I just tried it on 10.4 and I am getting the following error, hopefully I will have some time to look into it later today. dyld: NSLinkModule() error dyld: Library not loaded: /usr/lib/libiconv.2.dylib Referenced from: /usr/local/lib/ruby/gems/1.8/gems/wxruby-1.9.3-universal-darwin/lib/wxruby2.bundle Reason: Incompatible library version: wxruby2.bundle requires version 7.0.0 or later, but libiconv.2.dylib provides version 5.0.0 Trace/BPT trap Sean On Jan 15, 2008 1:35 AM, Alex Fenton <alex at pressure.to> wrote:> Alex Fenton wrote: > > Just to say that I''ve tagged 1.9.3 in the repository, but havent'' yet > > had time to create the release. Please do upload the binary builds as > > they become available. > > Fast work Sean, thanks! > > I came across a tiny error in the rake tar.gz task. I''ve tested and I''m > pretty sure it only affects making the source tarball. So I''ve cheated > and tweaked the checkout to make the tarball and uploaded it. > > I''ll build the Linux intel binary this evening and do the doc packages, > and announce. I''ll also get some feedback on whether people strongly > feel they want arch-specific OS X builds. If it looks like there''s a lot > of demand for it, I''m happy to turn those out. > > We can follow up with a 1.9.4 release in the next couple of weeks to get > over my guilt of cheating! > > cheers > alex > > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development >
Sean Long wrote:> I built 1.9.3 on OS X 10.5 where it works fine. I just tried it on > 10.4 and I am getting the following error, hopefully I will have some > time to look into it later today. > > dyld: NSLinkModule() error > dyld: Library not loaded: /usr/lib/libiconv.2.dylib > Referenced from: > /usr/local/lib/ruby/gems/1.8/gems/wxruby-1.9.3-universal-darwin/lib/wxruby2.bundle > Reason: Incompatible library version: wxruby2.bundle requires > version 7.0.0 or later, but libiconv.2.dylib provides version 5.0.0 > Trace/BPT trap >I was looking at a thread on the wx-dev mailing list earlier today on this. http://lists.wxwidgets.org/cgi-bin/ezmlm-cgi?5:mss:97032:200801:dnbgeandbjlddooblmko I don''t have a 10.4 machine available to test it out, but it looks like there are some build-time options that can be passed to wxWidgets to work around this (follow the thread through). But these will also mean that some 10.5 specific features aren''t enabled. My view would be that that at the moment 10.4 is the right target for the binary builds. People needing 10.3 compatibility, or wanting the latest and greatest 10.5 features can build their own without too much difficulty (esp as wx 2.8.6 comes with Leopard) alex
Thanks for the link, I already did a commit with the needed changes to the rake file. The changes to build wxWidgets are already up at: http://wxruby.rubyforge.org/wiki/wiki.pl?HowToBuildWxWidgets With these changes I built wxRuby on OS X 10.5 Intel and ran the resulting gem on OS X 10.4 ppc, all was well. Now what should we do about the 1.9.3 Mac OS X gem which currently only works on 10.5? Do I upload the fixed gem that contains code after 1.9.3 was tagged? Sean> I was looking at a thread on the wx-dev mailing list earlier today on this. > > http://lists.wxwidgets.org/cgi-bin/ezmlm-cgi?5:mss:97032:200801:dnbgeandbjlddooblmko > > I don''t have a 10.4 machine available to test it out, but it looks like > there are some build-time options that can be passed to wxWidgets to > work around this (follow the thread through). > > But these will also mean that some 10.5 specific features aren''t > enabled. My view would be that that at the moment 10.4 is the right > target for the binary builds. People needing 10.3 compatibility, or > wanting the latest and greatest 10.5 features can build their own > without too much difficulty (esp as wx 2.8.6 comes with Leopard) > > > alex > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development >
Sean Long wrote:> Now what should we do about the 1.9.3 Mac OS X gem which currently > only works on 10.5? Do I upload the fixed gem that contains code after > 1.9.3 was tagged?Thanks for tracking it down. I don''t mind, really. We could cheat and re-upload the gem but I''m aware that''s caused a few problems in the past. Doing the gem build on Linux turned up one more small exception so we could tag 1.9.4 and release that. I can put a patch for that in tomorrow and tag, in which case I''ll delay announcing on c.l.r. Let me know what you prefer alex
I think we should just write off 1.9.3 and go with 1.9.4. Sean On Jan 15, 2008 2:02 PM, Alex Fenton <alex at pressure.to> wrote:> Sean Long wrote: > > Now what should we do about the 1.9.3 Mac OS X gem which currently > > only works on 10.5? Do I upload the fixed gem that contains code after > > 1.9.3 was tagged? > Thanks for tracking it down. > > I don''t mind, really. We could cheat and re-upload the gem but I''m aware > that''s caused a few problems in the past. Doing the gem build on Linux > turned up one more small exception so we could tag 1.9.4 and release > that. I can put a patch for that in tomorrow and tag, in which case I''ll > delay announcing on c.l.r. > > Let me know what you prefer > > > alex > > > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development >
Sean Long wrote:> I think we should just write off 1.9.3 and go with 1.9.4.Cool. There is another build bug which emerges when trying to make a gem with the latest rubygems. Gem::Platform is no longer a string but a complex object, so when somewhere we do "if platform.include?(/darwin/)" or something it breaks. I''ve got a fix for this at home but my internet was down. Once this is in we''ll need to do gem --update system on any place where we''re packaging. I''ll try and check it and few other small fixes in this evening with a view to tagging 1.9.4 shortly after. thanks alex