"Using Skia" tutorial: googlecode -> googlesource

site/user/sample/building.md

 Building with Skia Tutorial
 ===========================
 
 dsinclair@chromium.org
 
 
 This document describes the steps used to create an application that uses Skia.  The assumptions are that you're using:
 
   * [git](http://git-scm.com)
   * [gclient](https://code.google.com/p/gclient/)
@@ skipping 59 matching lines @@
 Create a src/DEPS file with the following:
 
 ~~~~
 
   vars = {
     "skia_revision": "a6a8f00a3977e71dbce9da50a32c5e9a51c49285",
   }
 
   deps = {
     "src/third_party/skia/":
-        "http://skia.googlecode.com/skia.git@" + Var("skia_revision"),
+        "http://skia.googlesource.com/skia.git@" + Var("skia_revision"),
   }
 
 ~~~~
 
 There are two sections to the `DEPS` file at the moment, `vars` and `deps`.
 The `vars` sections defines variables we can use later in the file with the
 `Var()` accessor. In this case, we define our root directory, a shorter name
-for any googlecode repositories and a specific revision of Skia that we're
+for any googlesource repositories and a specific revision of Skia that we're
 going to use. I've pinned to a specific version to insulate the application
 from changes in the Skia tree. This lets us know that when someone checks out
 the repo they'll be using the same version of Skia that we've built and tested
 against.
 
 The `deps` section defines our dependencies. Currently we have one dependency
 which we're going to checkout into the `src/third_party/skia` directory.
 
 Once the deps file is created, commit and push it to the remote repository.
 Once done, we can use gclient to checkout our dependencies.
@@ skipping 17 matching lines @@
     solutions = [
       { "name"        : "src",
         "url"         : "https://bitbucket.org/dj2/usingskia.git",
         "deps_file"   : "DEPS",
         "managed"     : True,
         "custom_deps" : {
         },
         "safesync_url": "",
       },
       { "name"        : "src/third_party/skia",
-        "url"         : "http://skia.googlecode.com/skia.git@a6a8f00a3977e71dbce9da50a32c5e9a51c49285",
+        "url"         : "http://skia.googlesource.com/skia.git@a6a8f00a3977e71dbce9da50a32c5e9a51c49285",
         "deps_file"   : "DEPS",
         "managed"     : True,
         "custom_deps" : {
         },
         "safesync_url": "",
       },
     ]
     cache_dir = None
 
 This is a little annoying at the moment since I've duplicated the repository
 revision number in the `.gclient` file. I'm hoping to find a way to do this
 through the `DEPS` file, but until then, this seems to work.
 
 With that done, re-run `gclient sync` and you should see a whole lot more
 repositories being checked out. The
 `src/third_party/skia/third_party/externals` directory should now be
 populated.
 
 GYP
 ---
 
 The final piece of infrastructure we need to set up is GYP. GYP is a build
 system generator, in this project we're going to have it build ninja
 configuration files.
 
 First, we need to add GYP to our project. We'll do that by adding a new entry
 to the deps section of the `DEPS` file.
 
     "src/tools/gyp":
-        (Var("googlecode_url") % "gyp") + "/trunk@1700",
+        (Var("googlesource_url") % "gyp") + "/trunk@1700",
 
 As you can see, I'm going to put the library into `src/tools/gyp` and checkout
 revision 1700 (note, the revision used here, 1700, was the head revision at
 the time the `DEPS` file was written. You're probably safe to use the
 tip-of-tree revision in your `DEPS` file).  A quick `gclient sync` and we
 should have everything checked out.
  
 In order to run GYP we'll create a wrapper script. I've called this
 `src/build/gyp_using_skia`.
 
@@ skipping 106 matching lines @@
 
 Now, we can run:
 
     $ ./build/gyp_using_skia
 
 And, we get an error. Turns out, Skia is looking for a `find\_mac\_sdk.py` file in
 a relative tools directory which doesn't exist. Luckily, that's easy to fix
 with another entry in our DEPS file.
 
     "src/tools/":
-        File((Var("googlecode_url") % "skia") + "/trunk/tools/find_mac_sdk.py@" +
+        File((Var("googlesource_url") % "skia") + "/trunk/tools/find_mac_sdk.py@" +
             Var("skia_revision")),
 
 Here we using the `File()` function of `gclient` to specify that we're checking
 out an individual file. Running `gclient sync` should pull the necessary file
 into `src/tools`.
 
 With that, running `build/gyp\_using\_skia` should complete successfully. You
 should now have an `out/` directory with a `Debug/` and `Release/` directory inside.
 These correspond to the configurations we specified in `using\_skia.gyp`.
 
@@ skipping 16 matching lines @@
       {
         # A change to a .gyp, .gypi or to GYP itself should run the generator.
         "name": "gyp",
         "pattern": ".",
         "action": ["python", "src/build/gyp_using_skia"]
       }
     ]
 
 Adding the above to the end of DEPS and running gclient sync should show the
 GYP files being updated at the end of the sync procedure.