Thank you for this information. Adding "call" fixed my problem. -Marc
On Fri, Jul 31, 2009 at 11:21 AM, Tyler Roscoe <[email protected]> wrote: > On Fri, Jul 31, 2009 at 11:14:39AM -0400, David Cole wrote: > > This is not a VS specific problem, but rather how Windows batch files > behave > > in general. > > > > If an executable or batch file returns an error exit status, but the > "call" > > keyword is not used in the calling batch file, then the calling batch > file > > exits without executing the remainder of the script. Using the call > keyword > > prevents that behavior and makes it work like you'd expect. > > I have seen this behavior even when the batch file exits normally, > without error condition. This is in VS2005 if it matters. > > tyler >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
