Differences in path handling in ikvmc DLL vs. Java jar execution
Paul Chambre <[email protected]> Fri, 18 Nov 2016 12:39:34 -0700
| Newsgroups | gmane.comp.java.ikvm.devel |
|---|---|
| Message-ID | <CAJwVo5HGVTc6PWarvT5q-2u9hpXsExps_-5A-BonUKdLjbAaew@mail.gmail.com> |
--===============3006813293048832051== Content-Type: multipart/alternative; boundary=94eb2c0e668a3bddf30541987733 --94eb2c0e668a3bddf30541987733 Content-Type: text/plain; charset=UTF-8 Hi folks, I noticed some differences in file access from code within an ikvmc DLL vs. that same code executed by Java from a jar. One particular example is a properties file that is passed to one of our classes with a -D. Initially, whether local to the application (next to the jar/dll) or fully qualified, the file was inaccessible to the jar code. I then added . to the classpath in the manifest of the jar, and that allowed the jar code, when run through Java -jar, to access properties files in the same directory as the jar.However, this change did not help DLLs make with ikvmc from that jar. Those dlls still cannot access the properties file when it's in the same directory as the DLL (or fully qualified). Are there other properties to be set specifically for ikvmc, to define the classpath or other "local" path configurations? Thanks, Paul --94eb2c0e668a3bddf30541987733 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hi folks,</div><div><br></div><div>I noticed some dif= ferences in file access from code within an ikvmc DLL vs. that same code ex= ecuted by Java from a jar.</div><div><br></div><div>One particular example = is a properties file that is passed to one of our classes with a -D. </div>= <div><br></div><div>Initially, whether local to the application (next to th= e jar/dll) or fully qualified, the file was inaccessible to the jar code. I= then added . to the classpath in the manifest of the jar, and that allowed= the jar code, when run through Java -jar, to access properties files in th= e same directory as the jar.However, this change did not help DLLs make wit= h ikvmc from that jar. Those dlls still cannot access the properties file w= hen it's in the same directory as the DLL (or fully qualified).</div><d= iv><br></div><div>Are there other properties to be set specifically for ikv= mc, to define the classpath or other "local" path configurations?= </div><div><br></div><div>Thanks,<br>Paul</div> </div> --94eb2c0e668a3bddf30541987733-- --===============3006813293048832051== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ --===============3006813293048832051== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ikvm-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ikvm-developers --===============3006813293048832051==--