Lines Matching +full:build +full:- +full:docs
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
3 <!-- Material used from: HTML 4.01 specs: http://www.w3.org/TR/html401/ -->
6 <META http-equiv="Content-Type" content="text/html; charset=utf-8">
11 pre { margin-left: 1.5em; }
15 <!--#include virtual="menu.html.incl"-->
17 <!--*********************************************************************-->
19 <!--*********************************************************************-->
26 <li><a href="#docs">Developer Documentation</a></li>
30 <li><a href="#testingNonWindows">Testing on Unix-like Systems</a></li>
40 <!--=====================================================================-->
42 <!--=====================================================================-->
45 LLVM <a href="https://llvm.org/docs/CodingStandards.html">Coding
57 output. See <a href="https://llvm.org/docs/CodingStandards.html#use-raw-ostream">Coding
61 <!--=====================================================================-->
62 <h2 id="docs">Developer Documentation</h2>
63 <!--=====================================================================-->
73 <a href="https://llvm.org/docs/LangRef.html">reference manual</a> is
76 <!--=====================================================================-->
78 <!--=====================================================================-->
85 <li>The <a href="docs/InternalsManual.html#QualType"><tt>QualType</tt></a>
93 <a href="https://github.com/llvm/llvm-project/blob/main/llvm/utils/lldbDataFormatters.py">
97 <!--=====================================================================-->
99 <!--=====================================================================-->
102 <a href="https://github.com/llvm/llvm-project/blob/main/llvm/utils/LLVMVisualizers/llvm.natvis">
104 <a href="https://github.com/llvm/llvm-project/blob/main/clang/utils/ClangVisualizers/clang.natvis">
111 <a href="https://learn.microsoft.com/en-us/visualstudio/debugger/create-custom-views-of-native-objects">
114 <!--=====================================================================-->
116 <!--=====================================================================-->
118 <!--=====================================================================-->
119 <h3 id="testingNonWindows">Testing on Unix-like Systems</h3>
120 <!--=====================================================================-->
123 run with <tt>make test</tt> from the top-level clang directory, or
124 just <tt>make</tt> in the <em>test</em> sub-directory.
129 with <tt>make check-clang</tt> from the top-level LLVM directory.</p>
143 <pre>--- Running clang tests for i686-pc-linux-gnu ---</pre>
156 /home/john/llvm/tools/clang/test/SemaCXX/member-name-lookup.cpp
157 /home/john/llvm/tools/clang/test/SemaCXX/namespace-alias.cpp
158 /home/john/llvm/tools/clang/test/SemaCXX/using-directive.cpp
166 <tt>make test VG=1</tt> in the top-level clang directory.</p>
169 the <a href="https://llvm.org/docs/TestingGuide.html#quick-start">LLVM
171 override LLVMGCC, as in: <tt>make LLVMGCC="clang -std=gnu89"
175 <!--=====================================================================-->
177 <!--=====================================================================-->
195 <p>The cmake build tool is set up to create Visual Studio project files
196 for running the tests, "check-clang" being the root. Therefore, to
197 run the test from Visual Studio, right-click the check-clang project
198 and select "Build".</p>
202 <a href="https://llvm.org/docs/GettingStartedVS.html">Getting Started
204 <a href="https://llvm.org/docs/CMake.html">Building LLVM with CMake</a>.
207 <!--=====================================================================-->
209 <!--=====================================================================-->
212 be convenient to run the test harness on the command-line directly. Before
214 <tt>lit.site.cfg</tt> files have been created for your build. You can do
223 python (path to llvm)\llvm\utils\lit\lit.py -sv
224 --param=build_mode=Win32 --param=build_config=Debug
225 --param=clang_site_config=(build dir)\tools\clang\test\lit.site.cfg
230 to specify your build configuration (Debug, Release, etc.) via
231 <tt>--param=build_config=(build config)</tt>. You may also need to specify
232 the build mode (Win32, etc) via <tt>--param=build_mode=(build mode)</tt>.</p>
235 lives in (build dir)\tools\clang\test, via
236 <tt>--param=clang_site_config=(build dir)\tools\clang\test\lit.site.cfg</tt>.
242 python (path to llvm)\llvm\utils\lit\lit.py -sv
243 --param=build_mode=Win32 --param=build_config=Debug
244 --param=clang_site_config=(build dir)\tools\clang\test\lit.site.cfg
251 python C:\Tools\llvm\utils\lit\lit.py -sv
252 --param=build_mode=Win32 --param=build_config=Debug
253 --param=clang_site_config=C:\Tools\build\tools\clang\test\lit.site.cfg
257 <p>The -sv option above tells the runner to show the test output if
260 <p>You can also pass in the --no-progress-bar option if you wish to disable
266 -- Testing: Testing: 2534 tests, 4 threads --
276 <!--=====================================================================-->
278 <!--=====================================================================-->
291 <a href="https://buildkite.com/llvm-project/libcxx-ci">pre-commit CI</a>.
293 <p>For most configurations, the pre-commit CI uses a recent
294 <a href="https://apt.llvm.org/">nightly build</a> of Clang from LLVM's main
298 <p>The "Bootstrapping build" builds Clang and uses it to build and
299 test libc++. This build <em>does</em> use the Clang changes in the patch.</p>
306 <a href="https://libcxx.llvm.org/Contributing.html#pre-commit-ci">
307 documentation</a> about the pre-commit CI. For questions regarding
311 <!--=====================================================================-->
313 <!--=====================================================================-->
316 <a href="https://llvm.org/docs/GettingStarted.html#sending-patches">LLVM's Getting Started page</a></p>
318 <!--=====================================================================-->
320 <!--=====================================================================-->
328 <p>The output is most easily inspected using the <tt>-emit-llvm</tt>
329 option to clang (possibly in conjunction with <tt>-o -</tt>). You
330 can also use <tt>-emit-llvm-bc</tt> to write an LLVM bitcode file
332 like <tt>llvm-dis</tt>, <tt>llvm-nm</tt>, etc. See the LLVM
333 <a href="https://llvm.org/docs/CommandGuide/">Command Guide</a>