Updating nacl sdk docs to match changed sample.

native_client_sdk/doc_generated/io2014.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="building-a-nacl-app">
 <span id="io2014"></span><h1 id="building-a-nacl-app"><span id="io2014"></span>Building a NaCl App</h1>
 <h2 id="in-the-browser">In the browser!</h2>
 <p>Follow along with Brad Nelson&#8217;s Google I/O 2014 talk.
 Explore our new in-browser development environment and debugger.</p>
 <p>Learn how easy it is to edit, build, and debug NaCl application
 all in your desktop web browser or on a Chromebook.
 Work either on-line or off-line!</p>
 <iframe class="video" width="500" height="281"
-src="//www.youtube.com/embed/OzNuzBDEWzk?rel=0" frameborder="0"></iframe><h3 id="our-web-based-tools">Our Web-based Tools</h3>
+src="//www.youtube.com/embed/OzNuzBDEWzk?rel=0" frameborder="0"></iframe><div><b><font color="#880000" style="font-size: 120%">
+NOTE: The NaCl Development Environment has changed since this video was made.
+The instructions below no longer match the video.
+</font></b></div><h3 id="our-web-based-tools">Our Web-based Tools</h3>
 <p>These development tools are a <a class="reference external" href="nacldev">work in progress</a>.
 At this point, they are a learning tool and demonstration of NaCl&#8217;s
 flexibility, but are not the recommended tools for a production application.
 In the future, that may change, but for the moment,
 to develop a substantial application for Native Client /
 Portable Native Client,
 we recommend you use the
 <a class="reference external" href="/native-client/sdk/download">Native Client SDK</a>.</p>
 <b><font color="#880000">
 NOTE: The NaCl Development Environment is not yet stable.
@@ skipping 10 matching lines @@
 <li><p class="first">Navigate to: chrome://flags and:</p>
 <ul class="small-gap">
 <li>Enable <strong>Native Client</strong>.</li>
 <li>Restart your browser by clicking <strong>Relaunch Now</strong>.</li>
 </ul>
 </li>
 <li>First run is slow (as it downloads and installs packages). Launch and allow
 initial install to complete before first use.</li>
 </ul>
 </div></blockquote>
-<p>When initially experimenting with the development environment,
-at this time, we recommend you run it without the debugger activated.
-Once you&#8217;re ready to apply the debugger, follow these steps:</p>
-<blockquote>
-<div><ul class="small-gap">
-<li>Install a usable version of
-<a class="reference external" href="http://www.chromium.org/getting-involved/dev-channel">Chrome Linux (M36+, Dev or Beta channel)</a>.</li>
-<li>Install the <a class="reference external" href="https://chrome.google.com/webstore/detail/nacl-debugger/ncpkkhabohglmhjibnloicgdfjmojkfd">Native Client Debugger Extension</a>.</li>
-<li>Install <a class="reference external" href="https://chrome.google.com/webstore/detail/gdb/gkjoooooiaohiceibmdleokniplmbahe">Native Client GDB</a>.</li>
-<li><p class="first">Navigate to: chrome://flags and:</p>
-<ul class="small-gap">
-<li>Enable <strong>Native Client GDB-based debugging</strong>.</li>
-<li>Restart your browser by clicking <strong>Relaunch Now</strong>.</li>
-</ul>
-</li>
-<li>NOTE: If you experience unexplained hangs, disable GDB-based debugging
-temporarily and try again.</li>
-</ul>
-</div></blockquote>
 <h4 id="editing">Editing</h4>
 <p>To follow along in this codelab, you&#8217;ll need to use a text editor to modify
 various files in our development environment.
 There are currently two editor options, nano or vim.
 We have an Emacs port, but it is not yet available in the Dev Environment
 (coming soon).
 If you&#8217;re unsure what to pick, nano is simpler to start with and has on-screen
 help.</p>
 <ul class="small-gap">
 <li><p class="first">You can open <strong>nano</strong> like this:</p>
@@ skipping 21 matching lines @@
 git config --global user.email johndoe&#64;example.com
 </pre>
 <h3 id="tour-follow-the-video">Tour (follow the video)</h3>
 <p>Create a working directory and go into it:</p>
 <pre class="prettyprint">
 $ mkdir work
 $ cd work
 </pre>
 <p>Download a zip file containing our sample:</p>
 <pre class="prettyprint">
-$ curl http://nacltools.storage.googleapis.com/io2014/voronoi.zip -O
+$ curl https://nacltools.storage.googleapis.com/io2014/voronoi.zip -O
 $ ls -l
 </pre>
 <p>Unzip the sample:</p>
 <pre class="prettyprint">
 $ unzip voronoi.zip
 </pre>
 <p>Go into the sample and take a look at the files inside:</p>
 <pre class="prettyprint">
 $ cd voronoi
 $ ls
 </pre>
 <p>Our project combines voronoi.cc with several C++ libraries to produce a NEXE
 (or Native Client Executable).</p>
 <img alt="/native-client/images/voronoi1.png" src="/native-client/images/voronoi1.png" />
-<p>The resulting application combines the NEXE with some Javascript to load
-the NaCl module, producing the complete application.</p>
-<img alt="/native-client/images/voronoi2.png" src="/native-client/images/voronoi2.png" />
 <p>Let&#8217;s use git (a revision control program) to track our changes.</p>
 <p>First, create a new repository:</p>
 <pre class="prettyprint">
 $ git init
 </pre>
 <p>Add everything here:</p>
 <pre class="prettyprint">
 $ git add .
 </pre>
 <p>Then commit our starting state:</p>
 <pre class="prettyprint">
 $ git commit -m &quot;imported voronoi demo&quot;
 </pre>
-<p>Now, likes run <strong>make</strong> to compile our program (NOTE: Changed since video,
-we&#8217;ve got Makefiles!):</p>
+<p>Now, run <strong>make voronoi</strong> to compile and run our program (NOTE: Changed since
+video, we&#8217;ve got Makefiles!):</p>
 <pre class="prettyprint">
-$ make
-</pre>
-<p>Oops, we get this error:</p>
-<pre class="prettyprint">
-voronoi.cc: In member function 'void Voronoi::Update()':
-voronoi.cc:506: error: 'struct PSContext2D_t' has no member named 'hieght'
-</pre>
-<p>We&#8217;ll need to start an editor to fix this.
-You&#8217;ll want to change <em>hieght</em> to <em>height</em> on line 506.
-Then rebuild:</p>
-<pre class="prettyprint">
-$ make -j10
-</pre>
-<p>Lets look at the diff:</p>
-<pre class="prettyprint">
-$ git diff
-</pre>
-<p>And commit our fix:</p>
-<pre class="prettyprint">
-$ git commit -am &quot;fixed build error&quot;
-</pre>
-<p>To test our application, we run a local web server, written in python.
-Run the server with this command (NOTE: Running through a Makefile
-now):</p>
-<pre class="prettyprint">
-$ make serve
-</pre>
-<p>Then, navigate to <a class="reference external" href="http://localhost:5103/">http://localhost:5103/</a> to test the demo.</p>
-<p>If you follow along with the demo video, you will discover the sample crashes
-when you change the thread count.</p>
-<h3 id="debugging">Debugging</h3>
-<p>If you haven&#8217;t installed the debugger at this point, skip to the next section.</p>
-<p>At this point, if you have the debugger installed, you should be able to open
-the developer console and view the resulting crash.</p>
-<p>You can see a backtrace with:</p>
-<pre class="prettyprint">
-bt
-</pre>
-<p>You can see active threads with:</p>
-<pre class="prettyprint">
-info threads
-</pre>
-<p>Currently, symbol information is limited for GLibC executables.
-We have improvements coming that will improve the experience further.</p>
-<p>For newlib and PNaCl executables you can retrieve full symbols information
-with:</p>
-<pre class="prettyprint">
-remote get irt irt
-add-symbol-file irt
-remote get nexe nexe
-add-symbol-file nexe
-</pre>
-<h3 id="fix-it-up">Fix it up</h3>
-<p>Return to the development environment and stop the test server,
-by pressing Ctrl-C.</p>
-<p>Open your editor again, navigate to line 485 and change <em>valu</em> to <em>value</em>.</p>
-<p>Then rebuild:</p>
-<pre class="prettyprint">
-$ make -j10
-</pre>
-<p>Check the diff and commit our fix:</p>
-<pre class="prettyprint">
-$ git diff
-$ git commit -am &quot;fixed thread ui bug&quot;
-</pre>
-<p>Now look at your commit history:</p>
-<pre class="prettyprint">
-$ git log
-</pre>
-<p>Run the demo again. And everything now works:</p>
-<pre class="prettyprint">
-$ make serve
+$ make voronoi
 </pre>
 <h3 id="thanks">Thanks</h3>
 <p>Thanks for checking out our environment.
 Things are rapidly changing and in the coming months you can expect to see
 further improvements and filling out of our platform and library support.</p>
 <p>Follow the status of the NaCl Dev Environment at <a class="reference internal" href="/native-client/nacldev.html"><em>this page</em></a>.</p>
 </section>
 
 {{/partials.standard_nacl_article}}