John Colvin
4fdc866485
I noticed the build cmds were broken on Windows because the debugger would still start even when the preLaunchTask (build) failed!
25 lines
744 B
Batchfile
25 lines
744 B
Batchfile
@echo off
|
|
setlocal
|
|
setlocal enabledelayedexpansion
|
|
|
|
call "C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\Common7\\Tools\\VsDevCmd.bat"
|
|
|
|
set TOOLS_DIR=%~dp0
|
|
set REPO_DIR=%~dp0..
|
|
set BUILD_PY=%TOOLS_DIR%\py\build_data_stream.py
|
|
|
|
if DEFINED VIRTUAL_ENV (
|
|
@REM We're already in a venv, just run build_data_stream.py (whether or not it is
|
|
@REM the 'right' venv is the caller's responsibility)
|
|
echo "Building in the current venv '%VIRTUAL_ENV'"
|
|
@call python %BUILD_PY% %*
|
|
set RESULT=!ERRORLEVEL!
|
|
) else (
|
|
@REM Ensure the (default) venv is created, then run build_spark.py in it
|
|
@call %TOOLS_DIR%\ensure_venv.cmd
|
|
@call %TOOLS_DIR%\venv_exec.cmd python %BUILD_PY% %*
|
|
set RESULT=!ERRORLEVEL!
|
|
)
|
|
|
|
EXIT /B !RESULT!
|