On Fri, Jun 7, 2013 at 4:52 PM, Ben Reser <b...@reser.org> wrote: > I really don't understand why this change is necessary at all since as > you can see above the source tree is added to the load path with -I.
So I think I understand the logic here. Windows doesn't seem to have any wrapper for running the swig tests (like make check-swig-rb on Unix) so you're probably running run-test.rb directly. Since Windows doesn't support out of tree builds you don't see the problem that we see on Unix. I'm not a Ruby expert but if there's a way to add the current directory to the load path in the Ruby script like you can with -I from the command line I'd suggest that. Unfortunately, I can't seem to get the Ruby bindings to build on Windows. They blow up on a bunch of syntax errors in the Ruby headers for me and I can't crib off the buildbots since they don't seem to build them either.
