On 12/09/2019 07:46, Dimitry Sibiryakov wrote:
>   I also see that setenvvar.bat doesn't call vcvarsall.bat anymore
> which result in path to MSBuild is not set and build failure. Was this
> change intended?
>
>

It's the developer responsibility to call the VS scripts to set the
environment, through the VS command prompt or manually.


Adriano



Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to