That's a pretty messy workaround though, I think. ExternalProject_Add passes in lots of variables, including ones that do not typically change, like CMAKE_CXX_COMPILER. Why impose a special requirement on the CMAKE_TOOLCHAIN_FILE variable? Would a patch to avoid the warning be a welcome change, or is there a reason the warning should remain?<br>
<br>Pat<br><br><div class="gmail_quote">On Wed, Feb 6, 2013 at 9:52 PM, Michael Wild <span dir="ltr"><<a href="mailto:themiwi@gmail.com" target="_blank">themiwi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi<br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Wed, Feb 6, 2013 at 11:59 AM, Pat Marion <span dir="ltr"><<a href="mailto:pat.marion@kitware.com" target="_blank">pat.marion@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br><br>I'm emailing about <a href="http://public.kitware.com/Bug/view.php?id=13093" target="_blank">bug 13093</a> in the backlog. I found <a href="http://www.cmake.org/pipermail/cmake/2011-February/042556.html" target="_blank">comments by Brad</a> that suggest it's a legitimate warning, but I'm not sure how a project could avoid the warning.</blockquote>
</div><div><br>By not specifying the toolchain file, for instance? If you have the problem in conjunction with ExternalProject_Add, check whether the CMakeCache.txt file exists in the build tree of the external project. If not, include the flag, otherwise drop it. <br>
<br>My 2c<span class="HOEnZb"><font color="#888888"><br><br>Michael<br></font></span></div></div></div></div>
</blockquote></div><br>