Andi Vajda <va...@apache.org> wrote: > On Fri, 19 Mar 2010, Bill Janssen wrote: > > > I see we're still not doing this: > > > > http://www.mail-archive.com/pylucene-...@osafoundation.org/msg02204.html > > > > That is, lucene or jcc or whatever fails to load because the location of > > jvm.dll isn't on the value of the user's "Path" environment variable. > > > > What if I submitted a patch? I keep tripping over this darned bug. > > I sure don't want to mess with people's Path behind their backs.
You're already doing this in jcc/__init__.py, so don't be too pure :-). > If you can do this with yet another command line option used at jcc > invocation to cause it to add this to the __init__.py file, then > sure. Yes, that makes sense. Or perhaps in the initVM, with an optional parameter to enable or disable it. That way it could be controlled by an individual program, regardless of how the default was compiled in. > But it's got to be off by default. Just to bikeshed a bit, having it be off by default doesn't make much sense to me; you'd have the same problem you have now. It should be on by default, and there should be a way to disable it, for people who are doing things with the PATH. As I discuss in the thread referenced above (and generally agreed to by the participants in that thread), it would goes at the end of the path, so it's a backstop. And maybe we're going at this the wrong way. Maybe I should just get -R or -rpath working with the mingw ld. Bill
