There is such a code in the bat file:

FOR /R %BuilderDirectory% /D %%i IN (*) DO ( If Exist %Builder% Call :Build %%i ) :Build( set PathMSBuild=%1 echo %PathMSBuild% )

Along all the paths, the cycle is passed and goes into the label, only the parameter comes constantly empty, echo does not output anything. Tried and so transfer Call :Build "%%i" - the same thing.

What's the matter?

1 answer 1

And if so?

 FOR /R %BuilderDirectory% /D %%i IN (*) DO ( If Exist %Builder% Call :Build %%i ) goto :eof :Build set PathMSBuild=%1 echo %PathMSBuild%

And do not forget about

Finally, support for linking run-time for environment variables has been added. By default, this support is disabled. The / V command line CMD.EXE allows you to turn it on and off. For help, type cmd /?

Binding runtime for environment variables is useful when bypassing the limitations of early binding that occurs when a text string is first read, and not when it is executed. The following example demonstrates an emerging problem when using early variable binding:

set VAR=before if "%VAR%" == "before" ( set VAR=after if "%VAR%" == "after" @echo Тело внутреннего оператора сравнения )

This message will not be displayed, because % VAR% in BOTH IF expressions is substituted at the time of the first use in the first IF, including in the body of the first branch IF, which is a composite expression. In IF, inside a compound expression, the values ​​of "before" and "after" are actually compared, which is false. The following example demonstrates a similar error:

set LIST= for %i in (*) do set LIST=%LIST% %i echo %LIST%

in this case, the list of files in the current folder will never be built. Instead, the value of the LIST variable is the name of the last file found. And again, this happened because% LIST% is substituted only once - at the moment of processing the FOR expression, when the list is still empty. In fact, the above fragment is equivalent to the following example:

for %i in (*) do set LIST= %i

in which the name of the last found file is stored in the variable LIST.

The execution time binding for environment variables occurs when a special character (exclamation mark) is used to indicate that the comparison is performed at run time. If support for linking runtime is included, to achieve the expected results, the above snippets should be modified as follows:

set VAR=before if "%VAR%" == "before" ( set VAR=after if "!VAR!" == "after" @echo Тело внутреннего оператора сравнения )

set LIST= for %i in (*) do set LIST=!LIST! %i echo %LIST%