As I mentioned in October (wow, time moves quickly!), there are two big items I would like to have in a 0.2 release of wxRuby: 1. Binary builds for as many platforms as possible 2. A document describing how to use the standard wxWindows/wxPython documentation to develop wxRuby apps In order for this to happen in any reasonable time frame, I will need help. For those of you here who are not C++ coders, but want to help the project, this is a great opportunity. I know this is a busy time of the year for many people, so I don''t want to put too much pressure on you. However, most of these tasks will only take a few hours (hopefully), so perhaps you can find the time. I can do a binary build for Linux. Although I would love to have RPM and DEB packages, I do not see those as being necessary for this release. If anyone out there is able to build an RPM or DEB, please let me know! I just realized/discovered that I can theoretically do a cross-platform MinGW build on my Debian box. However, I am not completely confident that I can get it to compile, nor that the result would actually run under Windows. Therefore, I am asking for a volunteer who can build a MinGW version of the wxRuby library. Gour? We need a Windows library that works with Andy Hunt''s Ruby installer. This might be the MinGW build, so after someone builds it, we can have several Windows users test it. If it is not compatible, we will need an MSVC build, which Curt volunteered for earlier. However, last I heard the MSVC version was asserting at run time. Are you still available for this, Curt? I would like to have Mac OS X and BSD binaries available. Can BSD use a generic Linux library? If not, is there anyone here to could build a library on either of those platforms? At the same time, we can make the changes Gour requested to be compatible with his Gentoo "emerge" script, so that gives us yet another platform. Documentation. I just added a couple rough pages to the wiki. One describes the basic rules for translating C++ wxWindows documentation into wxRuby documentation. The other is a placeholder for where a tutorial should begin. Corrections and feedback are welcome, of course. Kevin
Kevin Smith wrote:> > As I mentioned in October (wow, time moves quickly!), there are two big > items I would like to have in a 0.2 release of wxRuby: > > 1. Binary builds for as many platforms as possible > 2. A document describing how to use the standard wxWindows/wxPython > documentation to develop wxRuby apps > > In order for this to happen in any reasonable time frame, I will need > help. For those of you here who are not C++ coders, but want to help the > project, this is a great opportunity. I know this is a busy time of the > year for many people, so I don''t want to put too much pressure on you. > However, most of these tasks will only take a few hours (hopefully), so > perhaps you can find the time. > > I can do a binary build for Linux. Although I would love to have RPM and > DEB packages, I do not see those as being necessary for this release. If > anyone out there is able to build an RPM or DEB, please let me know! > > I just realized/discovered that I can theoretically do a cross-platform > MinGW build on my Debian box. However, I am not completely confident > that I can get it to compile, nor that the result would actually run > under Windows. Therefore, I am asking for a volunteer who can build a > MinGW version of the wxRuby library. Gour? > > We need a Windows library that works with Andy Hunt''s Ruby installer. > This might be the MinGW build, so after someone builds it, we can have > several Windows users test it. If it is not compatible, we will need an > MSVC build, which Curt volunteered for earlier. However, last I heard > the MSVC version was asserting at run time. Are you still available for > this, Curt?Yes, I still want to do this. I too had recently discovered that its possible to use an MSYS/MinGW build with straight microsoft build (i.e., the Ruby Installer). And since Gour had sucessfully built with MSYS/MinGW I think this is better than continuing my unfruitful use of VC++. Curt --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.548 / Virus Database: 341 - Release Date: 12/5/2003
Curt Hibbs (curt@hibbs.com) wrote:> Yes, I still want to do this. I too had recently discovered that its > possible to use an MSYS/MinGW build with straight microsoft build (i.e., the > Ruby Installer). And since Gour had sucessfully built with MSYS/MinGW I > think this is better than continuing my unfruitful use of VC++.I can do the MinGW/MSYS build but since I''m in the midst of the seminar, I wo''t be able to do it before Monday. note: I was not able to make static build because of linking errors. Sincerely, Gour -- Gour gour@mail.inet.hr Registered Linux User #278493
Gour wrote:> I can do the MinGW/MSYS build but since I''m in the midst of the seminar, I > wo''t be able to do it before Monday.Monday would be great. If anyone else can do one earlier, that would also be nice. Please email me the .dll directly, along with at least a list of other dependencies, like which version of wxWindows. When you email it to me, please put it inside a zip file or tarball, or just give me a URL to somewhere on the web that you have uploaded the file.> note: I was not able to make static build because of linking errors.For 0.2 I am ok with a dynamic build. Incremental steps are fine. Thanks, Kevin
Do you want binaries based off of the current CVS source? I need to write some scripts for making the Mac OS X version. The problem is that you can''t execute the samples from the command line because Ruby isn''t a bundle, and doesn''t have any resources. My plan is to bundle each of the executables inside their own .app structure. The .rb files will be inside of the Resources directory, and a copy of the ruby interpreter (just the interpreter, not the full runtime library) will be in the MacOS subdirectory. This will allow people without ruby to test the samples. (Shouting out to the Mac OS X posse - does this sound ok?) Nick Kevin Smith wrote:> As I mentioned in October (wow, time moves quickly!), there are two > big items I would like to have in a 0.2 release of wxRuby: > > 1. Binary builds for as many platforms as possible > 2. A document describing how to use the standard wxWindows/wxPython > documentation to develop wxRuby apps > > In order for this to happen in any reasonable time frame, I will need > help. For those of you here who are not C++ coders, but want to help > the project, this is a great opportunity. I know this is a busy time > of the year for many people, so I don''t want to put too much pressure > on you. However, most of these tasks will only take a few hours > (hopefully), so perhaps you can find the time. > > I can do a binary build for Linux. Although I would love to have RPM > and DEB packages, I do not see those as being necessary for this > release. If anyone out there is able to build an RPM or DEB, please > let me know! > > I just realized/discovered that I can theoretically do a > cross-platform MinGW build on my Debian box. However, I am not > completely confident that I can get it to compile, nor that the result > would actually run under Windows. Therefore, I am asking for a > volunteer who can build a MinGW version of the wxRuby library. Gour? > > We need a Windows library that works with Andy Hunt''s Ruby installer. > This might be the MinGW build, so after someone builds it, we can have > several Windows users test it. If it is not compatible, we will need > an MSVC build, which Curt volunteered for earlier. However, last I > heard the MSVC version was asserting at run time. Are you still > available for this, Curt? > > I would like to have Mac OS X and BSD binaries available. Can BSD use > a generic Linux library? If not, is there anyone here to could build a > library on either of those platforms? > > At the same time, we can make the changes Gour requested to be > compatible with his Gentoo "emerge" script, so that gives us yet > another platform. > > Documentation. > > I just added a couple rough pages to the wiki. One describes the basic > rules for translating C++ wxWindows documentation into wxRuby > documentation. The other is a placeholder for where a tutorial should > begin. Corrections and feedback are welcome, of course. > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > >
Nick wrote:> Do you want binaries based off of the current CVS source?For the moment, yes. I would like to put together a "pre-release" binaries package, just to see what it would look like, and so people can test it on the various platforms. Then we would tag the source, and build binaries from that, for the actual 0.2 release.> I need to write some scripts for making the Mac OS X version.Your plan sounds ok to me, as a non-Mac person. If you don''t get any other feedback, you should try it and see how it goes. Thanks, Kevin