How to expose bash script errors?

If you want a run script error to stop the build, you should exit the script with a non-zero status code. For example:

exit 1

If you want to show an error from your script, you just have to print it in the standard way. For example:

echo "/foo/bar/tmp.sh:42: error: Varnish waffles before continuing."

where “42” is the line number.

I don’t think this is documented anywhere; I just cribbed the ideas from

/Applications/Xcode.app/Contents/Developer/Tools/RunUnitTests

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Thanks for your response, Quinn.

I understand that 'exit 1' and 'echo' works from a Build Phase Run Script, but my scripts are run from a scheme during Build pre-actions and post-actions. I have two schemes named Production and Test. My script accepts one parameter, PROD or TEST. This allows the script to differentiate between the Production or Test scheme. The script actually builds a .h file and must be run before the build starts. I don't think that I can use a Build Phase Run Script.

I think that I define my Build pre-action script for my scheme like this:

prebuildScript="${PROJECT_DIR}/BuildProcess/prebuild.sh"
errorFile="${buildProcessDir}prebuildErrors.txt"
$prebuildScript TEST 2>$errorFile

Then, I could create a Build Phase Run Script that checks if the error file exists and has more than zero bytes. If the error file has content, the content could be echo'ed and exit 1 could be called. This seems cumbersome, but it may be a solution. Is there a better way?

I resolved this issue by moving my pre-action and post-action bash scripts in the Build step of my scheme to scripts in the Build Phase. I added the following pre-action script in the Build step of each configuration.

# "TEST" corresponds to the current Xcode scheme (Test).
environmentFile="${PROJECT_DIR}/BuildProcess/CurrentEnvironment.txt"
echo "TEST" > $environmentFile

I check my CurrentEnvironment.txt file to determine which configuration is active from the Build Phase scripts. I don't know how else to determine the active configuration from a Build Phase Run Script. If anyone knows of a better way, please respond.