You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by 周晓强 <xi...@gmail.com> on 2008/03/09 14:11:17 UTC
[classlib][luni] What does HY_NO_SIG and HY_NO_THR mean in launcher source code
Re: [classlib][luni] What does HY_NO_SIG and HY_NO_THR mean in
launcher source code
Posted by Mark Hindess <ma...@googlemail.com>.
On 9 March 2008 at 21:11, "=?GB2312?B?1tzP/se/?=" <xi...@gmail.com>
wrote:
>
Passing the -Dhy.no.sig=true option to ant sets HY_NO_SIG and it means
that classlib (portlib) doesn't install a signal handler but leaves that
task to the VM.
Passing the -Dhy.no.thr=true option to ant sets HY_NO_THR and instructs
the classlib build not to build libhythr but to let the VM provide one.
There is also a HY_ZIP_API option which instructs classlib to use an API
for access to the Zip Cache rather than accessing internals directly.
I expect all of these will become the default in time.
-Mark.