Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove obsolete note about libatomic.

Browse Source 
There's only one GCC in any given NDK release, and it always has
libatomic.

Change-Id: Ifbdc10961c711a6ce27eab60ca2751a04a358a13
This commit is contained in:
Dan Albert
2016-04-07 17:14:07 -07:00
parent e2ff842e2b
commit 59daf3559d
1 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/html/ndk/guides/cpp-support.jd
View File

@@ -186,7 +186,7 @@ NDK to rebuild {@code libc++} from sources by adding the following line to your
LIBCXX_FORCE_REBUILD := true
</pre>
<h4>atomic support</h4>
<h4>Atomic support</h4>
<p>If you include {@code &lt;atomic&gt;}, it's likely that you also need {@code libatomic}.
If you are using {@code ndk-build}, add the following line:</p>
@@ -201,10 +201,6 @@ LOCAL_LDLIBS += -latomic
-latomic
</pre>
<p class="note"><strong>Note: </strong>{@code -latomic} is only available for GCC 4.8.
Because Clang 3.5 and Clang 3.6 use GCC 4.8's headers and libraries, as well as its
{@code as} and {@code ld} options, those versions of Clang also get {@code -latomic}.</p>
<h4>Compatibility</h4>