blocks|key|3150673|text|要将NXEngine移植到Native+Client，您需要移植NXEngine本身(当然！)加上它的依赖项。让我们逐一考虑它们：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3150674|3150675|SDL已经移植了，但可以使用更新，因为该端口比它晚了几个版本。它驻留在http://code.google.com/p/naclports/source/browse#svn%252Ftrunk%252Fsrc%252Flibraries%252Ffreetype-2.1.10.|unordered-list-item|offset|length|style|BOLD|3150676|的naclports社区存储库中(请参阅我关于freetype|CODE|3150677|freetype需要移植的说明，包括它的依赖项，据我所知，naclports已经移植并驻留在naclports中|3150678|3150679|移植到Native+Client非常类似于移植到一个新的-在很多方面更像Linux-的操作系统。但是，有一些重要的区别：|3150680|本地客户端的“操作系统”|3150681|是，或PPAPI，提供对浏览器功能的访问的一组API。主要的移植工作通常是让您的代码使用Pepper+API打开文件、显示图形、播放声音等(SDL使输入、声音和图形变得更容易)。要打开文件，人们通常使用nacl_mounts，这是一个包装了Pepper+file+API的库，这样就可以将应用程序的HTML5网络存储或URL作为文件系统挂载到Web上，然后使用熟悉的fopen、fread等。从Pepper+25开始，nacl_mounts的一部分包含在NaCl开发工具包中。|3150682|本地客户端模块不能使用本地操作系统调用，也没有访问主机文件系统的权限。这是出于安全原因，并确保portability.|3150683|There目前在Pepper中不是非实验性的字体应用程序接口。因此，所有字体渲染都必须在您的代码中完成，任何.ttf文件都必须作为应用程序的一部分提供，因为本地客户端将无法访问.ttf。出于安全原因，主机系统上的文件。|3150684|3150685|3150686|Chrome/Pepper25推荐：过去，Pepper+API调用只能从主线程进行。这需要对游戏和其他多线程程序进行重大重构，这些程序被设计为在一个线程上渲染，在另一个线程上播放音乐。从Chrome+25及更高版本开始，此限制将不复存在。有关详情，请参阅https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_message_loop。以Chrome25或更新版本为目标，从而使用NaCl+SDK的Pepper25版本，可能会减少这类应用程序的重构工作量。|3150687|在网页上运行本地客户端的：这个问题提到，你可以“访问网页并在浏览器中玩游戏”。重要的是要知道，目前只有Chrome支持Native+Client。当前一代的Native+Client和即将推出的Portable+Native+Client之间也有一个重要的区别，前者需要将Web应用程序放在Chrome+web+Store中才能使Native+Client工作，后者将允许在任何网页上显示Native+Client内容。为了让网页上的访问者能够以最少的弯路使用当前一代的基于氯化钠的应用程序，Chrome+web+Store内联安装(参见https://developers.google.com/chrome/web-store/docs/inline_installation)可以避免用户去Chrome+Web+Store的需要。|3150688|关于+naclports**:**+naclports的说明:+Native+Client是一个基于社区的存储库。它包含几个库和以前的端口。您可以在http://code.google.com/p/naclports/source/browse/trunk/src/libraries/上查看naclports中的库列表。虽然它包含了如何进行移植的有用示例，但naclports并不适合胆小鬼，因为它经常崩溃，而且-考虑到它是在志愿者/尽最大努力的基础上维护的-可能需要时间来修复。|3150689|附加提示：*在这个答案中有一些指向指南的附加提示和提示：Google+Chrome+Extension+using+NaCL+with+an+external+library。|3150690|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/naclports/source/browse#svn%252Ftrunk%252Fsrc%252Flibraries%252Ffreetype-2.1.10|1|https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_message_loop|2|https://developers.google.com/chrome/web-store/docs/inline_installation|3|http://code.google.com/p/naclports/source/browse/trunk/src/libraries/|4|https://stackoverflow.com/questions/13920954/google-chrome-extension-using-nacl-with-an-external-library/13932232#13932232^0|0|0|0|3|Z|2O|0|0|1|9|0|0|8|T|9|0|0|0|0|2T|B|53|5|59|5|5T|B|0|0|1I|4|2G|4|0|0|0|0|I|3J|2A|1|0|C|1|7H|1Z|2|0|0|2|3|B|3|9|I|9|42|9|50|9|22|1X|3|0|0|6|S|1N|4|0^^$0|@$1|2|3|4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1R|8|@$F|1S|G|1T|H|I]]|9|@$F|1U|G|1V|1|1W]]|A|$]]|$1|J|3|K|5|6|7|1X|8|@$F|1Y|G|1Z|H|L]]|9|@]|A|$]]|$1|M|3|N|5|E|7|20|8|@$F|21|G|22|H|I]|$F|23|G|24|H|L]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|25|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|26|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|27|8|@]|9|@]|A|$]]|$1|T|3|U|5|E|7|28|8|@$F|29|G|2A|H|L]|$F|2B|G|2C|H|L]|$F|2D|G|2E|H|L]|$F|2F|G|2G|H|L]]|9|@]|A|$]]|$1|V|3|W|5|E|7|2H|8|@]|9|@]|A|$]]|$1|X|3|Y|5|E|7|2I|8|@$F|2J|G|2K|H|L]|$F|2L|G|2M|H|L]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|2N|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|2O|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|2P|8|@$F|2Q|G|2R|H|I]]|9|@$F|2S|G|2T|1|2U]]|A|$]]|$1|13|3|14|5|6|7|2V|8|@$F|2W|G|2X|H|I]]|9|@$F|2Y|G|2Z|1|30]]|A|$]]|$1|15|3|16|5|6|7|31|8|@$F|32|G|33|H|I]|$F|34|G|35|H|I]|$F|36|G|37|H|L]|$F|38|G|39|H|L]|$F|3A|G|3B|H|L]|$F|3C|G|3D|H|L]]|9|@$F|3E|G|3F|1|3G]]|A|$]]|$1|17|3|18|5|6|7|3H|8|@$F|3I|G|3J|H|I]]|9|@$F|3K|G|3L|1|3M]]|A|$]]|$1|19|3|-4|5|6|7|3N|8|@]|9|@]|A|$]]]|1A|$1B|$5|1C|1D|1E|A|$1F|1G]]|1H|$5|1C|1D|1E|A|$1F|1I]]|1J|$5|1C|1D|1E|A|$1F|1K]]|1L|$5|1C|1D|1E|A|$1F|1M]]|1N|$5|1C|1D|1E|A|$1F|1O]]]]

To port NXEngine to Native Client, you'd need to port NXEngine itself (of course!) plus its dependencies. Let's consider each of them:

<ul>
<li>SDL has already been ported, but could use an update, as the port is a couple of versions behind. It resides in the <code>naclports</code> community repository at <a href="http://code.google.com/p/naclports/source/browse#svn%2Ftrunk%2Fsrc%2Flibraries%2FSDL-1.2.14" rel="nofollow noreferrer">http://code.google.com/p/naclports/source/browse#svn%2Ftrunk%2Fsrc%2Flibraries%2FSDL-1.2.14</a> (see my note about <code>naclports</code> below).</li>
<li>SDL_ttf would need to be ported including its dependencies, which as far as I can tell are just freetype</li>
<li>freetype has already been ported and resides in naclports at <a href="http://code.google.com/p/naclports/source/browse#svn%2Ftrunk%2Fsrc%2Flibraries%2Ffreetype-2.1.10" rel="nofollow noreferrer">http://code.google.com/p/naclports/source/browse#svn%2Ftrunk%2Fsrc%2Flibraries%2Ffreetype-2.1.10</a>.</li>
</ul>

Porting to Native Client is very much like porting to a new - in many ways rather Linux-like - operating system. However, there are some important differences:

<ul>
<li>The "operating system" API of Native Client is Pepper, or PPAPI, a set of APIs that provide access to the capabilities of the browser. The bulk of the porting work is typically to get your code to use the Pepper APIs for opening files, displaying graphics, playing sounds, etc. (SDL makes input, sound, and graphics a lot easier, though). To open files, people often use <code>nacl_mounts</code>, a library that wraps the Pepper File API, so that one can mount the HTML5 Web Storage of the app or URLs on the web as file systems and then use the familiar <code>fopen</code>, <code>fread</code>, etc. From Pepper 25, parts of <code>nacl_mounts</code> are included in the NaCl SDK.</li>
<li>Native Client modules cannot use native operating system calls and do not have access to the host file system. This is for security reasons and to ensure portability.</li>
<li>There is no non-experimental font API in Pepper currently. Hence all font rendering must be done in your code and any <code>.ttf</code> file must be supplied as part of the app, as the Native Client will not able to access <code>.ttf</code>. files on the host system for security reasons.</li>
</ul>

Chrome/Pepper 25 recommended: Historically, Pepper API calls could only be made from the main thread. This required significant refactoring of games and other multithreaded programs that were designed to, say, render on one thread and play music on another thread. From Chrome 25 and onwards this restriction no longer exists. For details see <a href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_message_loop" rel="nofollow noreferrer">https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_message_loop</a>. Targeting Chrome 25 or newer and thus using the Pepper 25 version of the NaCl SDK is likely to reduce the amount of refactoring work for this class of applications.

Running Native Client on a web page: The question mentions that one could "visit the page and play the game within a browser". It is important to know that only Chrome supports Native Client at this time. There is also an important difference between current-generation Native Client, which requires that the web app be put in Chrome Web Store for Native Client to work, and the forthcoming Portable Native Client, which will allow Native Client content on any web page. To allow visitors on a web page to use a current-generation NaCl-based app with minimal detours, Chrome Web Store Inline Installation (see <a href="https://developers.google.com/chrome/web-store/docs/inline_installation" rel="nofollow noreferrer">https://developers.google.com/chrome/web-store/docs/inline_installation</a>) can obviate the need for users to go to the Chrome Web Store.

A note on <code>naclports</code>: <code>naclports</code> is a community-based repository for Native Client. It contains several libraries and previous ports. You can see the list of libraries in <code>naclports</code> at <a href="http://code.google.com/p/naclports/source/browse/trunk/src/libraries/" rel="nofollow noreferrer">http://code.google.com/p/naclports/source/browse/trunk/src/libraries/</a>. While it contains useful examples of how to do ports, <code>naclports</code> is not for the faint-hearted as it often breaks and - given that it's maintained on a volunteer/best-effort basis - may take time to get fixed.

Additional pointers:* There are some additional tips and pointers to guides in this answer: <a href="https://stackoverflow.com/questions/13920954/google-chrome-extension-using-nacl-with-an-external-library/13932232#13932232">Google Chrome Extension using NaCL with an external library</a>.

blocks|key|5966679|text|你问的问题很有趣，我已经移植了！它真的不需要太多的改变(但我还是做了很多改变)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5966680|我已经有一段时间没有尝试重新编译它了，所以它可能已经坏了。也许我会花点时间试着让它再次工作。:)|5966681|你可以在http://github.com/binji/nacl-nxengine上找到它|offset|length|5966682|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/binji/nacl-nxengine^0|0|0|4|11|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]]]]

Funny you ask, I've already ported it! It really doesn't require much changing (but I made a lot of changes anyway).

I haven't tried to recompile it in a while, so it is probably broken. Maybe I'll spend some time trying to get it working again... :)

You can find it at <a href="http://github.com/binji/nacl-nxengine" rel="nofollow">http://github.com/binji/nacl-nxengine</a>

So, Native Client can run C++ code from the browser, and I know that the <a href="http://nxengine.sourceforge.net/" rel="nofollow">NX Engine</a> is build from C++, and can be tweaked to run on Android. So, if the NX Engine can run Cave Story, and that can in theory run in the native client, how do you get it to work and host so that one could visit the page and play the game within a browser?

How can one port Cave Story (NXEngine) to Native Client

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

因此，Native Client可以从浏览器运行C++代码，我知道是从C++构建的，可以调整以在安卓上运行。那么，如果NX引擎可以运行Cave Story，理论上可以在本地客户端运行，那么如何让它工作并托管，以便用户可以在浏览器中访问页面和玩游戏？

问如何将一个端口洞穴故事(NXEngine)连接到本机客户端
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何将一个端口洞穴故事(NXEngine)连接到本机客户端EN