summaryrefslogtreecommitdiffstats
path: root/Help
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2014-09-04 13:48:30 (GMT)
committerCMake Topic Stage <kwrobot@kitware.com>2014-09-04 13:48:30 (GMT)
commit0ad4f28fc0b702beff8d197e52d10814178b79b5 (patch)
treeeae6b65e869bd4666ae90331e1e587c7f17617d9 /Help
parentf7c44eac4c195a3ae416453be551910fdb311ac6 (diff)
parentabbe91c58ccf49dd60027ec5663154e54365f0fe (diff)
downloadCMake-0ad4f28fc0b702beff8d197e52d10814178b79b5.zip
CMake-0ad4f28fc0b702beff8d197e52d10814178b79b5.tar.gz
CMake-0ad4f28fc0b702beff8d197e52d10814178b79b5.tar.bz2
Merge topic 'doc-try_compile-debug-advice'
abbe91c5 Help: Clarify --debug-trycompile usage with try_compile
Diffstat (limited to 'Help')
-rw-r--r--Help/command/try_compile.rst7
1 files changed, 4 insertions, 3 deletions
diff --git a/Help/command/try_compile.rst b/Help/command/try_compile.rst
index 8ed3cf4..224c67b 100644
--- a/Help/command/try_compile.rst
+++ b/Help/command/try_compile.rst
@@ -36,9 +36,10 @@ cleaned automatically. For debugging, --debug-trycompile can be
passed to cmake to avoid this clean. However, multiple sequential
try_compile operations reuse this single output directory. If you use
--debug-trycompile, you can only debug one try_compile call at a time.
-The recommended procedure is to configure with cmake all the way
-through once, then delete the cache entry associated with the
-try_compile call of interest, and then re-run cmake again with
+The recommended procedure is to protect all try_compile calls in your
+project by ``if(NOT DEFINED RESULT_VAR)`` logic, configure with cmake
+all the way through once, then delete the cache entry associated with
+the try_compile call of interest, and then re-run cmake again with
--debug-trycompile.
Some extra flags that can be included are, INCLUDE_DIRECTORIES,