similar to: swig-3.0.7 for xapian-bindings to tcl

Regarding the earlier mail about [xapian-core-1.2.24] /tests/api_replicate.cc compiled under MSYS/MINGW (g++ 5.3.0). It seems likely that the error was specific to certain g++ versions. https://github.com/mxe/mxe/issues/1448 Eric at ERICS-NETBOOK /c/WORK $ cat test.cpp #include <stdlib.h> int setenv(const char *name, const char *value, int overwrite) { return _putenv_s(name, value); }

REMINDER: wxruby-swig is an experimental rewrite of wxRuby, using SWIG. It is not yet useful. The official wxRuby is still at 0.2.1. The 0.0.3 release of wxruby-swig is able to run the "minimal.rb" sample, which includes menu event handling. As always, it is available at: http://qualitycode.com/repos/wxruby-swig/ I also created a tarball this time, so you can just download that and

(Mostly for Roy): I saw this on the SWIG list, and wonder if it might be related to the problems we have been seeing where multi-arg typemaps end up invoking the wrong wrapper methods. (Not the newly-discovered directorout stuff). Perhaps if we switched to "compactdefaultargs" things would start to work more sanely. Looking at this section of the SWIG docs, it looks like it should

In trying to add wxTextCtrl to wxruby-swig, I''ve been running into a problem with the argument conversion that appears to be a SWIG director bug. It is tied to multiple inheritance, and is related to SWIG specifically making director''s ''initialize'' take a first argument, but because ''initialize'' is static there isn''t a self value

You can''t rake without swig now. I keep swig out of my path so I can do a build without swig to be sure it works with the download. Exception `Errno::ENOENT'' at ./rake/rakewx.rb:20 - No such file or directory - swig -version No such file or directory - swig -version ./rake/rakewx.rb:20:in ``'' ./rake/rakewx.rb:20:in `have_good_swig'' ./rake/rakewx.rb:254:in

Yep - simpleITK is available at github.com/SimpleITK/SimpleITK. There's also github.com/SimpleITK/SimpleITKRInstaller - a devtools based installer for mac and linux. CMake has a range of build environments. I experimented with MSYS2 and mingw makefiles, but had trouble with incompatibilities in the path required by CMake and those options - from memory the sh in RTools/bin caused problems.

I have a minimal working version of a SWIG-based wxRuby that can bring up an empty Frame with a title. On my system, it crashes on exit. I suspect this is the same problem that I mentioned months ago when I first upgraded to wxWindows 2.4.2. The problem mysteriously vanished at some point, but now it is back. I fiddled with this new code for several frustrating hours, and couldn''t

Hi, all I didn't get any response from swig for my question. see if I can get some help here Thanks ---------- Forwarded message ---------- From: charlie <charlie.xia.fdu@gmail.com> Date: Tue, Nov 4, 2008 at 1:55 PM Subject: SWIG with R and C++ STL To: swig-user@lists.sourceforge.net Hi all, I am new to SWIG. I encountered some problem when I try to SWIG to R some C++ modules. Here

If SWIG can be made to do a good job with Python/Ruby/Perl etc bindings around LLVM, I would be very interested in this. I'm personally interested in seeing both Python and Ruby bindings, and in having them be as easily maintained as possible. I think it would be interesting to see what the SWIG-style solution can do in this direction as opposed to the C-binding approach. If it results in

I have some conditional code based on the SWIG version. Current versions of SWIG 1.3.30 still don''t fix %trackobjects correctly so I''m going to remove the test for now so it builds correctly with my version of SWIG. Hopefully before 1.3.30 is released we''ll have a better trackobjects in SWIG. Roy _______________________________________________ wxruby-users

Hi, I've been lurking around the LLVM project for a couple of months now. The two recent threads about python bindings for LLVM ([1] and [2]), combined with the fact that I am looking for at GSoC project at the moment. Lead to the idea of making the "public" parts of LLVM SWIG[3]-friendly and basing a set of python bindings on this. My reasoning for doing it this way, is that it

I''ve checked a number of new .i files into the wxruby-swig tree. Not all of them are fully tested, but I thought it would be better for them to be there than to have somebody start duplicating the work. I''ve also added the ''caret'' and ''image'' samples, as well as the generic etc/test.rb. These need the unreleased SWIG-1.3.22. The current

I did some testing this morning, and wasn''t happy with the error messages presented to the user if they didn''t have the right SWIG version. I realized that the detection was happening at the wrong place in the code. We were detecting the swig version while *creating* the swig tasks, rather than while *executing* a swig task. This led to misleading output from rake. So I moved

I compiled a C++ SWIG interface. It works fine from irb (interactive Ruby). But, I''d like to embed this Swig module into a Rails application. (I did not write this particular Rails application and know very little about Rails per-se.) I know that, to start WEBrick, you say ruby script/server I looked at script/server and it does not look like the right place to stick the

I just pushed a new wxruby-swig, which includes the known MSWin rakefile changes. It also has some significant internal improvements that will make it easier to add classes, and it includes support for one new class (wxEvent). wxruby-swig is now licensed under the "MIT license". wxRuby will remain under the wxWindows license as long as we are releasing the old code base. When we

A few days ago, someone asked me why I am using wxpp instead of SWIG. The question prompted me to revisit and re-evaluate SWIG, and I now believe it would be best to convert wxRuby to SWIG. SWIG has greatly improved its C++ support since the last time I looked at it, and I think its Ruby support has improved quite a bit as well. Also, now that I have written wxpp, I understand the nature of

After seeing contributions from Dmitry and Alex, I''m wondering how we can better organize and encourage user contributions. ORGANIZING Maybe identifying what is still missing in wxRuby-SWIG and publishing a prioritized todo list could useful to contributors. GETTING NOTICED It might be useful to post a link to the unassigned todo list each month to comp.lang.ruby and ask for

Dear all, I was trying to use the R swig wrapper with R 2.7 and shogun ( http://www.shogun-toolbox.org ) but it fails completely, as in doesn't even compile and even after patching then though compiling - crashes... So I asked on swig-users/swig-devel CC'ing the potential R maintainer but I never received a reply. I now wonder if anyone here could help or would be willing to maintain

I decided to try my hand at hacking SWIG and successfully produced a patch that fixes the error I demonstrated. I''m not -positive- it''s correct for all cases but I''ll re-run my version of SWIG over the library and see how things turn out. Roy

Hi everyone, As Kevin has just announced, wxruby-swig has been moved into CVS as a toplevel project. It still is not in a "releasable" form yet, but it now builds on more systems than it doesn''t, and is moving towards stability. Because of the complexity of the build environment, we''re using rake (http://rake.rubyforge.org) as a build system instead of the standard