OK. I think we're getting somewhere. The projects which would not build using
lazbuild on the command line, now build OK with only console output, no dialog interaction. However, the two projects (out of a total of eight) still do not build in Xcode. I've noticed something else, which may or may not be significant. The two projects which fail, leave a shell script called
lazcmd.tmp.sh with lines like this contained therein:
set -e
'/usr/local/bin/lazbuild' '/Users/carlca/Code/fpc/Test/TestLazbuild/TestLazbuild.lpi'
cp -p '/Users/carlca/Code/fpc/Test/TestLazbuild/testlazbuild' '/Users/carlca/Library/Developer/Xcode/DerivedData/TestLazbuild-dxqebgtvlqoefdbumbwgbbqthksb/Build/Products/Debug/TestLazbuild.app/Contents/MacOS/TestLazbuild'
cp -p -R '/Users/carlca/Code/fpc/Test/TestLazbuild/testlazbuild.app/Contents/Resources/' '/Users/carlca/Library/Developer/Xcode/DerivedData/TestLazbuild-dxqebgtvlqoefdbumbwgbbqthksb/Build/Products/Debug/TestLazbuild.app/Contents/Resources'
I'm guessing that a similar file is created in the successful project folders as well, but is deleted on completion of a successful build and run.