On Tue, Jun 11, 2013 at 7:16 AM, Ben Reser <b...@reser.org> wrote: > 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.
Sorry Ben, I missed your first email on this until today (cmpilato - thanks for the heads up!) > 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. That's correct. > 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. Let me know if r1492295 fixes the problem for you. As you mentioned there are other problems running the Ruby tests on Windows on an out of tree build so I can't run the tests to completion, but this should fix the LoadError you encountered and AFAICT works with [Ruby 1.8 | 1.9] x [in-tree | out-of-tree builds]. -- Paul T. Burba CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development Skype: ptburba > 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.
