![]() A manifest file will then specify which version of the module to load based on the end-user’s architecture. To support a wide variety of devices you must compile separate versions of your Native Client module for different processors on end-user machines. These nexe files are also operating-system-independent, but they are not processor-independent. Native Client also supports architecture-specific nexe files. The same pexe will run on Windows, Mac OS X, Linux, and ChromeOS and it will run on x86-32, x86-64, ARM and MIPS processors. Chrome can load pexe files embedded in web pages and execute them as part of a web application.Īs explained in the Technical Overview, PNaCl modules are operating-system-independent and processor-independent. ![]() pexe extension using the PNaCl toolchain in the Native Client SDK. Portable Native Client (PNaCl) modules are written in C or C++ and compiled into an executable file ending in a. If you haven’t read the Native Client Technical Overview and Tutorial, we recommend starting with those. It is intended for developers who have experience writing, compiling, and linking C and C++ code. This document describes how to build Native Client modules. ![]() Can’t find libraries containing necessary symbols.Libraries and header files provided with the SDK.Using the PNaCl tools to compile, link, debug, and deploy SDK toolchains versus your hosted toolchain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |