Native Client

Native Client SDK

To build Native Client modules, you must download and install the Native Client Software Development Kit (SDK).

The SDK includes the following:

support for multiple Pepper versions
The SDK contains multiple bundles that let you compile Native Client modules using different versions of the Pepper API (e.g., Pepper 29 or Pepper 30). Review the Release Notes for a description of the new features included in each Pepper version to help you decide which bundle to use to develop your application. In general, Native Client modules compiled using a particular Pepper version will work in corresponding versions of Chrome and higher. For example, a module compiled using the Pepper 29 platform will work in Chrome 29 and higher.
update utility
The naclsdk utility (naclsdk.bat on Windows) lets you download new bundles that are available, as well as new versions of existing bundles.
toolchains
Each platform includes two toolchains—one for compiling with newlib and one for compiling with glibc, two different implementations of the C standard library. Both toolchains include 32- and 64-bit customized Native Client-compatible versions of standard compilers, linkers, and other tools.
examples
Each example in the SDK generally includes an HTML file, a manifest file, one or more C or C++ files and header files, a Makefile, and pre-built 32- and 64-bit executable .nexe files.
Makefiles
Makefiles have been kept simple so that they are easy to understand, use, and modify. Glance through or run the Makefiles included with the examples to determine the commands that are needed to build an application, then plug those commands into your own build system if you prefer.
tools
The SDK includes a number of additional tools, which you can use for tasks such as validating Native Client modules and running modules from the command line.

To download and install the SDK, follow the instructions on the Download page.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.