Don't let harmless errorlevels from the "set" utility leak into project-specific...
authoraroben@apple.com <aroben@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Wed, 1 Dec 2010 23:09:38 +0000 (23:09 +0000)
committeraroben@apple.com <aroben@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Wed, 1 Dec 2010 23:09:38 +0000 (23:09 +0000)
commit588d7b7fa20a2ed541fe5ddd122fe4a9db54babd
treea801694c984d9cdef0c2b2256c6eea5227330e76
parentdc428e37ec4c8a9f515aec2a8affafbc7c618877
Don't let harmless errorlevels from the "set" utility leak into project-specific build scripts

When using set to unset an environment variable that didn't previously
exist, set raises the errorlevel to 1. This was leaking into
project-specific scripts, causing them to think the build has failed.
We now clear the errorlevel after we finish setting environment
variables.

Fixes <http://webkit.org/b/50350> Windows builds mysteriously fail in
some configurations

Reviewed by Steve Falkenburg.

* win/tools/vsprops/common.vsprops: Call "cmd /c" after setting
environment variables to get rid of any errorlevel that "set" set.

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@73075 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKitLibraries/ChangeLog
WebKitLibraries/win/tools/vsprops/common.vsprops