OLD | NEW |
1 How to download Skia | 1 How to download Skia |
2 ==================== | 2 ==================== |
3 | 3 |
4 Install gclient and git | 4 Install depot_tools and Git |
5 ----------------------- | 5 --------------------------- |
6 | 6 |
7 Follow the instructions on | 7 Follow the instructions on [Installing Chromium's |
8 http://www.chromium.org/developers/how-tos/install-depot-tools to download | 8 depot_tools](http://www.chromium.org/developers/how-tos/install-depot-tools) |
9 chromium's depot_tools (which includes gclient ). | 9 to download depot_tools (which includes gclient, git-cl, and Ninja). |
10 | 10 |
11 depot_tools will also install git on your system, if it wasn't installed | 11 <!--?prettify lang=sh?--> |
| 12 |
| 13 git clone 'https://chromium.googlesource.com/chromium/tools/depot_tools.git' |
| 14 export PATH="${PWD}/depot_tools:${PATH}" |
| 15 |
| 16 depot_tools will also install Git on your system, if it wasn't installed |
12 already. | 17 already. |
13 | 18 |
14 | 19 |
15 | 20 Configure Git |
16 Configure git | |
17 ------------- | 21 ------------- |
18 | 22 |
19 $ git config --global user.name "Your Name" | 23 <!--?prettify lang=sh?--> |
20 $ git config --global user.email you@example.com | |
21 | 24 |
22 Download your tree | 25 git config --global user.name "Your Name" |
| 26 git config --global user.email you@example.com |
| 27 |
| 28 Clone the Skia repository |
| 29 ------------------------- |
| 30 |
| 31 <!--?prettify lang=sh?--> |
| 32 |
| 33 git clone https://skia.googlesource.com/skia.git |
| 34 cd skia |
| 35 |
| 36 Get Skia's dependencies and generate Ninja build files |
| 37 ------------------------------------------------------ |
| 38 |
| 39 <!--?prettify lang=sh?--> |
| 40 |
| 41 python bin/sync-and-gyp |
| 42 |
| 43 <!-- |
| 44 python tools/git-sync-deps |
| 45 python ./gyp_skia |
| 46 --> |
| 47 |
| 48 Compile all default targets |
| 49 --------------------------- |
| 50 |
| 51 <!--?prettify lang=sh?--> |
| 52 |
| 53 ninja -C out/Debug |
| 54 |
| 55 Execute Skia tests |
23 ------------------ | 56 ------------------ |
24 | 57 |
25 $ mkdir skia | 58 [More about Skia correctness testing tools](../dev/testing/testing) |
26 $ cd skia | 59 |
27 $ gclient config --name . --unmanaged https://skia.googlesource.com/skia.git | 60 <!--?prettify lang=sh?--> |
28 $ gclient sync | 61 |
29 $ git checkout master | 62 out/Debug/dm |
| 63 |
| 64 Execute Skia sample application |
| 65 ------------------------------- |
| 66 |
| 67 [More about Skia's SampleApp](sample/sampleapp) |
| 68 |
| 69 <!--?prettify lang=sh?--> |
| 70 |
| 71 out/Debug/SampleApp |
30 | 72 |
31 At this point, you have everything you need to build and use Skia! If | 73 At this point, you have everything you need to build and use Skia! If |
32 you want to make changes, and possibly contribute them back to the Skia | 74 you want to make changes, and possibly contribute them back to the Skia |
33 project, read on... | 75 project, read [How To Submit a Patch](../dev/contrib/submit). |
34 | |
35 Making changes | |
36 -------------- | |
37 | |
38 First create a branch for your changes: | |
39 | |
40 $ git checkout --track origin/master -b my_feature master | |
41 | |
42 After making your changes, create a commit | |
43 | |
44 $ git add [file1] [file2] ... | |
45 $ git commit | |
46 | |
47 If your branch gets out of date, you will need to update it: | |
48 | |
49 $ git pull --rebase | |
50 $ gclient sync | |
51 | |
52 Uploading changes for review | |
53 ---------------------------- | |
54 | |
55 $ git cl upload | |
56 | |
57 You may have to enter a Google Account username and password to authenticate | |
58 yourself to codereview.chromium.org. A free gmail account will do fine, or any | |
59 other type of Google account. It does not have to match the email address you | |
60 configured using git config --global user.email above, but it can. | |
61 | |
62 The command output should include a URL (similar to | |
63 https://codereview.chromium.org/111893004/ ) indicating where your changelist | |
64 can be reviewed. | |
65 | |
66 Once your change has received an LGTM ("looks good to me"), you can check the | |
67 "Commit" box on the codereview page and it will be committed on your behalf. | |
68 | |
69 Once your commit has gone in, you should delete the branch containing your | |
70 change: | |
71 | |
72 $ git checkout master | |
73 $ git branch -D my_feature | |
74 | |
OLD | NEW |