Author: Aaron Ballman Date: 2022-05-03T07:14:12-04:00 New Revision: 1fc208d40012103f81279ab85949a91f8188e7a1
URL: https://github.com/llvm/llvm-project/commit/1fc208d40012103f81279ab85949a91f8188e7a1 DIFF: https://github.com/llvm/llvm-project/commit/1fc208d40012103f81279ab85949a91f8188e7a1.diff LOG: Fix Clang sphinx build It seems we don't have this option exposed via RST, so switching to use generic backticks instead. Added: Modified: clang/docs/UsersManual.rst Removed: ################################################################################ diff --git a/clang/docs/UsersManual.rst b/clang/docs/UsersManual.rst index 402029c8a64b3..8eb676650ec61 100644 --- a/clang/docs/UsersManual.rst +++ b/clang/docs/UsersManual.rst @@ -1219,7 +1219,7 @@ for generating PCH files: Using a PCH File ^^^^^^^^^^^^^^^^ -A PCH file can then be used as a prefix header when a :option:`-include-pch` +A PCH file can then be used as a prefix header when a ``-include-pch`` option is passed to ``clang``: .. code-block:: console @@ -1245,7 +1245,7 @@ will be processed from the PCH file. Otherwise, Clang will report an error. In this example, ``clang`` will not automatically use the PCH file for ``test.h`` since ``test.h`` was included directly in the source file and not - specified on the command line using :option:`-include-pch`. + specified on the command line using ``-include-pch``. Relocatable PCH Files ^^^^^^^^^^^^^^^^^^^^^ _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
