Hi.From a builders perspective, if I run buildwin.cmd with an appropriate set of arguments ... and if PocoFoundation*.lib fails to build (say because some pocomsg.h file was read-only), then buildwin.cmd does not exit, but continues to try the downstream build actions.

Was this a planned behaviour? If not, what would be a good way to attempt to fix it ?Thanks in advance,Parag Doke

To check the return value and abort the script if build fails. Allegedly, there is some difference between devenv.exe and devenv.com in that regard. Perhaps switching to msbuild would be the best thing to do. If you can contribute some work towards that goal, let us know.

Thanks for your reply Alex. I have an untested version of the modified buildwin.cmd pasted below (don't know how to test all combinations).

However, if I understand correctly, you mentioned using msbuild. Does that mean picking up arguments passed to buildwin.cmd and passing them to msbuild as properties (and msbuild in turn does all the conditional processing and invokes child msbuild instances to build solutions) ... is the right way to go. If yes, I think I can contribute. Will look around on the site to understand how code changes are proposed, reviewed and submitted.

:BuildSolution SolutionName BuildModeREM Assuming all other variables are already set, only the solution name and build mode vary from 1 call of this procedure to anotherREM The tilde removes surrounding quotes. The set "variable=value" style rules out confusion if the value has whitespace.set "SolutionName=%~1"set "BuildMode=%~2"%BUILD_TOOL% %USEENV% %EXTRASW% %ACTIONSW%%ACTION% %CONFIGSW%%BuildMode% "%SolutionName%"if %errorlevel% NEQ 0 ( echo Building %SolutionName% in mode %BuildMode% failed! REM exit /b will only exit the batch file, it will not exit the cmd instance (which is desirable). exit /b %errorlevel%)REM This line simply runs echo. thricefor /l %%i in (1,1,3) do echo.goto EOF

one way would be to create a parent script calling all build combinations. In fact, since we are in the process of building a CI environment, we will need something like that real soon.

ParagDoke wrote:you mentioned using msbuild. Does that mean picking up arguments passed to buildwin.cmd and passing them to msbuild as properties (and msbuild in turn does all the conditional processing and invokes child msbuild instances to build solutions) ... is the right way to go. If yes, I think I can contribute

Yes, there is somewhat of msbuild support in the script already but it needs testing. See this post for more details and links to previous discussions. In particular, VCExpress builds are asked for but we (core developers) do not have time to address that (it is not our pressing need and it would require some code #ifdefing to remove dependencies on MFC imposed bu TestSuite GUI).

ParagDoke wrote:Will look around on the site to understand how code changes are proposed, reviewed and submitted.

When you do the work and test it, send us pull request on github. We'll test your contribution and integrate it. If you need more details or guidance, you can contact me directly at(alex, dot(pocoproject, org)). Here's Getting Started and Coding Style Guide.