From: Tom Harris Date: 2006-01-16T06:51:31+09:00 Subject: Re: Getting YAJB to work at all SAKURAI Masashi wrote: > I could run the yajb, setting {:jvm_stdout => :never} in > JBRIDGE_OPTIONS. Please try the option on your Windows. That did it! The :t for :jvm_output caused this. I cannot expect or require that all users of my open-source project will have cygwin when on Windows, and since the majority of my project is in Java, I'd like it to be platform agnostic as possible. That's why I initially wanted to use your bridge library, as it was the only one that seemed not to rely on native compilation. I wound up getting RJB working on my system, though it is in fact reliant on platform-specific native code to work. I think I'll be going back to YAJB now, though, because, as I said before, I want this software to work on all platforms as is, without a lot of hand-holding or forced choices on my part. Thanks! If there is any way to fix the library so that jvm_output works on mswin32, I think it'd be worth it. It'll certainly make debugging easier. Tom -- Posted via http://www.ruby-forum.com/.