3

I understand the there are multiple toolchains availble in "Native Client SDK". If i am not wrong there are 5 toolchains.

one PNaCl Toolchain

PNaCl  - for building pexe (These pexe are platform independent and architecture independent)

Multiple NaCl Toolchain

for building nexe (These nexe are platform independent and but not architecture independent)

NaCl32 
NaCl64
NaClRAM

one PPAPI Toolchain

PPAPI

I want to know for what purpose we can use PPAPI toolchain and how to use it??

Devesh Agrawal
  • 8,982
  • 16
  • 82
  • 131

1 Answers1

4

The PPAPI toolchain build uses the native compiler (on Windows, this is cl.exe). This produces a shared object/DLL that will be loaded by Chrome. Unlike Native Client, it is not sandboxed.

Like NaCl, it links against the ppapi library, so you can using Pepper (PPAPI) functions. Unlike NaCl and PNaCl, there are no limitations on other APIs you can use. You can use the Windows API, for example. This makes it easier to get your application working while you are porting it to Native Client.

That being said: you cannot release a PPAPI plugin in the Chrome Web Store.

The PPAPI toolchain is primarily used to make it easier to develop a NaCl application. This video describes the process. It is a bit old so some things have changed, but the basic steps are the same.

binji
  • 1,860
  • 9
  • 9