On Fri, Jul 11, 2008 at 9:52 AM, Sean Chittenden <[EMAIL PROTECTED]> wrote: >>> Ha! I just committed something nearly identical to this because I >>> couldn't >>> run the tests using ./setup.rb test. I didn't use the constant, however >>> and >>> did the File.join(...) for each open call. Anyway, let me know if trunk >>> works for the tests for you now. -sc >> >> The tests still do not work from setup.rb. When I try to run the test >> suite from the root directory, I get an error loading libxml_ruby. >> >> I typically run the tests like this: >> >> [EMAIL PROTECTED] libxml]$ ruby -I lib:ext:test test/test_suite.rb > > Can you try with just `./setup.rb test` ? I'm cautious about updating > lib/libxml.rb simply because it's included by everything and I'm still not > up to speed post-gem'ification re: path/packaging. > > I'll commit it for now, but I'm not entirely sure of its complete > correctness (unit tests work for me). If this breaks anything for anyone, > scream. -sc
I've added a patch to the tracker that adds a test task and a build task to the rake file. http://rubyforge.org/tracker/index.php?func=detail&aid=21172&group_id=494&atid=1973 If you apply that patch, you can just execute 'rake build' to build the extension, and 'rake test' to run the tests. Also, 'rake extensions:clean' will clean up the extensions directory. -- Aaron Patterson http://tenderlovemaking.com/ _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
