MSVC2013: How to avoid aborting build process with Pre-build script in error (error MSB3073: :VCEnd" exited with code -1)

manpreet Best Answer 2 years ago

I set a pre-build event in MSVC13 which exit with an error MSB3073: :VCEnd" exited with code -1.And I'm unable to bypass this error, i don't want the build process stop even if the bat file exit with error.

I have configured the

BuildEvents > Pre-Build Event

with a call to a bat file Command Line:

call $(ProjectDir)\pre_build.bat $(Configuration)=1

This bat file contains 2 calls to other bat files. The first one exit with an error (but i don't care as the sub-task I want it does is done) and the second is ok.

In the pre-build.bat, I tried to intercept this error and update the value to say everything is ok to MSVC but i can't succeed. I tried to echo ERRORLEVEL but it contains 0. I tried to set ERRORLEVEL to 0 but doesn't change anything at MSVC level. I tried to add an exit 0, exit /b 0 or @exit 0 at end of my bat file, but doesn't change.

I found this link (https://blogs.msdn.microsoft.com/astebner/2006/08/08/how-to-make-visual-studio-2005-ignore-return-codes-from-pre-build-events/) explaining how to tell to MSVC to ignore errors but it doesn't work as it is written for MSVC2005 and the syntax of PreBuildEvent in vcxproj has changed.

If i run my script in a console, it exit with an error but, as said previously, i don't care about this error, part of the job is done.

I also try with MSVC running as Admin, no change.

Content of my pre-build.bat:

call build.bat %* TOOLCHAIN=mdk4cc5 TC_NO_CHECK=1

and build.bat runs SCons (I haven't any knowledges on SCons)

If you have an idea on how to ignore this error in MSVC in order to contiue the build process (whatever it is clean or not), it will be very helpful as i already spent a day on this ...

Thanks a lot for your feedback and answers.

manpreet 2 years ago

I am not a real C++ Expert but maybe this post could help you: Disable single warning error

Someone in the Answers talked about Pragma Surprass so you could try that:

#pragma warning(suppress: 4101)

// here goes your single line of code where the warning occurs