From abbe91c58ccf49dd60027ec5663154e54365f0fe Mon Sep 17 00:00:00 2001 From: "Alan W. Irwin" Date: Wed, 3 Sep 2014 07:03:12 -0700 Subject: [PATCH] Help: Clarify --debug-trycompile usage with try_compile Explain that try_compile calls need to be protected with conditions to avoid running more than once so that it is easy to isolate a single try_compile to perform with --debug-trycompile. --- Help/command/try_compile.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Help/command/try_compile.rst b/Help/command/try_compile.rst index 8ed3cf4de..224c67b45 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,