<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Bazel (software) - Page 9 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Bazel_(software)&amp;p=8">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Bazel_%28software%29&amp;p=10">3.Next</a>
</p>
<p>for compilation steps. When Bazel performs a separate compilation, it creates a new directory and fills it with symlinks to the explicit input dependencies for the rule. For languages like C or C++, this requires the user to be explicit about the dependencies and it prevents the unexpected inclusion of a similarly named header file from another including directory.</p>

<p>This sandbox approach leads to issues with common build tools, resulting in a number of workarounds required to correctly compile code under different architectures. For example,</p><p>
<a accesskey="1" href="page.php?w=Bazel_(software)&amp;p=8">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Bazel_%28software%29&amp;p=10">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
