Lines Matching refs:we

14 I'm going to describe up to the point where we can build a simple application that prints out an Sk…
32 With the remote repo created, we create a .gclient configuration file. The
51 The name that we configured is the directory in which the repo will be checked
66 With the repo created we can go ahead and create our src/DEPS file. The DEPS
86 The `vars` sections defines variables we can use later in the file with the
87 `Var()` accessor. In this case, we define our root directory, a shorter name
88 for any googlecode repositories and a specific revision of Skia that we're
91 the repo they'll be using the same version of Skia that we've built and tested
94 The `deps` section defines our dependencies. Currently we have one dependency
95 which we're going to checkout into the `src/third_party/skia` directory.
98 Once done, we can use gclient to checkout our dependencies.
107 Now, we've run into a problem. Skia itself has a `DEPS` file which defines the
148 The final piece of infrastructure we need to set up is GYP. GYP is a build
149 system generator, in this project we're going to have it build ninja
152 First, we need to add GYP to our project. We'll do that by adding a new entry
161 tip-of-tree revision in your `DEPS` file).  A quick `gclient sync` and we
164 In order to run GYP we'll create a wrapper script. I've called this
200 In the case of 1, we're telling GYP to include (-I) the
202 variables for Skia to compile. In the case of 2, we're telling GYP that the
241 them.)  The `target_name` defines the name of the build target which we'll
242 provide to ninja. It will also be the name of the executable that we build.
245 before our sources are built. In this case, we depend on the `skia_lib` target
274 Now, we can run:
278 And, we get an error. Turns out, Skia is looking for a `find\_mac\_sdk.py` file in
286 Here we using the `File()` function of `gclient` to specify that we're checking
292 These correspond to the configurations we specified in `using\_skia.gyp`.