<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I hoped it would be so easy, but I don't have any Python.framework dir in the SDK, and in Xcode 5/Maverick, the default for no SDKROOT value is now latest OS X version, which result in 10.9 SDK and not in current system files.<div><br></div><div>I just checked with a new simple project and make sure there where no value for SDKROOT, and the compiler is invoked with:</div><div><br></div><div><div style="margin: 0px 0px 0px 12px; text-indent: -12px; font-size: 11px; font-family: Menlo;">-isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk</div><div style="margin: 0px 0px 0px 12px; text-indent: -12px; font-size: 11px; font-family: Menlo;"><br></div><div style="margin: 0px 0px 0px 12px; text-indent: -12px;">And there is nothing like "Current OS X" in the SDKROOT build setting.</div><div style="margin: 0px 0px 0px 12px; text-indent: -12px; font-size: 11px; font-family: Menlo;"><br></div><div style="margin: 0px 0px 0px 12px; text-indent: -12px;">Even adding the framework to the project does not solve this issue.</div><div style="margin: 0px 0px 0px 12px; text-indent: -12px;"><br></div><div style="margin: 0px 0px 0px 12px; text-indent: -12px;">Until I find a better solution, I will create a Python.framework symlink in my SDK.</div><div style="margin: 0px 0px 0px 12px; text-indent: -12px; font-size: 11px; font-family: Menlo;"><br></div><div><div><div>Le 20 nov. 2013 à 22:01, Greg Clayton <<a href="mailto:gclayton@apple.com">gclayton@apple.com</a>> a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite">I believe if you select "Current MacOSX" instead of the 10.9 SDK, you should be able to build. Or you can remove the Python.framework that is in the SDK. I believe the problem is there is a Python.framework in the SDK, but it is empty (no headers). If you remote the empty Python.framework from the SDK, it should fall back to the installed version.<br><br><br>On Nov 20, 2013, at 8:11 AM, Jean-Daniel Dupas <<a href="mailto:devlists@shadowlab.org">devlists@shadowlab.org</a>> wrote:<br><br><blockquote type="cite">OK,<br><br>I finally try to build it too, and encounter the same issue. And the problem is in fact that the SDK sold with Xcode no longer provide the Python framework. <br><br>See this tech note for details: <a href="https://developer.apple.com/library/mac/technotes/tn2328/_index.html">https://developer.apple.com/library/mac/technotes/tn2328/_index.html</a><br><br><br>Le 20 nov. 2013 à 09:46, Clayden, Jonathan <<a href="mailto:j.clayden@ucl.ac.uk">j.clayden@ucl.ac.uk</a>> a écrit :<br><br><blockquote type="cite">Jean-Daniel,<br><br>Thanks for the reply. I do, however, already have the command-line tools installed.<br><br>Regards,<br>Jon<br><br><br><blockquote type="cite">On 20 Nov 2013, at 08:42, "Jean-Daniel Dupas" <<a href="mailto:devlists@shadowlab.org">devlists@shadowlab.org</a>> wrote:<br><br><br><blockquote type="cite">Le 19 nov. 2013 à 18:14, Clayden, Jonathan <<a href="mailto:j.clayden@ucl.ac.uk">j.clayden@ucl.ac.uk</a>> a écrit :<br><br>Dear all,<br><br>I'm trying to build LLDB, and specifically the command line program, from the SVN trunk on OS X (10.9 + Xcode 5.0.2). The build instructions seem to suggest that this should be straightforward, but after selecting the "lldb-tool" scheme and starting the build as described, after a while I get a build failure with "'Python/Python.h' file not found', referring to the source file lldb-python.h.<br><br>I have installed Swig (via Homebrew), so as far as I know all dependencies should be met.<br><br>Apologies in advance if I've missed something obvious, but it's not clear to me how to proceed. Any help would be appreciated.<br><br>Regards,<br>Jon<br></blockquote><br><br>I didn't try yet to build it on Maverick, but do you have installed "command line tools" with Xcode ?<br>This kind of error appears when some tools try to use the default search path for header instead of using the SDK distributed with Xcode. <br>The usual workaround is to install "command line tools" which provide these headers.<br><br>You can force installation of the "command line tools" by running the following in the terminal, and then choosing install in the dialog that appears.<br><br>xcode-select --install<br><br>Of course, a better solution would be to investigate and figure out what part of the build system relies on this header and fix it to properly use the Xcode SDK.<br><br>-- Jean-Daniel<br><br><br><br><br><br></blockquote><br></blockquote><br>-- Jean-Daniel<br><br><br><br><br><br>_______________________________________________<br>lldb-dev mailing list<br><a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a><br>http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev<br></blockquote><br></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><div>-- Jean-Daniel</div><div><br></div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></div></div></body></html>