CMD Call command does not work properly

[Destrocamil]

Hey guys!
So, I am trying to convert the set of commands

call "%VS140COMNTOOLS%..\..\VC\bin\amd64\vcvars64.bat"
python build.py -b

cd "..\some-path\windows"
call some.bat

into a stage for just file. Currently, I have this

set windows-shell := ["cmd.exe", "/c"] 
set shell := ["bash", "-uc"]
vstudio_tools := if os_family() == "windows" { 'call "%VS140COMNTOOLS%..\..\VC\bin\amd64\vcvars64.bat" ' } else { "" }
script_dir :=  { "/deployment/" }
build_script := if os_family() == "windows" { "python build.py -b" } else { "python3 deployment/build.py -b --xcode "<xcode-path>"" }
build name version: && build-main
    @echo 'Building {{ name }} version {{ version }} using {{ build_script }} on {{os_family()}}'

[windows] 
[no-cd]
build-main:
   @echo "Building X for {{os_family()}}" 
   {{ vstudio_tools }}
   cd /D {{ justfile_directory()}}{{ script_dir }} && {{ build_script }}
   
   [unix]
build-main:
    @echo "Building X for {{os_family()}}"
    {{ build_script }}

The issue I am facing is that I am unable to make run the {{vstudio_tools}} command. Env var %VS140COMNTOOLS% expands properly, but everytime I get a command not found type of thing. I am not sure how to escape or deal with this.
Just seems to add some ' and \ when it runs.
Help is also appreciated for the correct way of using "" in the build_script for non-windows
Can you guys help me out?
Thanks!

[Destrocamil]

If I do like this

[windows] 
[no-cd]
build-main:
   @echo "Building X for {{os_family()}}" 
   call "%VS140COMNTOOLS%..\..\VC\bin\amd64\vcvars64.bat"
   cd /D {{ justfile_directory()}}{{ script_dir }} && {{ build_script }}

I get this error:

call "%VS140COMNTOOLS%..\..\VC\bin\amd64\vcvars64.bat"
'\"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\..\..\VC\bin\amd64\vcvars64.bat\"' is not recognized as an internal or external command,
operable program or batch file.
error: Recipe `build-main` failed on line 13 with exit code 1

[casey]

I'm not sure, but I think the issue is with quoting. cmd.exe quoting and splitting is very strange, so if at all possible, I'd suggest using a different shell, like powershell or bash.