I wrote a bunch of Objective-C logging code that includes file and line in the output in such a way that I can click on it in the XCode build window.
Usually that works fine, but the bundle logic that finds the full path when given a file name seems to have a flaw: For example when the listed line is
PLDocumentController.m:117:[updateRecentMenu:] WARNING: bla bla
the link actually ends up pointing to a file named BPLDocumentController.m *note the extra 'B' at the beginning).
Seems to me it might be a fairly easy fix for someone how knows what he/she is doing...
Thanks
Gerd
On Oct 23, 2007, at 6:24 PM, Gerd Knops wrote:
I wrote a bunch of Objective-C logging code that includes file and line in the output in such a way that I can click on it in the XCode build window.
Usually that works fine, but the bundle logic that finds the full path when given a file name seems to have a flaw: For example when the listed line is
PLDocumentController.m:117:[updateRecentMenu:] WARNING: bla bla
the link actually ends up pointing to a file named BPLDocumentController.m *note the extra 'B' at the beginning).
Seems to me it might be a fairly easy fix for someone how knows what he/she is doing...
Was bugging me enough to dig through the code... Patch below. Should I apply it to the repository?
Gerd
Index: Bundles/Xcode.tmbundle/Support/bin/run_xcode_target.rb =================================================================== --- Bundles/Xcode.tmbundle/Support/bin/run_xcode_target.rb (revision 8284) +++ Bundles/Xcode.tmbundle/Support/bin/run_xcode_target.rb (working copy) @@ -170,7 +170,7 @@ end next unless obj['isa'] == 'PBXFileReference' - next unless obj['path'].include? basename + next unless obj['path'].include? '/' + basename or obj ['path'] == basename path = path_for_fileref(key) + '/' + obj['path'] break end
-
Gerd Knops