You are viewing the documentation for Chrome/Pepper 31 and the corresponding
pepper_31 bundle in the Native Client SDK.
If you are developing with a different SDK bundle, you should select the corresponding version of the Native Client
documentation using the links below.
Native Client developer documentation is updated and versioned with each release of Chrome/Pepper and the Native Client SDK. We generally recommend developing with the latest version of Chrome/Pepper and the corresponding SDK bundle. See the SDK Release Notes for a list of features in the latest versions of Pepper and the corresponding SDK bundle.
The remainder of this document describes the versioning pipeline for Chrome/Pepper, the Native Client SDK, and the Native Client developer documentation.
The versioning pipeline for Chrome, Pepper, and the Native Client SDK
Chrome and Pepper versions
The Pepper Plug-in API (PPAPI), called Pepper for convenience, is an open-source, cross-platform API for browser plug-ins. From the point of view of Native Client, Pepper is a set of APIs that allow a C or C++ Native Client module to communicate with the hosting browser and get access to system-level functions in a safe and portable way.
Each version of Chrome includes a corresponding version of Pepper (for example, Chrome 31 includes the Pepper 31 APIs). Native Client modules compiled using a particular version of Pepper will generally work in corresponding versions of Chrome and higher. For example, a module compiled using Pepper 31 will work in Chrome 31 and higher.
Release channels and the Chrome release schedule
A new version of Chrome is released approximately every 6 weeks. Releases are distributed through three release channels: dev, beta, and stable. Each version of Chrome is released first in the dev channel, then in the beta channel, and finally in the stable channel. To see which version of Chrome is currently in which channel, check the Chromium Release Calendar.
The Native Client SDK includes multiple bundles. Each bundle corresponds to a version of Chrome/Pepper, and includes toolchains, header files,
and libraries that you can use to compile Native Client modules for that version of Chrome/Pepper. Modules compiled with a specific bundle
will work in the corresponding version of Chrome and higher. For example, modules compiled with the
will work in Chrome 31 and higher.
SDK bundles are assigned a stability level (dev, beta, stable, or post-stable) that generally correlates to the current release
channel of the corresponding Chrome/Pepper version. For example, the
pepper_31 bundle will be at the "dev"
stability level at about the same time that Chrome/Pepper 31 is in the dev release channel.
The SDK also includes a special bundle called
pepper_canary. This bundle contains the toolchains, libraries, and examples
that are designed to work with the most recent development builds of the
canary channel of the Chrome browser.
pepper_canary bundle to test the newest Pepper APIs or SDK tools that are not yet available in regular
Pepper bundles and released versions of Chrome. You can run a canary build of Chrome side-by-side with a stable version. When you ship a
Native Client application you should build it with a numbered Pepper bundle that corresponds to
the version of Chrome that you plan to support.
The versioning pipeline for Native Client documentation
Native Client developer documentation follows the same versioning scheme as Chrome/Pepper and the Native Client SDK. A new version of the documentation is created for each SDK bundle. You should use the documentation that corresponds to the SDK bundle and the version of Chrome/Pepper that you are developing with.
You can access the Native Client developer documentation by stability level, as shown in the table below.
|Stability level||URL||Currently contains documentation for|
Note that the documentation for the stable level is located at the root level of the Native Client doc site, rather than in a "stable" subdirectory.
The documentation for each SDK bundle progresses from the dev, to the beta, to the root (top level) directory based on the bundle's stability level. The documentation moves to a new directory roughly every 6 weeks, at about the same time a new Chrome version is released.
Note: Because the Chrome and SDK bundle release schedules are not precisely synchronized, the actual version numbers for
the same stability level of Chrome and the SDK may not be identical. For instance, the version of Chrome in the dev channel might be version 25,
while the SDK bundle at the dev level might be
pepper_24. If you access Native Client documentation by stability level, you should
check the Pepper version (shown at the top of the nav bar at the left) to be sure it matches the SDK bundle you are using, and that it is
equal to or less than the version of Chrome you are using.
Alternatively, you can access the Native Client developer documentation by Pepper version number, as shown in the table below.