Google의 Native Client SDK, 좋은 물건이네요. 직접 저장해 보세요----chrome for future
10137 단어 Google
Download the Native Client SDK
Follow the steps below to download and install the SDK:
python ‑V
"in a terminal window, and make sure that the version of Python you have is 2.6.x or 2.7.x (if it's not, upgrade to one of those versions). C:\python27
) to the PATH environment variable . After you've installed Python, run the command "python ‑V
"in a Command Prompt window and verify that the version of Python you have is 2.6.x or 2.7.x. make
command on your system before you can build and run the examples. One easy way to get make
, along with several other useful tools, is to install Xcode Developer Tools . After installing Xcode, go to the Preferences menu, select Downloads and Components, and verify that Command Line Tools are installed. If you'd rather not install Xcode, you can download and build an open source version of make
. In order to build the command you may also need to download and install a copy of gcc . unzip nacl_sdk.zip
"in a Terminal window. Unzipping the SDK update utility creates a directory called
nacl_sdk
with the following files and directories:naclsdk
(and naclsdk.bat
for Windows) – the front end of the update utility, i.e., the command you run to download the latest bundles sdk_cache
– a directory with a manifest file that lists the bundles you have already downloaded sdk_tools
– the back end of the update utility, also known as the "sdk_tools"bundle nacl_sdk
directory and run naclsdk
with the "list"command to see a list of available bundles. The SDK includes a separate bundle for each version of Chrome/Pepper (see versioning information ). On Mac/Linux: $ cd nacl_sdk
$ ./naclsdk list
On Windows: > cd nacl_sdk
> naclsdk list
You should see output similar to this: Available bundles:
sdk_tools
description: Native Client SDK Tools, revision 1.5
stability: stable
recommended: yes
version: 1
revision: 5
pepper_14
description: Chrome 14 bundle, revision 1052
stability: stable
recommended: yes
version: 14
revision: 1052
pepper_15
description: Chrome 15 bundle, revision 1208
stability: beta
recommended: no
version: 15
revision: 1208
Currently installed bundles:
sdk_tools
description: Native Client SDK Tools, revision 1.5
stability: stable
recommended: yes
version: 1
revision: 5
This sample output shows that there are three bundles available for download, and that you have already installed the latest revision of the sdk_tools
bundle (it was included in the zip file you downloaded). In this example note that the pepper_15
bundle has the "recommended"attribute set to "no", meaning that the bundle is still experimental and not yet recommended for general use. naclsdk
with the "update"command to download particular bundles that are available. On Mac/Linux: $ ./naclsdk update
On Windows: > naclsdk update
By default, naclsdk
only downloads bundles that are recommended. Continuing with the earlier example, the "update"command would only download the sdk_tools
and the pepper_14
bundles, since the pepper_15
bundle is not yet recommended. If you want the pepper_15
bundle, you must either ask for it explicitly, or ask to get all of the available bundles. Use one of the commands below: $ ./naclsdk update pepper_15 # explicitly list the bundle you want to get, or
$ ./naclsdk update all # get all available bundles, including experimental bundles
Continuing with the earlier example, if you run naclsdk
with the "update all"command, you should see output similar to this: sdk_tools is already up-to-date.
Updating bundle pepper_14 to version 14, revision 1052
Updating bundle pepper_15 to version 15, revision 1208
Note that the toolchains for Mac and Linux are around 150 MB, so the downloads can take a while, even on a fast Internet connection. naclsdk
with the "list"command again; this will show you the list of available bundles and verify which bundles are installed. On Mac/Linux: $ ./naclsdk list
On Windows: > naclsdk list
Continuing with the earlier example, if you previously downloaded all of the available bundles, you should see output similar to this: Available bundles:
sdk_tools
description: Native Client SDK Tools, revision 1.5
stability: stable
recommended: yes
version: 1
revision: 5
pepper_14
description: Chrome 14 bundle, revision 1052
stability: stable
recommended: yes
version: 14
revision: 1052
pepper_15
description: Chrome 15 bundle, revision 1208
stability: beta
recommended: no
version: 15
revision: 1208
Currently installed bundles:
sdk_tools
description: Native Client SDK Tools, revision 1.5
stability: stable
recommended: yes
version: 1
revision: 5
pepper_14
description: Chrome 14 bundle, revision 1052
stability: stable
recommended: yes
version: 14
revision: 1052
pepper_15
description: Chrome 15 bundle, revision 1208
stability: beta
recommended: no
version: 15
revision: 1208
naclsdk
with the "update"command again will verify that your bundles are up-to-date, or warn if you there are new versions of previously installed bundles. On Mac/Linux: $ ./naclsdk update
On Windows: > naclsdk update
Continuing with the earlier example in which the pepper_15
bundle is not yet recommended, you should see output similar to this: sdk_tools is already up-to-date.
pepper_14 is already up-to-date.
If there is a new version of a previously installed bundle, the update utility will warn you with a message similar to this: WARNING: pepper_14 already exists, but has an update available.
Run update with the --force option to overwrite the existing directory.
Warning: This will overwrite any modifications you have made within this directory.
To dowload the new version of a bundle and overwrite the existing directory for that bundle, run naclsdk
with the --force
option. On Mac/Linux: $ ./naclsdk update --force
On Windows: > naclsdk update --force
Next steps:
이 내용에 흥미가 있습니까?
현재 기사가 여러분의 문제를 해결하지 못하는 경우 AI 엔진은 머신러닝 분석(스마트 모델이 방금 만들어져 부정확한 경우가 있을 수 있음)을 통해 가장 유사한 기사를 추천합니다:
그림 미리보기 호환 i 구글 Firefox<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 TRANSITIONAL//EN" "HTTP://WWW.W3.ORG/TR/XHTML1/DTD/XHTML1-TRANSITIONAL.DTD"...
텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
CC BY-SA 2.5, CC BY-SA 3.0 및 CC BY-SA 4.0에 따라 라이센스가 부여됩니다.