blocks|key|2525737|text|如果许可是可以接受的(LGPL)，Java本机访问提供了比JNI更友好的FFI；移植可能会减少到剥离RNI层，而仅仅公开一个简单的‘C’可调用的API。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2525738|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/twall/jna/^0|H|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If the licensing is acceptable (LGPL), <a href="https://github.com/twall/jna/" rel="nofollow noreferrer">Java Native Access</a> provides a rather friendlier FFI than the JNI does; porting may reduce to stripping away the RNI layer and just exposing a simple 'C'-callable API.

blocks|key|1030150|text|看看南国防军+--也许可以通过这种方式直接访问RNI；或者至少它将使移植它的工作比手动进行JNI容易得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1030151|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/twall/jna/^0|2|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Take a look at <a href="https://github.com/twall/jna/" rel="nofollow noreferrer">JNA</a> - it might be possible to access the RNI DLL directly that way; or at least it will make the job of porting it much easier than doing JNI manually.

blocks|key|2525702|text|如果可能的话，我建议您考虑通过用纯->重写C%2B%2B代码来避免RNI的C%2B%2B+JNI移植问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2525703|编写JNI代码需要大量的注意，如果你弄错了，JVM的稳定性就会受到威胁。我的建议是，如果可能的话，尽量避免。|2525704|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If possible, I suggest that you consider avoiding the RNI -> JNI porting problem by rewriting the C++ code in pure Java. 

Writing JNI code requires a huge amount of care, and places JVM stability at risk if you get it wrong. My advice is to avoid it if you possibly can.

blocks|key|999659|text|虽然我从未使用过微软的RNI，只有Sun的JNI，但我希望您不能像使用JNI风格的DLL那样直接使用RNI风格的DLL。我也不知道会自动转换或桥接RNI到JNI的任何事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|999660|您没有提到是否有C%2B%2B+RNI的源代码，但我假设您是这样做的，因为您提到了继承项目。如果您有任何C%2B%2B/C经验，并且对RNI+DLL提供的功能有很好的了解，那么将它移到JNI应该不会太困难。在移植上投入的时间很可能会为它的继续发展带来回报。|999661|您向维基百科上的JNI条目提供的链接在使用JNI编码方面有很多有用的链接。如果没有更多的细节，很难给出任何其他的建议。|offset|length|999662|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Java_Native_Interface^0|0|0|2|4|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

While I have never used Microsoft's RNI, only Sun's JNI, I would expect that you couldn't directly use an RNI-style DLL as if it were a JNI-style DLL. I am also unaware of anything that would automatically convert or bridge RNI to JNI.

You do not mention if you have the source to the C++ RNI DLL, although I'll assume you do since you mention inheriting the project. If you have any C++/C experience, and have a good idea of what functionality the RNI DLL is providing, it should not be too difficult to move it to JNI. The time invested in porting it would likely pay off for maintaining it moving forward.

The link you provided to the JNI entry on <a href="http://en.wikipedia.org/wiki/Java_Native_Interface" rel="nofollow noreferrer">Wikipedia</a> has lots of helpful links on coding with JNI. Without a bit more detail, it is hard to give any other advice.

blocks|key|1031493|text|Java本机接口:程序员指南和规范是我找到的编写JNI代码的最佳资源。它没有涵盖RNI+->+JNI，但它是学习JNI工作方式的一个很好的起点。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1031494|事实上，它非常干燥，而且读起来也不是特别有趣，但它是我能找到的最好的。|1031495|entityMap|0|LINK|mutability|MUTABLE|url|http://java.sun.com/docs/books/jni/^0|0|H|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

<a href="http://java.sun.com/docs/books/jni/" rel="nofollow noreferrer">Java Native Interface: Programmer's Guide and Specification</a> is the best resource that I've found for writing JNI code. It doesn't cover RNI -> JNI, but it is a great* starting point for learning how JNI works.

*It's actually very dry, and not particularly fun to read, but it's the best I've been able to find.

I've inherited a legacy J++ project. I've upgraded this project to standard Sun Java successfully.

However, this project includes a native C++ dll which the Java code talks to via the Microsoft-specific <a href="http://en.wikipedia.org/wiki/Java_Native_Interface#Microsoft.27s_RNI" rel="nofollow noreferrer">RNI framework</a>.

Needless to say, calling System.loadLibrary("myRniNativeDll") now throws a UnsatisifiedLinkError, saying one of the dependencies couldn't be found.

I'm totally clueless how to migrate a C++ RNI dll to a JNI dll; I've no idea where to begin. I have the C++ source code, but I don't know how to build a JNI dll. Are there any tips/tutorials/online materials you Java experts can point me to?

J++ to Java: how to migrate from RNI to JNI?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我继承了一个遗留的J++项目。我已经成功地将这个项目升级为标准的Sun。然而，该项目包括一个本机C++ dll，该代码通过特定于微软的进行对话。不用说，调用System.loadLibrary("myRniNativeDll")现在抛出一个UnsatisifiedLinkError，表示找不到其中一个依赖项。我完全不知道如何将C++ RNI dll迁移到JNI；我不知道从哪里开始。我有C++源代码

问J++到Java:如何从RNI迁移到JNI？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问J++到Java:如何从RNI迁移到JNI？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问J++到Java:如何从RNI迁移到JNI？
EN