Make unittests work on Windows (again)

sdk/bin/pub.bat

 @echo off
 REM Copyright (c) 2014, the Dart project authors.  Please see the AUTHORS file
 REM for details. All rights reserved. Use of this source code is governed by a
 REM BSD-style license that can be found in the LICENSE file.
 
 rem Run pub.dart on the Dart VM. This script is only used when running pub from
 rem within the Dart source repo. The shipped SDK instead uses "pub_sdk.bat",
 rem which is renamed to "pub.bat" when the SDK is built.
 
 setlocal
@@ skipping 17 matching lines @@
   set VM_OPTIONS=%VM_OPTIONS% %DART_VM_OPTIONS%
 )
 
 rem Use the Dart binary in the built SDK so pub can find the version file next
 rem to it.
 set BUILD_DIR=%SDK_DIR%\..\build\ReleaseIA32
 set PACKAGES_DIR=%BUILD_DIR%\packages
 set DART=%BUILD_DIR%\dart-sdk\bin\dart
 
 rem Run pub.
-set PUB="%SDK_DIR%\lib\_internal\pub.dart"

[Johnni Winther, 2015/03/24 10:52:24]

nweiz@, rnystrom@: Why has this not been tested on Windows?

[Bob Nystrom, 2015/03/24 16:30:42]

We generally do try to locally test Windows-only changes, but it's not easy to
do. We only have one Windows machine and it's crushingly slow and takes forever
(hours) to get the latest code.

Note that this batch file is only used by Dart developers running directly from
the Dart source repo. End users run pub_sdk.bat which gets renamed to pub.bat
and shipped in the actual SDK.

[Johnni Winther, 2015/03/25 07:48:31]

Acknowledged. Hope pub_sdk.bat is tested better then.

+set PUB="%SDK_DIR%\lib\_internal\pub\bin\pub.dart"
 "%DART%" %VM_OPTIONS% --package-root="%PACKAGES_DIR%" "%PUB%" %*
 
 endlocal
 
 exit /b %errorlevel%
 
 :follow_links
 setlocal
 for %%i in (%1) do set result=%%~fi
 set current=
 for /f "usebackq tokens=2 delims=[]" %%i in (`dir /a:l "%~dp1" 2^>nul ^
                                              ^| find ">     %~n1 ["`) do (
   set current=%%i
 )
 if not "%current%"=="" call :follow_links "%current%", result
 endlocal & set %~2=%result%
 goto :eof
 
 :end