CINXE.COM

<!DOCTYPE html> <html class="writer-html5" lang="en"> <head> <meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>About this site — Emscripten 4.0.0-git (dev) documentation</title> <link rel="stylesheet" type="text/css" href="../../_static/pygments.css?v=fa44fd50" /> <link rel="stylesheet" type="text/css" href="../../_static/css/theme.css?v=6895f958" /> <link rel="shortcut icon" href="../../_static/emscripten.ico"/> <script src="../../_static/jquery.js?v=5d32c60e"></script> <script src="../../_static/_sphinx_javascript_frameworks_compat.js?v=2cd50e6c"></script> <script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=faf469f6"></script> <script src="../../_static/doctools.js?v=888ff710"></script> <script src="../../_static/sphinx_highlight.js?v=4825356b"></script> <script src="../../_static/js/theme.js"></script> <link rel="index" title="Index" href="../../genindex.html" /> <link rel="search" title="Search" href="../../search.html" /> <link rel="prev" title="Profiling the Toolchain" href="../optimizing/Profiling-Toolchain.html" /> </head> <body class="wy-body-for-nav"> <div class="grid-to-center-rtd-theme"> <div class="wy-grid-for-nav"> <nav data-toggle="wy-nav-shift" class="wy-nav-side"> <div class="wy-side-scroll"> <div class="wy-side-nav-search" > <a href="../../index.html">  <img src="../../_static/Emscripten_logo_full.png" class="logo" alt="Logo"/> </a> <div role="search"> <form id="rtd-search-form" class="wy-form" action="../../search.html" method="get"> <input type="text" name="q" placeholder="Search docs" aria-label="Search docs" /> <input type="hidden" name="check_keywords" value="yes" /> <input type="hidden" name="area" value="default" /> </form> </div> </div><div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="Navigation menu"> <ul class="current"> <li class="toctree-l1"><a class="reference internal" href="../introducing_emscripten/index.html">Introducing Emscripten</a></li> <li class="toctree-l1"><a class="reference internal" href="../getting_started/index.html">Getting Started</a></li> <li class="toctree-l1"><a class="reference internal" href="../compiling/index.html">Compiling and Running Projects</a></li> <li class="toctree-l1"><a class="reference internal" href="../porting/index.html">Porting</a></li> <li class="toctree-l1"><a class="reference internal" href="../api_reference/index.html">API Reference</a></li> <li class="toctree-l1"><a class="reference internal" href="../tools_reference/index.html">Tools Reference</a></li> <li class="toctree-l1"><a class="reference internal" href="../optimizing/Optimizing-Code.html">Optimizing Code</a></li> <li class="toctree-l1"><a class="reference internal" href="../optimizing/Optimizing-WebGL.html">Optimizing WebGL</a></li> <li class="toctree-l1"><a class="reference internal" href="../debugging/Sanitizers.html">Debugging with Sanitizers</a></li> <li class="toctree-l1"><a class="reference internal" href="../building_from_source/index.html">Building Emscripten from Source</a></li> <li class="toctree-l1"><a class="reference internal" href="../contributing/index.html">Contributing to Emscripten</a></li> <li class="toctree-l1"><a class="reference internal" href="../optimizing/Profiling-Toolchain.html">Profiling the Toolchain</a></li> <li class="toctree-l1 current"><a class="current reference internal" href="#">About this site</a><ul> <li class="toctree-l2"><a class="reference internal" href="#searching-the-site">Searching the site</a></li> <li class="toctree-l2"><a class="reference internal" href="#reporting-bugs">Reporting bugs</a></li> <li class="toctree-l2"><a class="reference internal" href="#contributing-to-the-site">Contributing to the site</a></li> <li class="toctree-l2"><a class="reference internal" href="#building-the-site">Building the site</a><ul> <li class="toctree-l3"><a class="reference internal" href="#installing-sphinx">Installing Sphinx</a></li> <li class="toctree-l3"><a class="reference internal" href="#site-builds">Site builds</a></li> <li class="toctree-l3"><a class="reference internal" href="#sdk-builds">SDK Builds</a></li> <li class="toctree-l3"><a class="reference internal" href="#build-version">Build version</a></li> </ul> </li> <li class="toctree-l2"><a class="reference internal" href="#writing-and-updating-articles">Writing and updating articles</a><ul> <li class="toctree-l3"><a class="reference internal" href="#style-guide">Style guide</a></li> <li class="toctree-l3"><a class="reference internal" href="#how-to-link-to-a-document-or-heading">How to link to a document or heading</a></li> <li class="toctree-l3"><a class="reference internal" href="#recommended-section-heading-markup">Recommended section/heading markup</a></li> <li class="toctree-l3"><a class="reference internal" href="#working-in-markdown">Working in markdown</a></li> </ul> </li> <li class="toctree-l2"><a class="reference internal" href="#read-the-docs-theme">Read the docs theme</a></li> <li class="toctree-l2"><a class="reference internal" href="#site-license">Site license</a></li> </ul> </li> <li class="toctree-l1"><a class="reference internal" href="../../genindex.html">Index</a></li> </ul> </div> </div> </nav> <section data-toggle="wy-nav-shift" class="wy-nav-content-wrap"><nav class="wy-nav-top" aria-label="Mobile navigation menu" > <i data-toggle="wy-nav-top" class="fa fa-bars"></i>  <a href="../../index.html"> <img src="../../_static/Emscripten_logo_full.png" alt="Logo" /> </a> </nav> <div class="wy-nav-content"> <div class="rst-content">   <a href="https://github.com/emscripten-core/emscripten"><img style="position: absolute; top: 0; right: 0; border: 0;" src="https://github.blog/wp-content/uploads/2008/12/forkme_right_darkblue_121621.png" alt="Fork me on GitHub" data-canonical-src="https://github.blog/wp-content/uploads/2008/12/forkme_right_darkblue_121621.png"></a> <div class="main-nav-bar" style="">  <ul id="menu-options"> <li style="text-align:left;"><a class="navlink-short" title="Docs" href="../index.html">Docs</a><a class="navlink-long" title="Documentation" href="../index.html">Documentation</a></li> <li><a class="navlink-short" title="SDK" href="../getting_started/downloads.html">SDK</a><a class="navlink-long" title="Downloads" href="../getting_started/downloads.html">Downloads</a></li> <li><a class="navlink-short" title="Help" href="../introducing_emscripten/community.html">Help</a><a class="navlink-long" title="Community" href="../introducing_emscripten/community.html">Community</a></li> <li style="text-align:right;"><a class="navlink-short" title="GitHub" href="../index.html">GitHub</a><a class="navlink-long" title="" href="../index.html"></a></li> </ul>  <div role="navigation" aria-label="breadcrumbs navigation"> <div class="breadcrumb-box"> <a class="breadcrumb-box-item" href="../../index.html">Home</a> <div class="breadcrumb-box-item">» About this site</div> </div> </div> </div>   <div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article"> <div itemprop="articleBody"> <section id="about-this-site"> <span id="id1"></span><h1>About this site<a class="headerlink" href="#about-this-site" title="Permalink to this heading"></a></h1> <p>The site is built using <a class="reference external" href="https://www.sphinx-doc.org/en/master/">Sphinx</a> (7.1.2), the open source tool used to create the official Python documentation and many other sites. This is a very mature and stable tool, and was selected for, among other reasons, its support for defining API items and linking to them from code.</p> <p>The site uses a custom theme, which is based on the <a class="reference internal" href="#read-the-docs-theme"><span class="std std-ref">Read the docs theme</span></a>.</p> <section id="searching-the-site"> <span id="about-this-site-search"></span><h2>Searching the site<a class="headerlink" href="#searching-the-site" title="Permalink to this heading"></a></h2> <p>Searching returns topics that contain <strong>all</strong> the specified keywords.</p> <div class="admonition tip"> <p class="admonition-title">Tip</p> <p>Always start by searching for <em>single</em> words like “interacting” or “compiling”. Generally this will be enough to find the relevant document. If not, you can refine the search by adding additional terms.</p> </div> <div class="admonition note"> <p class="admonition-title">Note</p> <p>Searches that include characters like “-” and “+” will not work. There is no support for logical operators.</p> </div> </section> <section id="reporting-bugs"> <h2>Reporting bugs<a class="headerlink" href="#reporting-bugs" title="Permalink to this heading"></a></h2> <p>Please <a class="reference internal" href="../getting_started/bug_reports.html#site-and-documentation-bug-reports"><span class="std std-ref">report documentation bugs</span></a> as you would any other Emscripten bug. Help <a class="reference internal" href="#writing-and-updating-articles"><span class="std std-ref">fix them</span></a> by updating existing documents or by creating new ones.</p> </section> <section id="contributing-to-the-site"> <span id="about-this-site-contributing"></span><h2>Contributing to the site<a class="headerlink" href="#contributing-to-the-site" title="Permalink to this heading"></a></h2> <p><a class="reference internal" href="../contributing/contributing.html#contributing"><span class="std std-ref">Contributions</span></a> to this site (and indeed any part of Emscripten) are welcome!</p> <p>Check out the rest of this article for instructions on how to <a class="reference internal" href="#building-the-site"><span class="std std-ref">build the site</span></a> and <a class="reference internal" href="#writing-and-updating-articles"><span class="std std-ref">write and update articles</span></a>.</p> </section> <section id="building-the-site"> <span id="id2"></span><h2>Building the site<a class="headerlink" href="#building-the-site" title="Permalink to this heading"></a></h2> <p>The site sources are stored on <a class="reference external" href="https://github.com/emscripten-core/emscripten/tree/main/site">GitHub</a>. Edits and additions should be submitted to this branch in the same way as any other change to the tool.</p> <p>The site is published to the <strong>emscripten-core/emscripten-site</strong> <em>gh-pages</em> branch (GitHub pages).</p> <div class="admonition note"> <p class="admonition-title">Note</p> <p>Remember to update the <a class="reference internal" href="#about-build-versions"><span class="std std-ref">Build version</span></a> for <em>public</em> builds.</p> </div> <section id="installing-sphinx"> <h3>Installing Sphinx<a class="headerlink" href="#installing-sphinx" title="Permalink to this heading"></a></h3> <p>This site requires a specific version of Sphinx to be installed. Run the following command to ensure you have the correct version installed:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">pip</span> <span class="n">install</span> <span class="o">-</span><span class="n">r</span> <span class="n">requirements</span><span class="o">-</span><span class="n">dev</span><span class="o">.</span><span class="n">txt</span> </pre></div> </div> </section> <section id="site-builds"> <span id="about-site-builds"></span><h3>Site builds<a class="headerlink" href="#site-builds" title="Permalink to this heading"></a></h3> <p>The site can be built from source on Ubuntu and Windows by navigating to the <em>/emscripten/site</em> directory and using the command:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">make</span> <span class="n">clean</span> <span class="n">make</span> <span class="n">html</span> </pre></div> </div> </section> <section id="sdk-builds"> <span id="about-sdk-builds"></span><h3>SDK Builds<a class="headerlink" href="#sdk-builds" title="Permalink to this heading"></a></h3> <p>SDK builds are virtually identical to <a class="reference internal" href="#about-site-builds"><span class="std std-ref">Site builds</span></a>. The main difference is that on SDK builds the <a class="reference internal" href="../../index.html#home-page"><span class="std std-ref">home page</span></a> has a clear notification that it is an SDK build.</p> <p>SDK builds are enabled by enabling the <code class="docutils literal notranslate"><span class="pre">sdkbuild</span></code> tag. This is done through the <code class="docutils literal notranslate"><span class="pre">SPHINXOPTS</span></code> environment variable:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="c1"># Set the sdkbuild tag.</span> <span class="nb">set</span> <span class="n">SPHINXOPTS</span><span class="o">=-</span><span class="n">t</span> <span class="n">sdkbuild</span> <span class="n">make</span> <span class="n">html</span> <span class="c1"># Unset SPHINXOPTS</span> <span class="nb">set</span> <span class="n">SPHINXOPTS</span><span class="o">=</span> </pre></div> </div> </section> <section id="build-version"> <span id="about-build-versions"></span><h3>Build version<a class="headerlink" href="#build-version" title="Permalink to this heading"></a></h3> <p>The documentation version should match the Emscripten version for the current build. For a general site build this will be the latest tagged release as defined in <a class="reference external" href="https://github.com/emscripten-core/emscripten/blob/main/emscripten-version.txt">Emscripten version</a>. For an SDK build it will be the Emscripten version for the SDK.</p> <p>The version and release information is used in a few places in the documentation, for example <a class="reference internal" href="../contributing/AUTHORS.html#emscripten-authors"><span class="std std-ref">AUTHORS</span></a>.</p> <p>The version information is defined in <strong>conf.py</strong> — see variables <code class="docutils literal notranslate"><span class="pre">version</span></code> and <code class="docutils literal notranslate"><span class="pre">release</span></code>. These variables can be overridden by setting new values in the <code class="docutils literal notranslate"><span class="pre">SPHINXOPTS</span></code> environment variable. For example, to update the <code class="docutils literal notranslate"><span class="pre">release</span></code> variable through the command line on Windows:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="c1"># Set SPHINXOPTS</span> <span class="nb">set</span> <span class="n">SPHINXOPTS</span><span class="o">=-</span><span class="n">D</span> <span class="n">release</span><span class="o">=</span><span class="mf">6.40</span> <span class="n">make</span> <span class="n">html</span> <span class="c1"># Unset SPHINXOPTS</span> <span class="nb">set</span> <span class="n">SPHINXOPTS</span><span class="o">=</span> </pre></div> </div> </section> </section> <section id="writing-and-updating-articles"> <span id="id3"></span><h2>Writing and updating articles<a class="headerlink" href="#writing-and-updating-articles" title="Permalink to this heading"></a></h2> <div class="admonition note"> <p class="admonition-title">Note</p> <p>Sphinx is <a class="reference external" href="http://sphinx-doc.org/latest/index.html">well documented</a>. This section only attempts to highlight specific styles and features used on this site.</p> <p>The <a class="reference internal" href="#building-the-site"><span class="std std-ref">Building the site</span></a> section explains how to find the sources for articles and build the site.</p> </div> <p>Site content is written using <a class="reference internal" href="glossary.html#term-reStructured-text"><span class="xref std std-term">reStructured text</span></a>. We recommend you read the following articles to understand the syntax:</p> <ul class="simple"> <li><p><a class="reference external" href="http://sphinx-doc.org/rest.html">reStructured text primer</a>.</p></li> <li><p><a class="reference external" href="http://sphinx-doc.org/domains.html">Sphinx Domains</a> (define and link to code items).</p></li> <li><p><a class="reference external" href="http://sphinx-doc.org/markup/inline.html">Inline markup</a>.</p></li> </ul> <section id="style-guide"> <h3>Style guide<a class="headerlink" href="#style-guide" title="Permalink to this heading"></a></h3> <p>This section has a few very brief recommendations to help authors use common style.</p> <div class="admonition tip"> <p class="admonition-title">Tip</p> <p>In terms of contributions, we value your coding and content writing far more than perfect prose! Just do your best, and then <a class="reference internal" href="../introducing_emscripten/community.html#contact"><span class="std std-ref">ask for editorial review</span></a>.</p> </div> <p><strong>Spelling:</strong> Where possible use US-English spelling.</p> <p><strong>Avoid idiomatic expressions</strong>: These can be particularly confusing to non-native speakers (for example “putting your foot in your mouth” actually means “saying something embarrassing”).</p> <p><strong>Emphasis:</strong></p> <blockquote> <div><ul class="simple"> <li><p><strong>Bold</strong> : use for file names, and UI/menu instructions (for example: “Press <strong>OK</strong> to do something”).</p></li> <li><p><em>Italic</em> : use for tool names - e.g. <em>Clang</em>, <em>emcc</em>, <em>Closure Compiler</em>.</p></li> <li><p><code class="docutils literal notranslate"><span class="pre">monotype</span></code> : use for inline code (where you can’t link to the API reference) and for demonstrating tool command line options.</p></li> </ul> <div class="admonition note"> <p class="admonition-title">Note</p> <p>Other than the above rules, emphasis should be used sparingly.</p> </div> </div></blockquote> <p><strong>Lists</strong>: Use a colon on the lead-in to the list where appropriate. Capitalize the first letter and use a full-stop for each item.</p> </section> <section id="how-to-link-to-a-document-or-heading"> <h3>How to link to a document or heading<a class="headerlink" href="#how-to-link-to-a-document-or-heading" title="Permalink to this heading"></a></h3> <p>To link to a page, first define a globally unique reference before the page title (e.g. <code class="docutils literal notranslate"><span class="pre">_my-page-reference</span></code>) then link to it using the <a class="reference external" href="http://sphinx-doc.org/markup/inline.html#ref-role">ref</a> role as shown:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span>.. _my-page-reference: My Page Title ============= This is the text of the section. To link to page use either of the options below: ref:`my-reference-label` - the link text is the heading name after the reference ref:`some text <my-reference-label>` - the link text is "some text" </pre></div> </div> <p>This is a better approach than linking to documents using the <em>:doc:</em> role, because the links do not get broken if the articles are moved.</p> <p>This approach is also recommended for linking to arbitrary headings in the site.</p> <div class="admonition note"> <p class="admonition-title">Note</p> <p>There are a number of other roles that are useful for linking — including <a class="reference external" href="http://sphinx-doc.org/domains.html">Sphinx Domains</a> for linking to code items, and <strong>term</strong> for linking to glossary terms.</p> </div> </section> <section id="recommended-section-heading-markup"> <h3>Recommended section/heading markup<a class="headerlink" href="#recommended-section-heading-markup" title="Permalink to this heading"></a></h3> <p>reStructured text <a class="reference external" href="http://sphinx-doc.org/rest.html#sections">defines</a> section headings using a separate line of punctuation characters after (and optionally before) the heading text. The line of characters must be at least as long as the heading. For example:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">A</span> <span class="n">heading</span> <span class="o">=========</span> </pre></div> </div> <p>Different punctuation characters are used to specify nested sections. Although the system does not mandate which punctuation character is used for each nested level, it is important to be consistent. The recommended heading levels are:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="o">=======================================</span> <span class="n">Page</span> <span class="n">title</span> <span class="p">(</span><span class="n">top</span> <span class="ow">and</span> <span class="n">bottom</span> <span class="n">bars</span> <span class="n">of</span> <span class="s2">"="</span><span class="p">)</span> <span class="o">=======================================</span> <span class="n">Level</span> <span class="mi">1</span> <span class="n">heading</span> <span class="p">(</span><span class="n">single</span> <span class="n">bar</span> <span class="n">of</span> <span class="s2">"="</span> <span class="n">below</span><span class="p">)</span> <span class="o">=========================================</span> <span class="n">Level</span> <span class="mi">2</span> <span class="n">heading</span> <span class="p">(</span><span class="n">single</span> <span class="n">bar</span> <span class="n">of</span> <span class="s2">"-"</span> <span class="n">below</span><span class="p">)</span> <span class="o">-----------------------------------------</span> <span class="n">Level</span> <span class="mi">3</span> <span class="n">heading</span> <span class="p">(</span><span class="n">single</span> <span class="n">bar</span> <span class="n">of</span> <span class="s2">"+"</span> <span class="n">below</span><span class="p">)</span> <span class="o">+++++++++++++++++++++++++++++++++++++++++</span> <span class="n">Level</span> <span class="mi">4</span> <span class="n">heading</span> <span class="p">(</span><span class="n">single</span> <span class="n">bar</span> <span class="n">of</span> <span class="s2">"~"</span> <span class="n">below</span><span class="p">)</span> <span class="o">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</span> </pre></div> </div> </section> <section id="working-in-markdown"> <h3>Working in markdown<a class="headerlink" href="#working-in-markdown" title="Permalink to this heading"></a></h3> <p>New articles may be authored and discussed on the <a class="reference external" href="https://github.com/emscripten-core/emscripten/wiki">wiki</a> using Markdown syntax before being included in the documentation set. The easiest way to convert these to restructured text is to use a tool like <a class="reference external" href="http://johnmacfarlane.net/pandoc/try/?text=&from=markdown_github&to=rst">Pandoc</a>.</p> <div class="admonition note"> <p class="admonition-title">Note</p> <p>The <em>get_wiki.py</em> tool (<strong>/site/source/get_wiki.py</strong>) can be used to automate getting a snapshot of the wiki. It clones the wiki and calls <em>pandoc</em> on each file. The output is copied to a folder <strong>wiki_static</strong>. The tool also adds a heading, a note stating that the file is a “wiki snapshot”, and fixes up links marked as “inline code” to matching links in the API Reference.</p> </div> </section> </section> <section id="read-the-docs-theme"> <span id="id5"></span><h2>Read the docs theme<a class="headerlink" href="#read-the-docs-theme" title="Permalink to this heading"></a></h2> <p>The site uses a modification of the <a class="reference external" href="http://read-the-docs.readthedocs.org/en/latest/theme.html">Read the docs theme</a> (this can be found in the source at <em>/emscripten/site/source/_themes/emscripten_sphinx_rtd_theme</em>).</p> <p>The main changes to the original theme are listed below.</p> <ul class="simple"> <li><p><strong>Footer.html</strong></p> <ul> <li><p>Copyright changed to link to Emscripten authors (some code was broken by translation markup)</p></li> <li><p>Added footer menu bar</p></li> </ul> </li> <li><p><strong>Layout.html</strong></p> <ul> <li><p>Added header menu bar with items</p></li> </ul> </li> <li><p><strong>Breadcrumb.html</strong></p> <ul> <li><p>Changed the text of the first link from “docs” to “Home”</p></li> <li><p>Moved the “View Page Source” code into the bottom footer</p></li> </ul> </li> <li><p><strong>theme.css</strong></p> <ul> <li><p>Changed to support 4 levels of depth in sidebar toc.</p></li> <li><p>Centred theme. Made sidebar reach bottom of page using absolute positioning.</p></li> </ul> </li> </ul> </section> <section id="site-license"> <h2>Site license<a class="headerlink" href="#site-license" title="Permalink to this heading"></a></h2> <p>The site is licensed under the same <a class="reference internal" href="../introducing_emscripten/emscripten_license.html#emscripten-license"><span class="std std-ref">Open Source License</span></a> as the rest of Emscripten. Contributors to the site should add themselves to <a class="reference internal" href="../contributing/AUTHORS.html#emscripten-authors"><span class="std std-ref">AUTHORS</span></a>.</p> </section> </section> </div> </div> <footer> <div class="rst-footer-buttons" role="navigation" aria-label="footer navigation"> <a href="../optimizing/Profiling-Toolchain.html" class="btn btn-neutral" title="Profiling the Toolchain"><span class="fa fa-arrow-circle-left"></span> Previous</a> </div>    <div class="footer-nav-bar" style=""> <div class="footer-options"> <a class="footer-navlink-short" title="Report Bug" href="../getting_started/bug_reports.html">Report Bug</a><a class="footer-navlink-long" title="Report Bug" href="../getting_started/bug_reports.html">Report Bug</a> <a class="footer-navlink-short" title="Licensing" href="../introducing_emscripten/emscripten_license.html">Licensing</a><a class="footer-navlink-long" title="Licensing" href="../introducing_emscripten/emscripten_license.html">Licensing</a> <a class="footer-navlink-short" title="Contributing" href="../contributing/contributing.html">Contributing</a><a class="footer-navlink-long" title="Contributing" href="../contributing/contributing.html">Contributing</a> <a class="footer-navlink-short external" href="https://groups.google.com/forum/#!forum/emscripten-discuss">Mailing list</a><a class="footer-navlink-long external" href="https://groups.google.com/forum/#!forum/emscripten-discuss">Mailing list</a> <a class="footer-navlink-short external" href="https://github.com/emscripten-core/emscripten/wiki">Wiki</a><a class="footer-navlink-long external" href="https://github.com/emscripten-core/emscripten/wiki">Wiki</a> <a class="footer-navlink-short" title="Release notes" href="../introducing_emscripten/release_notes.html">Release notes</a><a class="footer-navlink-long" title="Release notes" href="../introducing_emscripten/release_notes.html">Release notes</a> <a class="footer-navlink-short" title="Blogs" href="../introducing_emscripten/community.html">Blogs</a><a class="footer-navlink-long" title="Blogs" href="../introducing_emscripten/community.html">Blogs</a> <a class="footer-navlink-short" title="Help" href="../introducing_emscripten/community.html">Help</a><a class="footer-navlink-long" title="Contact" href="../introducing_emscripten/community.html">Contact</a> </div> </div>    <div role="contentinfo" class="copyright-box">  <ul class="wy-breadcrumbs"> <li class="wy-breadcrumbs-aside"> </li> <li class="wy-breadcrumbs-aside"> <a href="#">About site</a> </li> <li class="wy-breadcrumbs-aside"> <a href="https://github.com/emscripten-core/emscripten/issues/new?title=Bug%20in%20page:About%20this%20site%20&body=REPLACE%20THIS%20TEXT%20WITH%20BUG%20DESCRIPTION%20%0A%0AURL:%20../../docs/site/about&labels=bug">Page bug</a> </li> </ul> <p>  © Copyright 2015, <a href="../contributing/AUTHORS.html">Emscripten Contributors</a>.  </p> </div> </footer> </div> </div> </section> </div> <script> jQuery(function () { SphinxRtdTheme.Navigation.enable(true); }); </script> </div> </body> </html>