Hi Pat,<br><br>How do you manage to deal with situations where the build environment runs the ExternalProject's configuration via cmake and has environment variables set that wouldn't have been otherwise (and that you don't want set) - for example, Visual Studio sets half a dozen new environment variables and modifies the path before running its build steps. Are you just figuring out all of the CMake variables and properties that are affected by environment variables, and presetting them in the cache? Or is there a way to avoid this that I just haven't managed to find yet?<br>
<br>I've seen cases where the result of running CMake on a project, and using the same project as an ExternalProject are rather different - I'll admit it's largely a guess that it's a difference in the environment variables on the shell vs through the build environment/tool, but it's the only thing that seems to make sense.<br>
<br>Or do you just avoid this by never using the more complex build environments, sticking to make, and hoping it doesn't do anything strange to your environment before calling the external project (because I don't think I've seen this behaviour with make).<br>
<br>Thanks,<br>Christopher<br><br><div class="gmail_quote">On Tue, Jan 22, 2013 at 3:26 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 Bill,<br><br>We use ExternalProject on the VES project to manage crosscompile builds. We use ExternalProject to create builds for the host, Android, iOS-device, and iOS-simulator architectures.<span class="HOEnZb"><font color="#888888"><br>
<br>Pat</font></span><div class="HOEnZb"><div class="h5"><br><br></div></div></blockquote></div><br>