harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Deakin (JIRA)" <j...@apache.org>
Subject [jira] Created: (HARMONY-2201) [classlib][luni] Add creation of stub jvm.dll to luni module
Date Wed, 15 Nov 2006 16:38:37 GMT
[classlib][luni] Add creation of stub jvm.dll to luni module
------------------------------------------------------------

                 Key: HARMONY-2201
                 URL: http://issues.apache.org/jira/browse/HARMONY-2201
             Project: Harmony
          Issue Type: Improvement
          Components: Classlib
            Reporter: Oliver Deakin
            Priority: Minor


It is standard practise when writing a VM launcher to link against invocation API providing
libraries called jvm.dll/libjvm.so. The RI and J9 VMs both follow the convention of placing
a jvm.lib file (on Windows) into <jdk>/lib, and the actual jvm.dll/libjvm.so in the
appropriate place under jre/bin. Harmony differs from this convention in two ways:

1) There is no jvm.lib provided in the deploy/jdk/lib directory. This means that any Windows
user writing a custom launcher will not be able to make calls to our invocation API. It makes
sense in this case to create a stubbed set of invocation API natives to build a jvm.lib in
the appropriate place. We currently do something similar to create a stubbed vmi.lib for linking
against.

2) The libraries providing the invocation API are currently called harmonyvm.dll/libharmonyvm.so.
I would suggest that these are renamed to jvm.dll/libjvm.so to follow the conventional naming
scheme.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message