<div class="gmail_quote">On Mon, Sep 21, 2009 at 4:03 PM, Brad King <span dir="ltr"><<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Robert Dailey wrote:<br>
> I've attached a test project that reproduces this issue. At the root<br>
> "test" directory, create a new directory called 'build'. So you will<br>
> have "test/build".<br>
><br>
> cd into test/build and run:<br>
><br>
> cmake -G "Xcode" ..<br>
><br>
> This will generate an xcode project for you. Open that, and right click<br>
> on main.cpp (which should be colored red because it is an invalid path)<br>
> and click "Get Info". Look at the path. It's totally wrong.<br>
<br>
</div>Great, thanks. Now I see the problem. In fact it happens<br>
even if I manually expand the function inline in the subdir.<br>
The key is that the Xcode project file is in a subdir and<br>
not the top.<br>
<br>
This was in fact caused by the patch for the bug I linked<br>
earlier in this thread:<br>
<div class="im"><br>
<a href="http://www.cmake.org/Bug/view.php?id=8481" target="_blank">http://www.cmake.org/Bug/view.php?id=8481</a><br>
<br>
</div>In order to help Xcode 3.0 set breakpoints the project file<br>
needs to reference sources with relative paths. The fix for<br>
that bug always converts paths relative to the top of the<br>
tree instead of the directory containing the Xcode project<br>
file. It went unnoticed because usually these are the same.<br>
<br>
I'm going to re-open that issue with a link to this message.</blockquote><div><br></div><div>Great! Glad I could help. Let me know when this is fixed so I can download a new nightly build. I'll try to keep up with that bug status as well. </div>
</div>