Comments on: Xcode Run Script Build Phase debugging https://briksoftware.com/blog/archives/120 Thu, 14 Jun 2012 18:56:48 +0000 hourly 1 https://wordpress.org/?v=4.7 By: bitwise · Xcode Run Script Build Phase error reporting https://briksoftware.com/blog/archives/120/comment-page-1#comment-16167 Fri, 26 Mar 2010 17:15:07 +0000 https://briksoftware.com/blog/?p=120#comment-16167 […] thought about blogging about this several months ago, but never got around to it. And don’t skip reading the comments. […]

]]>
By: 0xced https://briksoftware.com/blog/archives/120/comment-page-1#comment-16166 Fri, 26 Mar 2010 13:40:38 +0000 https://briksoftware.com/blog/?p=120#comment-16166 You can also use echo “note: xxx”

]]>
By: Kelan Champagne https://briksoftware.com/blog/archives/120/comment-page-1#comment-16165 Thu, 25 Mar 2010 22:58:12 +0000 https://briksoftware.com/blog/?p=120#comment-16165 If you really want to get fancy, you can include a file path and line number (and the appropriate colons), and Xcode will open that when you double-click on the entry in the build log. The exact format is:

file_path:line_num: [error|warning]: message goes here

for example, from Python I use:

print “%s:%d: %s: %s” % (filePath, lineNum, level, message)

Not all custom build script warnings/errors will have an associated file and line, but if they do, this trick can be pretty handy.

]]>