[PATCH] D53018: Document the behavior of option passing when using -DCLANG_ENABLE_BOOTSTRAP=OnAlso document -DCLANG_BOOTSTRAP_PASSTHROUGH

Phabricator via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Tue Oct 16 23:37:40 PDT 2018


This revision was not accepted when it landed; it landed in state "Needs Review".
This revision was automatically updated to reflect the committed changes.
Closed by commit rL344669: Document the behavior of option passing when using -DCLANG_ENABLE_BOOTSTRAP=On (authored by sylvestre, committed by ).

Repository:
  rL LLVM

https://reviews.llvm.org/D53018

Files:
  llvm/trunk/docs/AdvancedBuilds.rst


Index: llvm/trunk/docs/AdvancedBuilds.rst
===================================================================
--- llvm/trunk/docs/AdvancedBuilds.rst
+++ llvm/trunk/docs/AdvancedBuilds.rst
@@ -41,6 +41,16 @@
 configurations for each stage. The next series of examples utilize CMake cache
 scripts to provide more complex options.
 
+By default, only a few CMake options will be passed between stages.
+The list, called _BOOTSTRAP_DEFAULT_PASSTHROUGH, is defined in clang/CMakeLists.txt.
+To force the passing of the variables between stages, use the -DCLANG_BOOTSTRAP_PASSTHROUGH
+CMake option, each variable separated by a ";". As example:
+
+.. code-block:: console
+
+  $ cmake -G Ninja -DCLANG_ENABLE_BOOTSTRAP=On -DCLANG_BOOTSTRAP_PASSTHROUGH="CMAKE_INSTALL_PREFIX;CMAKE_VERBOSE_MAKEFILE" <path to source>
+  $ ninja stage2
+
 The clang build system refers to builds as stages. A stage1 build is a standard
 build using the compiler installed on the host, and a stage2 build is built
 using the stage1 compiler. This nomenclature holds up to more stages too. In


-------------- next part --------------
A non-text attachment was scrubbed...
Name: D53018.169951.patch
Type: text/x-patch
Size: 1066 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20181017/484b6d9d/attachment.bin>


More information about the llvm-commits mailing list