You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
building...
CMD will not recognize non .exe file for execution, path: make build
Building hbat-blmp-api-windows.exe ...
running...
'bin' is not recognized as an internal or external command,
operable program or batch file.
Process Exit with Code: 1
building...
CMD will not recognize non .exe file for execution, path: make build
Building hbat-blmp-api-windows.exe ...
running...
'.' is not recognized as an internal or external command,
operable program or batch file.
Result:
The only successful run. I have to use bin\<binary name> with the windows path separator.
It seems that the universal path separator / is being split for some reason. When i use \ it can find the directory. When i supply bin/<binary-name> to the .air.toml file everything works fine. So, something in the cli prevents the universale path separator from working properly.
However, i need to use the cli as the binary name is being generated dynamically, relative to some build conditions.
The text was updated successfully, but these errors were encountered:
ZanzyTHEbar
changed the title
Using the air cli on Windows breaks when providing nested paths to build.cmd
Using the air cli on Windows breaks when providing nested paths to build.binMay 24, 2024
Example 1
.Result:
Example 2
.Result:
Example 3
.Result:
The only successful run. I have to use
bin\<binary name>
with the windows path separator.It seems that the universal path separator
/
is being split for some reason. When i use\
it can find the directory. When i supplybin/<binary-name>
to the.air.toml
file everything works fine. So, something in the cli prevents the universale path separator from working properly.However, i need to use the
cli
as the binary name is being generated dynamically, relative to some build conditions.The text was updated successfully, but these errors were encountered: