1.. _sdk-index: 2 3################# 4Native Client SDK 5################# 6 7To build Native Client modules, you must download and install the Native 8Client Software Development Kit (SDK). 9 10The SDK includes the following: 11 12support for multiple Pepper versions 13 The SDK contains **bundles** that let you compile Native Client modules 14 using different versions of the 15 `Pepper API </overview.html#link_pepper>`_ 16 (e.g., Pepper 30 or Pepper Canary). Review the 17 :doc:`Release Notes <release-notes>` for a description of the new features 18 included in each Pepper version to help you decide which bundle to 19 use to develop your application. In general, Native Client modules 20 compiled using a particular Pepper version will work in 21 corresponding versions of Chrome and higher. For example, a module 22 compiled using the Pepper 30 platform will work in Chrome 30 and 23 higher. 24 25update utility 26 The ``naclsdk`` utility (``naclsdk.bat`` on Windows) lets you download new 27 bundles that are available, as well as new versions of existing bundles. 28 29toolchains 30 Each platform includes three toolchains---one for Portable Native Client 31 (PNaCl) applications, one for compiling architecture-specific Native 32 Client applications with newlib, and a third native NaCl toolchain for 33 compiling with glibc. Newlib and glibc are two different implementations 34 of the C standard library. All toolchains contain Native Client-compatible 35 versions of standard compilers, linkers, and other tools. 36 See :doc:`this document </nacl-and-pnacl>` to help you choose the 37 right toolchain. 38 39examples 40 Each example in the SDK includes C or C++ source files and header files 41 illustrating how to use NaCl and Pepper, along with a Makefile to build 42 the example using each of the toolchains. 43 44tools 45 The SDK includes a number of additional tools, which you can use for 46 tasks such as validating Native Client modules and running modules 47 from the command line. 48 49To download and install the SDK, follow the instructions on the 50:ref:`Download <download>` page. 51 52