From: <le...@us...> - 2012-08-17 17:22:55
|
Revision: 13644 http://swig.svn.sourceforge.net/swig/?rev=13644&view=rev Author: leiflm Date: 2012-08-17 17:22:48 +0000 (Fri, 17 Aug 2012) Log Message: ----------- Change style of command line snippets to "shell" Modified Paths: -------------- branches/gsoc2012-c/Doc/Manual/C.html Modified: branches/gsoc2012-c/Doc/Manual/C.html =================================================================== --- branches/gsoc2012-c/Doc/Manual/C.html 2012-08-17 17:22:38 UTC (rev 13643) +++ branches/gsoc2012-c/Doc/Manual/C.html 2012-08-17 17:22:48 UTC (rev 13644) @@ -84,7 +84,7 @@ <p> To build a C module (C as the target language), run SWIG using the <tt>-c</tt> option :</p> -<div class="code"><pre> +<div class="shell"><pre> %swig -c example.i </pre></div> @@ -92,7 +92,7 @@ The above assumes C as the input language. If the input language is C++ add the <tt>-c++</tt> option: </p> -<div class="code"><pre> +<div class="shell"><pre> $ swig -c++ -c example.i </pre></div> @@ -115,7 +115,7 @@ The following table list the additional commandline options available for the C module. They can also be seen by using: </p> -<div class="code"><pre> +<div class="shell"><pre> swig -c -help </pre></div> @@ -143,7 +143,7 @@ The next step is to build a dynamically loadable module, which we can link to our application. This can be done easily, for example using the <tt>gcc</tt> compiler (Linux, MinGW, etc.): </p> -<div class="code"><pre> +<div class="shell"><pre> $ swig -c example.i $ gcc -c example_wrap.c $ gcc -c example_proxy.c @@ -154,7 +154,7 @@ Or, for C++ input: </p> -<div class="code"><pre> +<div class="shell"><pre> $ swig -c++ -c example.i $ g++ -c example_wrap.cxx $ gcc -c example_proxy.c @@ -172,7 +172,7 @@ The simplest way to use the generated shared module is to link it to the application code during the compilation stage. We have to compile the proxy file as well. The process is usually similar to this: </p> -<div class="code"><pre> +<div class="shell"><pre> $ gcc runme.c -L. -lexample -o runme </pre></div> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |