On Friday 08 September 2006 17:31 Evgueni Brevnov wrote: > On 9/8/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: > > Evgueni Brevnov wrote: > > > On 9/7/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: > > >> Evgueni Brevnov wrote: > > >> > It seems we don't need vm.boot.library.path anymore. I propose to > > >> > remove it from the sources completely. What do you think? > > >> > > >> I wasn't sure. It is used in Classloader and Runtime, I suppose as a > > >> parallel to Sun's equivalent? > > > > > > No, not as Sun's equivalent. There are two different strategies to > > > load VM libraries. The first one which was implemented in DRLVM before > > > assumes full VM responsibility to load its dlls. It was done by means > > > of vm.boot.library.path option. Search order is also important. DRLVM > > > searches libraries in the following order java.library.path then > > > system path then vm.boot.library.path. Probably, it is wrong sequence > > > or it doesn't matter at all but it seems reference implementation does > > > it exactly the same way. > > > > Does the RI have a "vm.boot.library.path" option? > > Yes, it has I don't remeber exact name.
It is sun.boot.library.path. -- Gregory Shimansky, Intel Middleware Products Division --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
