• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 22 subscribers
  • Views 3140 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Pre build batch file exit code

BAUMER Electric AG BAUMER Electric AG

Hello all

I'd like to use a windows batch-file (preBuild.bat) as pre-build script. If the preBuild.bat detects an error, the build process should be stopped. This works perfectly if the pre-build "script" is a regular .exe, returning a non zero value.

However, I am not successful when returning a non zero value using the preBuild.bat batch file.

I tried to use

exit 1

in the .bat file, but uVision seems to ignore the return value of .bat files.

Any ideas?

Thanks & regards,
Martin

Parents
  • 0

    windows batch-file (preBuild.bat)

    To some extent that's a contradiction. *.bat files are DOS batch files, really. CMD.exe will run those, too, sure, but proper Windows batch files (on those versions of Windows that actually support current uVision) are supposed to be named *.cmd.

    Now, that distinction would usually be moot. But there's just this far-off possibility that uVision might know about one of the major show-stopping shortcomings of actual DOS batch files: they cannot return an exit status. Command.com always finishes with exit status 0 no matter what. The optional "[Exitcode]" argument to CMD.exe's "exit" ia a Windows extension.

    So, assuming that uVision embodies this knowledge, they would be somewhat justified to ignore any exit code from a *.bat script. Maybe you should try making that a *.cmd script instead.

Reply
  • 0

    windows batch-file (preBuild.bat)

    To some extent that's a contradiction. *.bat files are DOS batch files, really. CMD.exe will run those, too, sure, but proper Windows batch files (on those versions of Windows that actually support current uVision) are supposed to be named *.cmd.

    Now, that distinction would usually be moot. But there's just this far-off possibility that uVision might know about one of the major show-stopping shortcomings of actual DOS batch files: they cannot return an exit status. Command.com always finishes with exit status 0 no matter what. The optional "[Exitcode]" argument to CMD.exe's "exit" ia a Windows extension.

    So, assuming that uVision embodies this knowledge, they would be somewhat justified to ignore any exit code from a *.bat script. Maybe you should try making that a *.cmd script instead.

Children