[NaCl SDK Docs] Remove links to developers.google.com

native_client_sdk/doc_generated/devguide/tutorial/tutorial-part2.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="c-tutorial-getting-started-part-2">
 <span id="tutorial2"></span><h1 id="c-tutorial-getting-started-part-2"><span id="tutorial2"></span>C++ Tutorial: Getting Started (Part 2)</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#overview" id="id1">Overview</a></li>
 <li><p class="first"><a class="reference internal" href="#using-the-native-client-sdk-build-system" id="id2">Using the Native Client SDK build system</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#simplifying-the-makefile" id="id3">Simplifying the Makefile</a></li>
@@ skipping 14 matching lines @@
 <li><a class="reference internal" href="#loading-the-page-and-creating-the-module" id="id12">Loading the page and creating the module</a></li>
 </ul>
 </li>
 <li><a class="reference internal" href="#example-specific-behavior-with-example-js" id="id13">Example-specific behavior with example.js</a></li>
 </ul>
 
 </div><section id="overview">
 <h2 id="overview">Overview</h2>
 <p>This tutorial shows how to convert the finished PNaCl web application from
 <a class="reference internal" href="/native-client/devguide/tutorial/tutorial-part1.html"><em>Part 1</em></a> to use the Native Client SDK build system and
-common JavaScript files. It also demonstrates some techniques to make your
-web application <cite>Content Security Policy (CSP)-compliant
-&lt;http://developer.chrome.com/apps/contentSecurityPolicy.html&gt;</cite>, which is
-necessary for <a class="reference external" href="https://developer.chrome.com/apps/about_apps.html">Chrome Apps</a>.</p>
+common JavaScript files. It also demonstrates some techniques to make your web
+application <a class="reference external" href="/apps/contentSecurityPolicy">Content Security Policy (CSP)-compliant</a>, which is necessary for <a class="reference external" href="/apps/about_apps">Chrome Apps</a>.</p>
 <p>Using the Native Client SDK build system makes it easy to build with all of the
 SDK toolchains, and switch between the Debug and Release configurations. It
 also simplifies the makefiles for your project, as we&#8217;ll see in the next
 section. Finally, it adds some useful commands for <a class="reference internal" href="/native-client/sdk/examples.html#id1"><em>running</em></a> and <a class="reference internal" href="/native-client/sdk/examples.html#debugging-the-sdk-examples"><em>debugging</em></a>
 your application.</p>
 <p>The finished code for this example can be found in the
 <code>pepper_$(VERSION)/getting_started/part2</code> directory in the Native Client SDK
 download.</p>
 </section><section id="using-the-native-client-sdk-build-system">
 <h2 id="using-the-native-client-sdk-build-system">Using the Native Client SDK build system</h2>
@@ skipping 88 matching lines @@
 <dd>The name of the project to build. This variable determines the name of the
 library or executable that will be generated. In the above example, we call
 the target <code>part2</code>, which will generate an executable called
 <code>part2.pexe</code> for PNaCl. For NaCl toolchains, the executable&#8217;s file name
 will be given a suffix for its architecture. For example, the ARM executable
 is called <code>part2_arm.nexe</code>.</dd>
 <dt>LIBS</dt>
 <dd>A list of libraries that this executable needs to link against. The library
 search path is already set up to only look in the directory for the current
 toolchain and architecture. In this example, we link against <code>ppapi_cpp</code>
-and <code>ppapi</code>. <code>ppapi_cpp</code> is needed to use the <a class="reference external" href="https://developers.google.com/native-client/peppercpp/">Pepper C++ interface</a>. <code>ppapi</code> is
-needed for communicating with the browser.</dd>
+and <code>ppapi</code>. <code>ppapi_cpp</code> is needed to use the <a class="reference external" href="/native-client/pepper_stable/cpp/">Pepper C++ interface</a>. <code>ppapi</code> is needed for communicating
+with the browser.</dd>
 <dt>CFLAGS</dt>
 <dd>A list of extra flags to pass to the compiler. In this example, we pass
 <code>-Wall</code>, which turns on all warnings.</dd>
 <dt>LDFLAGS</dt>
 <dd>A list of additional flags to pass to the linker. This example does not need
 any special linker flags, so this variable is omitted.</dd>
 <dt>SOURCES</dt>
 <dd>A list of C or C++ sources to compile, separated by spaces. If you have a
 long list of sources, it may be easier to read if you put each file on its
 own line, and use <code>\</code> as a line-continuation character. Here&#8217;s an example:</dd>
@@ skipping 43 matching lines @@
 $(eval $(call LINK_RULE,$(TARGET),$(SOURCES),$(LIBS),$(DEPS)))
 endif
 </pre>
 <p>Finally, the NMF rule generates a NaCl manifest file (<code>.nmf</code>) that references
 each executable generated in the previous step:</p>
 <pre class="prettyprint">
 $(eval $(call NMF_RULE,$(TARGET),))
 </pre>
 </section></section><section id="making-index-html-work-for-chrome-apps">
 <h2 id="making-index-html-work-for-chrome-apps">Making index.html work for Chrome Apps</h2>
-<p>This section describes the changes necessary to make the HTML and JavaScript
-in part1 CSP-compliant. This is required if you want to build a <a class="reference external" href="https://developer.chrome.com/apps/about_apps.html">Chrome App</a>, but is not necessary
-if you want to use PNaCl on the open web.</p>
+<p>This section describes the changes necessary to make the HTML and JavaScript in
+part1 CSP-compliant. This is required if you want to build a <a class="reference external" href="/apps/about_apps">Chrome App</a>, but is not necessary if you want to use PNaCl on the open
+web.</p>
 <section id="csp-rules">
 <h3 id="csp-rules">CSP rules</h3>
-<p><a class="reference external" href="http://developer.chrome.com/apps/contentSecurityPolicy.html#what">Chrome Apps CSP</a>
-restricts you from doing the following:</p>
+<p><a class="reference external" href="/apps/contentSecurityPolicy#what">Chrome Apps CSP</a> restricts you from doing
+the following:</p>
 <ul class="small-gap">
 <li>You can’t use inline scripting in your Chrome App pages. The restriction
 bans both <code>&lt;script&gt;</code> blocks and event handlers (<code>&lt;button onclick=&quot;...&quot;&gt;</code>).</li>
 <li>You can’t reference any external resources in any of your app files (except
 for video and audio resources). You can’t embed external resources in an
 iframe.</li>
 <li>You can’t use string-to-JavaScript methods like <code>eval()</code> and <code>new
 Function()</code>.</li>
 </ul>
 </section><section id="making-index-html-csp-compliant">
@@ skipping 205 matching lines @@
 // This function is called by common.js when a message is received from the
 // NaCl module.
 function handleMessage(message) {
   var logEl = document.getElementById('log');
   logEl.textContent += message.data;
 }
 </pre>
 </section></section>
 
 {{/partials.standard_nacl_article}}