Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / libcxx / 35d775d0e49a70207e0896ae7930e79b9b100336 / . / www / index.html
blob: c1f3aa56e288b3005737e86c902fef69fab0f281 [file] [log] [blame]
Howard Hinnantd2bb0322010-08-22 01:04:38 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]2 "http://www.w3.org/TR/html4/strict.dtd">
3<!-- Material used from: HTML 4.01 specs: http://www.w3.org/TR/html401/ -->
4<html>
5<head>
6 <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
7 <title>"libc++" C++ Standard Library</title>
8 <link type="text/css" rel="stylesheet" href="menu.css">
9 <link type="text/css" rel="stylesheet" href="content.css">
10</head>
11
12<body>
13<div id="menu">
14 <div>
15 <a href="http://llvm.org/">LLVM Home</a>
16 </div>
Howard Hinnantd2bb0322010-08-22 01:04:38 +0000[diff] [blame]17
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]18 <div class="submenu">
19 <label>libc++ Info</label>
20 <a href="/index.html">About</a>
21 </div>
22
23 <div class="submenu">
24 <label>Quick Links</label>
Chris Lattnera535ffd2010-05-11 20:53:16 +0000[diff] [blame]25 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">cfe-dev</a>
26 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits">cfe-commits</a>
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]27 <a href="http://llvm.org/bugs/">Bug Reports</a>
Howard Hinnant76e1ffc2010-05-11 20:51:20 +0000[diff] [blame]28 <a href="http://llvm.org/svn/llvm-project/libcxx/trunk/">Browse SVN</a>
29 <a href="http://llvm.org/viewvc/llvm-project/libcxx/trunk/">Browse ViewVC</a>
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]30 </div>
31</div>
32
33<div id="content">
34 <!--*********************************************************************-->
35 <h1>"libc++" C++ Standard Library</h1>
36 <!--*********************************************************************-->
Howard Hinnantd2bb0322010-08-22 01:04:38 +0000[diff] [blame]37
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]38 <p>libc++ is a new implementation of the C++ standard library, targeting
Howard Hinnantaf347342012-07-19 15:57:51 +0000[diff] [blame]39 C++11.</p>
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]40
Chris Lattnerf38bc6e2010-11-16 21:40:19 +0000[diff] [blame]41 <p>All of the code in libc++ is <a
42 href="http://llvm.org/docs/DeveloperPolicy.html#license">dual licensed</a>
43 under the MIT license and the UIUC License (a BSD-like license).</p>
Howard Hinnantd2bb0322010-08-22 01:04:38 +0000[diff] [blame]44
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]45 <!--=====================================================================-->
46 <h2 id="goals">Features and Goals</h2>
47 <!--=====================================================================-->
Howard Hinnantd2bb0322010-08-22 01:04:38 +0000[diff] [blame]48
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]49 <ul>
Howard Hinnantaf347342012-07-19 15:57:51 +0000[diff] [blame]50 <li>Correctness as defined by the C++11 standard.</li>
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]51 <li>Fast execution.</li>
52 <li>Minimal memory use.</li>
53 <li>Fast compile times.</li>
54 <li>ABI compatibility with gcc's libstdc++ for some low-level features
55 such as exception objects, rtti and memory allocation.</li>
56 <li>Extensive unit tests.</li>
57 </ul>
58
59 <!--=====================================================================-->
Marshall Clowfaa17162012-11-14 16:31:15 +0000[diff] [blame]60 <h2 id="why">Why a new C++ Standard Library for C++11?</h2>
Chris Lattner24173b82010-05-12 22:21:15 +0000[diff] [blame]61 <!--=====================================================================-->
Howard Hinnantd2bb0322010-08-22 01:04:38 +0000[diff] [blame]62
Chris Lattner24173b82010-05-12 22:21:15 +0000[diff] [blame]63 <p>After its initial introduction, many people have asked "why start a new
64 library instead of contributing to an existing library?" (like Apache's
65 libstdcxx, GNU's libstdc++, STLport, etc). There are many contributing
66 reasons, but some of the major ones are:</p>
Howard Hinnantd2bb0322010-08-22 01:04:38 +0000[diff] [blame]67
Chris Lattner24173b82010-05-12 22:21:15 +0000[diff] [blame]68 <ul>
69 <li><p>From years of experience (including having implemented the standard
70 library before), we've learned many things about implementing
71 the standard containers which require ABI breakage and fundamental changes
72 to how they are implemented. For example, it is generally accepted that
73 building std::string using the "short string optimization" instead of
74 using Copy On Write (COW) is a superior approach for multicore
Marshall Clowfaa17162012-11-14 16:31:15 +0000[diff] [blame]75 machines (particularly in C++11, which has rvalue references). Breaking
Chris Lattnera5058d92010-05-12 22:30:22 +0000[diff] [blame]76 ABI compatibility with old versions of the library was
Chris Lattner24173b82010-05-12 22:21:15 +0000[diff] [blame]77 determined to be critical to achieving the performance goals of
78 libc++.</p></li>
Howard Hinnantd2bb0322010-08-22 01:04:38 +0000[diff] [blame]79
Chris Lattner24173b82010-05-12 22:21:15 +0000[diff] [blame]80 <li><p>Mainline libstdc++ has switched to GPL3, a license which the developers
81 of libc++ cannot use. libstdc++ 4.2 (the last GPL2 version) could be
Marshall Clowfaa17162012-11-14 16:31:15 +0000[diff] [blame]82 independently extended to support C++11, but this would be a fork of the
Chris Lattnerf3382492010-05-12 22:33:00 +0000[diff] [blame]83 codebase (which is often seen as worse for a project than starting a new
84 independent one). Another problem with libstdc++ is that it is tightly
85 integrated with G++ development, tending to be tied fairly closely to the
86 matching version of G++.</p>
Chris Lattner24173b82010-05-12 22:21:15 +0000[diff] [blame]87 </li>
88
89 <li><p>STLport and the Apache libstdcxx library are two other popular
Marshall Clowfaa17162012-11-14 16:31:15 +0000[diff] [blame]90 candidates, but both lack C++11 support. Our experience (and the
Howard Hinnantaf347342012-07-19 15:57:51 +0000[diff] [blame]91 experience of libstdc++ developers) is that adding support for C++11 (in
Chris Lattner24173b82010-05-12 22:21:15 +0000[diff] [blame]92 particular rvalue references and move-only types) requires changes to
93 almost every class and function, essentially amounting to a rewrite.
Chris Lattnerbfa808e2010-05-12 22:34:21 +0000[diff] [blame]94 Faced with a rewrite, we decided to start from scratch and evaluate every
95 design decision from first principles based on experience.</p>
Howard Hinnantd2bb0322010-08-22 01:04:38 +0000[diff] [blame]96
Chris Lattner24173b82010-05-12 22:21:15 +0000[diff] [blame]97 <p>Further, both projects are apparently abandoned: STLport 5.2.1 was
98 released in Oct'08, and STDCXX 4.2.1 in May'08.</p>
99
100 </ul>
101
102 <!--=====================================================================-->
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]103 <h2 id="requirements">Platform Support</h2>
104 <!--=====================================================================-->
105
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]106 <p>
107 libc++ is known to work on the following platforms, using g++-4.2 and
108 clang (lack of C++11 language support disables some functionality). Note
109 that functionality provided by &lt;atomic&gt; is only functional with
110 clang.
111 </p>
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]112
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]113 <ul>
114 <li>Mac OS X i386</li>
115 <li>Mac OS X x86_64</li>
116 <li>FreeBSD 10+ i386</li>
117 <li>FreeBSD 10+ x86_64</li>
118 <li>FreeBSD 10+ ARM</li>
119 </ul>
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]120
121 <!--=====================================================================-->
122 <h2 id="dir-structure">Current Status</h2>
123 <!--=====================================================================-->
124
Howard Hinnantb0895ff2012-11-27 18:52:32 +0000[diff] [blame]125 <p>libc++ is a 100% complete C++11 implementation on Apple's OS X. </p>
Michael J. Spencerdb8a0302012-12-31 19:34:21 +0000[diff] [blame]126 <p>LLVM and Clang can self host in C++ and C++11 mode with libc++ on Linux.</p>
Marshall Clow874ec672014-04-03 02:38:12 +0000[diff] [blame]127 <p>libc++ is also a 100% complete C++14 implementation. A list of new features and changes for
Marshall Clowe4915d92014-04-03 02:35:29 +0000[diff] [blame]128 C++14 can be found <a href="cxx1y_status.html">here</a>.</p>
Marshall Clowd2f0b5c2014-06-02 23:37:13 +0000[diff] [blame]129 <p>Implementation of the post-c++14 Technical Specifications is in progress. A list of features and
130 the current status of these features can be found <a href="ts1z_status.html">here</a>.</p>
Howard Hinnant0cbb3a12011-09-28 15:44:39 +0000[diff] [blame]131 <p>
Howard Hinnantee7a0bf2012-07-31 21:30:28 +0000[diff] [blame]132 Ports to other platforms are underway. Here are recent test
133 results for <a href="results.Windows.html">Windows</a>
134 and <a href="results.Linux.html">Linux</a>.
Howard Hinnant0cbb3a12011-09-28 15:44:39 +0000[diff] [blame]135 </p>
136
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]137 <!--=====================================================================-->
138 <h2>Get it and get involved!</h2>
139 <!--=====================================================================-->
Howard Hinnantd2bb0322010-08-22 01:04:38 +0000[diff] [blame]140
Howard Hinnant2481cba2011-09-30 16:58:02 +0000[diff] [blame]141 <p>First please review our
142 <a href="http://llvm.org/docs/DeveloperPolicy.html">Developer's Policy</a>.
143
Howard Hinnant704f09b2011-11-17 17:14:16 +0000[diff] [blame]144 <p>
Howard Hinnant22b781b2012-11-06 21:31:37 +0000[diff] [blame]145 On Mac OS 10.7 (Lion) and later, the easiest way to get this library is to install
Howard Hinnant704f09b2011-11-17 17:14:16 +0000[diff] [blame]146 Xcode 4.2 or later. However if you want to install tip-of-trunk from here
Howard Hinnant271a1c02012-04-03 15:08:42 +0000[diff] [blame]147 (getting the bleeding edge), read on. However, be warned that Mac OS
148 10.7 will not boot without a valid copy of <code>libc++.1.dylib</code> in
149 <code>/usr/lib</code>.
Howard Hinnant704f09b2011-11-17 17:14:16 +0000[diff] [blame]150 </p>
151
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]152 <p>To check out the code, use:</p>
153
Howard Hinnant65451f12011-01-27 23:18:19 +0000[diff] [blame]154 <ul>
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]155 <li><code>svn co http://llvm.org/svn/llvm-project/libcxx/trunk libcxx</code></li>
Howard Hinnant65451f12011-01-27 23:18:19 +0000[diff] [blame]156 </ul>
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]157
Howard Hinnant65451f12011-01-27 23:18:19 +0000[diff] [blame]158 <p>
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]159 Note that for an in-tree build, you should check out libcxx to
160 llvm/projects.
Howard Hinnant65451f12011-01-27 23:18:19 +0000[diff] [blame]161 </p>
162
Howard Hinnant65451f12011-01-27 23:18:19 +0000[diff] [blame]163 <p>
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]164 The following instructions are for building libc++ on FreeBSD, Linux, or Mac
165 using <a href="http://libcxxabi.llvm.org/">libc++abi</a> as the C++ ABI
166 library. On Linux, it is also possible to use
167 <a href="#libsupcxx">libsupc++</a> or <a href="#libcxxrt">libcxxrt</a>.
168 </p>
169
170 <p>In-tree build:</p>
171 <ul>
172 <li>Check out libcxx and <a href="http://libcxxabi.llvm.org/">libcxxabi</a>
173 into llvm/projects</li>
174 <li><code>cd llvm</code></li>
175 <li><code>mkdir build &amp;&amp; cd build</code></li>
176 <li><code>cmake .. # Linux may require -DCMAKE_C_COMPILER=clang
177 -DCMAKE_CXX_COMPILER=clang++</code></li>
178 <li><code>make cxx</code></li>
179 </ul>
180
181 <p>Out-of-tree build:</p>
182 <ul>
183 <li>Check out libcxx</li>
184 <li>If not on a Mac, also check out
185 <a href="http://libcxxabi.llvm.org/">libcxxabi</a></li>
186 <li><code>cd libcxx</code></li>
187 <li><code>mkdir build &amp;&amp; cd build</code></li>
188 <li><code>cmake -DLIBCXX_CXX_ABI=libcxxabi
189 -DLIBCXX_LIBCXXABI_INCLUDE_PATHS=path/to/libcxxabi/include
190 -DLIT_EXECUTABLE=path/to/llvm/utils/lit/lit.py .. # Linux may require
191 -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++</code></li>
192 <li><code>make</code></li>
193 </ul>
194
195 <p>To run the tests:</p>
196 <ul>
197 <li><code>make check-libcxx</code></li>
198 </ul>
199
200 <p>If you wish to run a subset of the test suite:</p>
201 <ul>
202 <li><code>cd path/to/libcxx/libcxx</code></li>
203 <li><code>alias lit='python path/to/llvm/utils/lit/lit.py'</code></li>
204 <li><code>ln -s path/to/build/dir/projects/libcxx/test/lit.site.cfg
205 test/lit.site.cfg</code></li>
206 <li><code>lit -sv test/re/ # or whichever subset of tests you're interested
207 in</code></li>
208 </ul>
209 <p>The above is currently quite inconvenient. Sorry! We're working on it!</p>
210
211 <p>More information on using LIT can be found
212 <a href="http://llvm.org/docs/CommandGuide/lit.html">here</a>. For more
213 general information about the LLVM testing infrastructure, see the
214 <a href="http://llvm.org/docs/TestingGuide.html">LLVM Testing Infrastructure
215 Guide</a>
216 </p>
217
218 <p>
219 Shared libraries for libc++ should now be present in llvm/build/lib. Note
220 that it is safest to use this from its current location rather than
221 replacing your system's libc++ (if it has one, if not, go right ahead).
222 </p>
223
224 <p>
225 Mac users, remember to be careful when replacing the system's libc++.
226 <strong>Your system will not be able to boot without a funcioning
227 libc++.</strong>
228 </p>
229
230 <!--=====================================================================-->
231 <h3>Notes</h3>
232 <!--=====================================================================-->
233
234 <p>
235 Building libc++ with <code>-fno-rtti</code> is not supported. However
236 linking against it with <code>-fno-rtti</code> is supported.
237 </p>
238
239 <p>Send discussions to the
240 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">clang mailing list</a>.</p>
241
242 <!--=====================================================================-->
243 <h2>Using libc++ in your programs</h2>
244 <!--=====================================================================-->
245
246 <!--=====================================================================-->
247 <h3>FreeBSD and Mac OS X</h3>
248 <!--=====================================================================-->
249
250 <p>
251 To use your system-installed libc++ with clang you can:
Howard Hinnant65451f12011-01-27 23:18:19 +0000[diff] [blame]252 </p>
253
254 <ul>
255 <li><code>clang++ -stdlib=libc++ test.cpp</code></li>
Howard Hinnantaf347342012-07-19 15:57:51 +0000[diff] [blame]256 <li><code>clang++ -std=c++11 -stdlib=libc++ test.cpp</code></li>
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]257 </ul>
258
Howard Hinnant22b781b2012-11-06 21:31:37 +0000[diff] [blame]259 <p>
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]260 To use your tip-of-trunk libc++ on Mac OS with clang you can:
Howard Hinnant22b781b2012-11-06 21:31:37 +0000[diff] [blame]261 </p>
262
263 <ul>
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]264 <li><code>export DYLD_LIBRARY_PATH=path/to/build/lib</code>
Howard Hinnant22b781b2012-11-06 21:31:37 +0000[diff] [blame]265 <li><code>clang++ -std=c++11 -stdlib=libc++ -nostdinc++
266 -I&lt;path-to-libcxx&gt;/include -L&lt;path-to-libcxx&gt;/lib
267 test.cpp</code></li>
268 </ul>
269
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]270 <!--=====================================================================-->
271 <h3>Linux</h3>
272 <!--=====================================================================-->
273
274 <p>
275 You will need to keep the source tree of
276 <a href="http://libcxxabi.llvm.org">libc++abi</a> available on your build
277 machine and your copy of the libc++abi shared library must be placed where
278 your linker will find it.
279 </p>
280
281 <p>
282 Unfortunately you can't simply run clang with "-stdlib=libc++" at this
283 point, as clang is set up to link for libc++ linked to libsupc++. To get
284 around this you'll have to set up your linker yourself (or patch clang).
285 For example:
286 </p>
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]287
288 <ul>
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]289 <li><code>clang++ -stdlib=libc++ helloworld.cpp -nodefaultlibs -lc++ -lc++abi -lm -lc -lgcc_s -lgcc</code></li>
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]290 </ul>
291
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]292 <p>
293 Alternately, you could just add libc++abi to your libraries list, which in
294 most situations will give the same result:
295 </p>
Howard Hinnant51065652012-05-20 13:03:53 +0000[diff] [blame]296
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]297 <ul>
298 <li><code>clang++ -stdlib=libc++ helloworld.cpp -lc++abi</code></li>
299 </ul>
Howard Hinnant8c217372010-05-11 19:53:34 +0000[diff] [blame]300
Howard Hinnant56f0d5b2010-10-05 16:44:40 +0000[diff] [blame]301 <!--=====================================================================-->
Marshall Clow992f9d52014-04-03 03:13:12 +0000[diff] [blame]302 <h2>Bug reports and patches</h2>
303 <!--=====================================================================-->
304
305<p>
306If you think you've found a bug in libc++, please report it using
307the <a href="http://llvm.org/bugs">LLVM Bugzilla</a>. If you're not sure, you
Marshall Clow3f357192014-04-07 07:28:33 +0000[diff] [blame]308can post a message to the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">cfe-dev</a>
Marshall Clow992f9d52014-04-03 03:13:12 +0000[diff] [blame]309mailing list or on IRC. Please include "libc++" in your subject.
310</p>
311
312<p>
313If you want to contribute a patch to libc++, the best place for that is the
314<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits">cfe-commits</a>
315mailing list. Please include "libc++" and "PATCH" in your subject.
316</p>
317
318 <!--=====================================================================-->
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]319 <h2 id="libsupcxx">Build on Linux using CMake and libsupc++.</h2>
Michael J. Spencerdb8a0302012-12-31 19:34:21 +0000[diff] [blame]320 <!--=====================================================================-->
321
322 <p>
323 You will need libstdc++ in order to provide libsupc++.
324 </p>
325
326 <p>
327 Figure out where the libsupc++ headers are on your system. On Ubuntu this
328 is <code>/usr/include/c++/&lt;version&gt;</code> and
329 <code>/usr/include/c++/&lt;version&gt;/&lt;target-triple&gt;</code>
330 </p>
331
332 <p>
333 You can also figure this out by running
334 <pre>
335$ echo | g++ -Wp,-v -x c++ - -fsyntax-only
336ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu"
337ignoring nonexistent directory "/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../x86_64-linux-gnu/include"
338#include "..." search starts here:
339#include &lt;...&gt; search starts here:
340 /usr/include/c++/4.7
341 /usr/include/c++/4.7/x86_64-linux-gnu
342 /usr/include/c++/4.7/backward
343 /usr/lib/gcc/x86_64-linux-gnu/4.7/include
344 /usr/local/include
345 /usr/lib/gcc/x86_64-linux-gnu/4.7/include-fixed
346 /usr/include/x86_64-linux-gnu
347 /usr/include
348End of search list.
349 </pre>
350
351 Note the first two entries happen to be what we are looking for. This
352 may not be correct on other platforms.
353 </p>
354
355 <p>
356 We can now run CMake:
357 <ul>
358 <li><code>CC=clang CXX=clang++ cmake -G "Unix Makefiles"
Peter Collingbourned0d308f2013-10-06 22:13:19 +0000[diff] [blame]359 -DLIBCXX_CXX_ABI=libstdc++
Michael J. Spencerdb8a0302012-12-31 19:34:21 +0000[diff] [blame]360 -DLIBCXX_LIBSUPCXX_INCLUDE_PATHS="/usr/include/c++/4.7/;/usr/include/c++/4.7/x86_64-linux-gnu/"
361 -DCMAKE_BUILD_TYPE=Release
362 -DCMAKE_INSTALL_PREFIX=/usr
363 &lt;libc++-source-dir&gt;</code></li>
Peter Collingbourned0d308f2013-10-06 22:13:19 +0000[diff] [blame]364 <li>You can also substitute <code>-DLIBCXX_CXX_ABI=libsupc++</code>
365 above, which will cause the library to be linked to libsupc++ instead
366 of libstdc++, but this is only recommended if you know that you will
367 never need to link against libstdc++ in the same executable as libc++.
368 GCC ships libsupc++ separately but only as a static library. If a
369 program also needs to link against libstdc++, it will provide its
370 own copy of libsupc++ and this can lead to subtle problems.
Michael J. Spencerdb8a0302012-12-31 19:34:21 +0000[diff] [blame]371 <li><code>make</code></li>
372 <li><code>sudo make install</code></li>
373 </ul>
374 <p>
375 You can now run clang with -stdlib=libc++.
376 </p>
377 </p>
378
379 <!--=====================================================================-->
Dan Albert35d775d2014-08-11 15:12:46 +0000[diff] [blame^]380 <h2 id="libcxxrt">Build on Linux using CMake and libcxxrt.</h2>
Howard Hinnantaf4d1612013-02-08 19:10:36 +0000[diff] [blame]381 <!--=====================================================================-->
382
383 <p>
384 You will need to keep the source tree of
385 <a href="https://github.com/pathscale/libcxxrt/">libcxxrt</a> available
386 on your build machine and your copy of the libcxxrt shared library must
387 be placed where your linker will find it.
388 </p>
389
390 <p>
391 We can now run CMake:
392 <ul>
393 <li><code>CC=clang CXX=clang++ cmake -G "Unix Makefiles"
394 -DLIBCXX_CXX_ABI=libcxxrt
Howard Hinnantfae54b92013-02-26 16:27:55 +0000[diff] [blame]395 -DLIBCXX_LIBCXXRT_INCLUDE_PATHS="&lt;libcxxrt-source-dir&gt;/src"
Howard Hinnantaf4d1612013-02-08 19:10:36 +0000[diff] [blame]396 -DCMAKE_BUILD_TYPE=Release
397 -DCMAKE_INSTALL_PREFIX=/usr
398 &lt;libc++-source-dir&gt;</code></li>
399 <li><code>make</code></li>
400 <li><code>sudo make install</code></li>
401 </ul>
402 <p>
403 Unfortunately you can't simply run clang with "-stdlib=libc++" at this point, as
404 clang is set up to link for libc++ linked to libsupc++. To get around this
405 you'll have to set up your linker yourself (or patch clang). For example,
406 <ul>
407 <li><code>clang++ -stdlib=libc++ helloworld.cpp -nodefaultlibs -lc++ -lcxxrt -lm -lc -lgcc_s -lgcc</code></li>
408 </ul>
409 Alternately, you could just add libcxxrt to your libraries list, which in most
410 situations will give the same result:
411 <ul>
412 <li><code>clang++ -stdlib=libc++ helloworld.cpp -lcxxrt</code></li>
413 </ul>
414 </p>
415 </p>
416
417 <!--=====================================================================-->
Howard Hinnant56f0d5b2010-10-05 16:44:40 +0000[diff] [blame]418 <h2>Design Documents</h2>
419 <!--=====================================================================-->
420
421<ul>
422<li><a href="atomic_design.html"><tt>&lt;atomic&gt;</tt></a></li>
Howard Hinnant9835d762010-11-19 01:38:58 +0000[diff] [blame]423<li><a href="type_traits_design.html"><tt>&lt;type_traits&gt;</tt></a></li>
Marshall Clowe47bc9b2013-03-14 19:00:34 +0000[diff] [blame]424<li><a href="http://cplusplusmusings.wordpress.com/2012/07/05/clang-and-standard-libraries-on-mac-os-x/">Excellent notes by Marshall Clow</a></li>
Howard Hinnantc7cbe502013-03-14 18:37:48 +0000[diff] [blame]425<li><a href="debug_mode.html">Status of debug mode</a></li>
Howard Hinnant56f0d5b2010-10-05 16:44:40 +0000[diff] [blame]426</ul>
427
Howard Hinnantbc8d3f92010-05-11 19:42:16 +0000[diff] [blame]428</div>
429</body>
Chris Lattner4b748952010-05-11 20:37:52 +0000[diff] [blame]430</html>