Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(70)

Side by Side Diff: native_client_sdk/src/doc/sdk/examples.rst

Issue 23531031: Minor cleanups for SDK devsite docs. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 7 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « native_client_sdk/src/doc/rest-devsite-examples.rst ('k') | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 .. _sdk-examples-2: 1 .. _sdk-examples-2:
2 2
3 Running the SDK Examples 3 Running the SDK Examples
4 ======================== 4 ========================
5 5
6 Every Native Client SDK bundle comes with a folder of example applications. 6 Every Native Client SDK bundle comes with a folder of example applications.
7 Each example demonstrates one or two key Native Client programming concepts. 7 Each example demonstrates one or two key Native Client programming concepts.
8 After you've :doc:`downloaded the SDK <download>`, follow the instructions 8 After you've :doc:`downloaded the SDK <download>`, follow the instructions
9 on this page to build and run the examples. 9 on this page to build and run the examples.
10 10
(...skipping 134 matching lines...) Expand 10 before | Expand all | Expand 10 after
145 contain .nexe files for all target architectures. For the PNaCl toolchain 145 contain .nexe files for all target architectures. For the PNaCl toolchain
146 they contain a single .pexe file. PNaCl debug also produces pre-translated 146 they contain a single .pexe file. PNaCl debug also produces pre-translated
147 .nexe files, for ease of debugging. All Debug and Release directories contain 147 .nexe files, for ease of debugging. All Debug and Release directories contain
148 a manifest (.nmf) file that references the associated .nexe or .pexe files. 148 a manifest (.nmf) file that references the associated .nexe or .pexe files.
149 For information about Native Client manifest files, see the :doc:`Technical 149 For information about Native Client manifest files, see the :doc:`Technical
150 Overview <../overview>`. 150 Overview <../overview>`.
151 151
152 For details on how to use ``make``, see the `GNU 'make' Manual 152 For details on how to use ``make``, see the `GNU 'make' Manual
153 <http://www.gnu.org/software/make/manual/make.html>`_. For details on how to 153 <http://www.gnu.org/software/make/manual/make.html>`_. For details on how to
154 use the SDK toolchain itself, see :doc:`Building Native Client Modules 154 use the SDK toolchain itself, see :doc:`Building Native Client Modules
155 <devcycle/building>`. 155 <../devguide/devcycle/building>`.
156 156
157 Run the SDK examples 157 Run the SDK examples
158 -------------------- 158 --------------------
159 159
160 To run the SDK examples, you can use the ``make run`` command:: 160 To run the SDK examples, you can use the ``make run`` command::
161 161
162 $ cd pepper_28/examples/api/core 162 $ cd pepper_28/examples/api/core
163 $ make run 163 $ make run
164 164
165 This will launch a local HTTP server which will serve the data for the 165 This will launch a local HTTP server which will serve the data for the
(...skipping 68 matching lines...) Expand 10 before | Expand all | Expand 10 after
234 234
235 This tells GDB to connect to a TCP port on localhost:4014--the port that 235 This tells GDB to connect to a TCP port on localhost:4014--the port that
236 Chrome is listening on. GDB will respond:: 236 Chrome is listening on. GDB will respond::
237 237
238 Remote debugging using :4014 238 Remote debugging using :4014
239 0x000000000fa00080 in ?? () 239 0x000000000fa00080 in ?? ()
240 240
241 At this point, you can use the standard GDB commands to debug your NaCl module. 241 At this point, you can use the standard GDB commands to debug your NaCl module.
242 The most common commands you will use to debug are ``continue``, ``step``, 242 The most common commands you will use to debug are ``continue``, ``step``,
243 ``next``, ``break`` and ``backtrace``. See :doc:`Debugging 243 ``next``, ``break`` and ``backtrace``. See :doc:`Debugging
244 <devcycle/debugging>` for more information about debugging a Native Client 244 <../devguide/devcycle/debugging>` for more information about debugging a Native Client
245 application. 245 application.
246 246
247 247
248 .. |menu-icon| image:: /images/menu-icon.png 248 .. |menu-icon| image:: /images/menu-icon.png
249 .. |gear-icon| image:: /images/gear-icon.png 249 .. |gear-icon| image:: /images/gear-icon.png
OLDNEW
« no previous file with comments | « native_client_sdk/src/doc/rest-devsite-examples.rst ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698